Have you checked our README?

• I have checked the README

Have you followed our Troubleshooting?

• I have followed your Troubleshooting

Is there already an issue for your problem?

• I have checked older issues, open and closed

Have you checked the discussions?

• I have read the Discussions

Have you ACTUALLY checked all these?

YES

Environment

- FlareSolverr version:
- Last working FlareSolverr version: -
- Operating system: Windows 11
- Are you using Docker: No. I am using flaresolverr.exe
- FlareSolverr User-Agent (see log traces or / endpoint):
- Are you using a VPN: No
- Are you using a Proxy: Yes
- Are you using Captcha Solver: No
- If using captcha solver, which one:
- URL to test this issue:

Description

Proxy authentication via Chrome extension fails on servers with public IP addresses, causing requests to bypass the proxy and use the server's direct IP. The same proxy configuration works correctly on machines behind CGNAT (without direct public IP).

Affected: Servers with public IP addresses (tested on multiple servers)
Working: Machines behind CGNAT without direct public IP (tested on multiple machines)
Proxy Provider: iProyal (geo.iproyal.com:12321)
Proxy Type: HTTPS proxy with username/password authentication

The proxy credentials and connectivity are verified working (curl/Postman tests succeed)
The issue is consistent across multiple servers with public IPs
The issue does not occur on CGNAT machines
No session parameter is used in the requests (fresh WebDriver instance each time)
Chrome version differences may also be a factor, but the network environment (public IP vs CGNAT) appears to be the primary differentiator

Logged Error Messages

No logged error during send request to flaresolverr

Screenshots

No response