-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP Proxy Not Working #2371
Comments
Please provide a copy of the troubleshooting information page because it could be platform specific or triggered by a conflic with another addon. |
Same issue for me, with everything above 8.0.4 the http proxy setting gets completely ignored. |
+1 here. Never tried this feature before so can't say that is was ever working but it does't work for 8.0.7 for sure |
Name: Firefox Crash Reports for the Last 3 DaysFirefox FeaturesName: DoH Roll-Out Name: Firefox Screenshots Name: Form Autofill Name: Picture-In-Picture Name: Web Compatibility Interventions Name: WebCompat Reporter Remote Featuresbug-1680034-rollout-shirley-feature-roll-out-81-to-83-release-81-83: active Remote ProcessesType: Isolated Web Content Type: Privileged About Type: Extension Type: Privileged Mozilla Content Type: Isolated Service Worker Type: Preallocated Type: Socket Add-onsName: Add-ons Search Detection Name: Amazon.co.uk Name: Bing Name: DuckDuckGo Name: eBay Name: Firefox Multi-Account Containers Name: Google Name: Reddit Enhancement Suite Name: uBlock Origin Name: Web Developer Name: Wikipedia (en) Security SoftwareType: Microsoft Defender Antivirus Type: Type: Windows Firewall GraphicsFeatures Failure Log MediaAudio Backend: wasapi Enumerate database Environment VariablesMOZ_CRASHREPORTER_DATA_DIRECTORY: C:\Users\tom\AppData\Roaming\Mozilla\Firefox\Crash Reports Experimental Featuresabout:home startup cache (browser.startup.homepage.abouthome_cache.enabled): false Remote ExperimentsTCP rollout, Phase III (TCP on by default for 95% EXISTING Release profiles): control Important Modified Preferencesaccessibility.typeaheadfind.flashBar: 0 Important Locked Preferencesfission.autostart.session: true Places DatabaseAccessibilityActivated: false Library VersionsNSPR NSS NSSSMIME NSSSSL NSSUTIL SandboxContent Process Sandbox Level: 6 Startup CacheDisk Cache Path: C:\Users\tom\AppData\Local\Mozilla\Firefox\Profiles\pr91iioy.default-1556016294328\startupCache\startupCache.8.little Internationalization & LocalizationApplication Settings Remote Debugging (Chromium Protocol)Accepting Connections: false PrintingModified print settingsprint_printer: NPIF0AAC7 (HP LaserJet M15w) |
I am having this issue as well. HTTP proxies are useless for containers. Can't use my I2P proxy in a container because of it :( |
Is there any progress on this issue? |
Same issue here. I used to test proxy settings on a container a long time ago and now I find it doesn't work. It isn't platform specific because the original report is Windows, mine is Linux. Tested on Firefox from the distribution, even with a new profile. Tested too with a Mozilla built developer edition. The proxy logs don't show even a single try to use it. The extension has the permission to manage proxy settings too. |
Looks like the DNS leak "fix" from 8.0.5 is generating more problems that solving them. There was a try to solve it at #2278. I would have reverted it until the problem with that patch was found. |
This issue also seems to exist on Mac as well; any proxy URL set up is completely ignored and traffic is routed around it as far as I can tell. This extension is working in the mean time, but I don't see why this is a feature of multi-account containers plugin yet seems to have almost never worked since release |
Before submitting a bug report
Provide a copy of Troubleshooting Information page
N/A
Step to reproduce
Actual behavior
HTTP proxies are not working
Expected behavior
HTTP proxies should be honoured
Additional informations
SOCKS proxies seem to still be working. Just HTTP affected it seems. I have rolled back to v8.0.4 temporarily and HTTP is working as expected.
The text was updated successfully, but these errors were encountered: