中文翻译版

Fiddler Everywhere Patch (Automated)

Guides you to Patch Fiddler Everywhere on Windows Automatically.

Parent Repo: https://github.com/msojocs/fiddler-everywhere-enhance

What and How?

This's a a patch for Telerik Fiddler Everywhere. It can grant you a trial that doesn't expire. The trial has all the features. This's the guide for applying patch automatically.

Feature Updates

[!TIP] Patching is even faster.

• Previously    : 2m 25s
• Now             : 1m 30s

[!IMPORTANT] If you encounter an issue of "Fiddle Everywhere Crashing in Startup", you can follow this.

[!TIP] Now supports changing patch server port (Useful if port conflitcts encountered)

[!TIP] Now supports changing default user profile (fake) for FE (incl - email, fname, lname, country-code, provider)

[!IMPORTANT] Linux Automated Patching is Supported Now!

[!WARNING] The new patch want to write files in a directory inside FE app itself. So you need to give write permissions in Linux. See #27 for more. And feel free to drop your suggestion to automate the process.

[!IMPORTANT]

Update Notice: Support for Syncing forks with upstream repo: READ MORE

Get Started.

[!TIP] You must always check if your fork is up to date so no fails. (We reccomend you enable Scheduled upstream pulling)

• How even this Automated Patching Works?

  • Well, this automated patch do the same that you do mannually for patching. It downloads fiddler everywhere extract it. Remove, Replace, Edit, Move files and then, the patched application is ready.

• Workflow Dispatch? or Workflow Dispatch Latest?

  • Latest Version - Workflow Dispatch - Patch the latest version, and upload as artifact.
  • Custom Version - Workflow Dispatch - Allows you to select a compatible version (5.9.0 +) and patch and upload as a workflow artifact.

[!TIP] We highly reccomend you to use Latest Version - Workflow Dispatch, which patch the latest available version. Custon Version - Workflow Dispatch allows you to select a version starting from 5.9.0 + too.

With Latest Version - Workflow Dispatch

• Fork this repo.
• Go to actions tab, Select Latest Version - Workflow Dispatch workflow.
• Trigger it with workflow dispatch
• After a successful trigger download artifact that named like Fiddler-Everywhere-VX.X.X-Patched
• Extract it. Run it

• Here how you do it...

  https://github.com/user-attachments/assets/437c3448-1ea2-4c99-9123-e56b1665a37b

With Custom Version - WorkFlow Dispatch

• Fork this repo
• Go to actions tab, Select Custom Version - Workflow Dispatch workflow.
• Trigger it with workflow diaptch providing the version you want to patch
• After a successful trigger download artifact that named like Fiddler-Everywhere-VX.X.X-Patched
• Extract it. Run it

[!WARNING] Please Note that Only Versions Up to 5.9.0 ( 5.9.0 + ) are supported.

You can find a list of releases here - Release History

• Here how you do it...

  https://github.com/user-attachments/assets/1e9fa214-b9c9-469c-83f0-e5ae4527d2f7

Scheduled Syncing Forks with Upstream Repo

FE Patch 1.0.8 adds support to sync your repo with upstream repo - scheduled (default: every 6 hours)

[!NOTE] Tnx: lobe-chat & ous50

[!IMPORTANT]

• For this upstream pulling action to work, you need to enable Upstream Sync Github Action.
• And the action'll create an issue in your fork if pulling is unsuccesfull. So you need to enable issues for your fork with your repositories settings (Settings --> General --> Features Issues)
• For more information on how this action works: lobe-chat's Sync Feature Wiki - en-US & lobe-chat's Sync Feature Wiki - zh-CN

[!TIP]

• You can change schedule by editing - cron: '0 */6 * * *' in cp_pull_upstream.yml
• For more information on - cron of Github Actions, visit Github Documentation - Scheduling Actions

[!CAUTION]

• IF you use another method (maybe a Github App), to sync your forks with upstream repos, (for ex: Pull by Wei), you should disable the Upstream Sync action by going through, Actions --> Upstream Sync --> Right Top Menu [...] --> Disable Workflow
• For more information on how to disable a workflow: Github Documentation on Disabling & Enabling Workflows

[!NOTE] For Generic Linux and MacOS instructions, use source repository

[!CAUTION] Please don't use this patch for illegal matters. And we'd love if you can buy and support the officials: Please Support

Fiddler Everywhere Crashing at Startup

If you encounter this issue, it's most likely unrelated to the patch! You should confirm it!

• Check logs by running Fiddler Everywhere.exe from the terminal. Pay special attention to the following line. (it’s omitted in the official, non-patched version of Fiddler Everywhere.)

  Server error log during start: System.IO.IOException: Failed to bind to address http://localhost:8868.
  

  If you see this, it's completely unrelated to the patch. You should see the same issue with the non-patched official FE. Confirm this.

• Check Fiddler Everywhere logs in %AppData%\Fiddler Everywhere\logs\

• Check Administered port exclusions to see if port 8868 is restricted. You can check it with:

  netsh interface ipv4 show excludedportrange protocol=tcp
  

• If port 8868 is restricted,

  • You should also see the same issue with the non-patched official FE. Confirm this.
  • You can try removing port 8868 from Administered port exclusions.

You should also follow issue #44 ; Special tnx to @choneas.

If this didn't solve your problem, feel free to open an issue.