Firefox shows "Proxy Server Refused Connection" when using VPN
Categories
(Fenix :: General, defect)
Tracking
(Not tracked)
People
(Reporter: fireattack, Unassigned)
References
Details
Steps to reproduce:
I often use VPN on my phone for certain circumstances. I've been using the same VPN for years, and it worked fine with Firefox.
Recently I found that as soon as I enabled VPN, Firefox failed to connect to the Internet.
Every page shows "Proxy Server Refused Connection".
- I have zero network issues with any other apps. Firefox is the only app having this issue.
- I've tried Release, Beta, Nightly, no difference.
- I've tried clean all the data, reinstall, etc., no difference.
Something interesting: the home page of Firefox seems to still have Internet access as it can load these Pocket "stories" just fine. But as soon as I started to open any website, it immediately shows "Proxy Server Refused Connection".
I firstly posted it to Reddit (https://www.reddit.com/r/firefox/comments/1714d3l/android_firefox_shows_proxy_server_refused/) and some other users say they have the same issue.
One particular report from user baddy_movin is:
I'm running a proxy on my home network and I have the same issue: instead of using the proxy configured in wifi settings (i.e proxy.mynetwork:8080) I did a capture and Firefox is using TCP 80 to connect to proxy so it fail.
Firefox is the ONLY app having such issue. All others are using the proxy. It's recent, probably less than a week.
So it looks like Firefox isn't respecting port number of the HTTP proxy given.
Actual results:
The Firefox is unable to visit any website when a VPN service is enabled.
Expected results:
Firefox should be able to visit the Internet.
Reporter | ||
Comment 1•1 year ago
|
||
I use: Pixel 7, Android 13.
Tested and reproduced the bug with Firefox 118.1.1, 119.0b5, and 120.0a1.
Comment 2•1 year ago
|
||
this sounds like bug 1853574 , although it's under mobile data.
both share the same problem: port of the proxy is wrong (may be set to default).
Could you help finding the latest working version (and the first not-working version if possible) ?
if you found , please also attach geckoview' version number (you could find it in settings -> about firefox -> the line start with GV: )
Reporter | ||
Comment 3•1 year ago
|
||
I went back to ver. 98 and it's still broken. I didn't remember it being not working for that long.
Is it possible it's due to some Android system changes than Firefox changes? I update my OS monthly patch.
Comment 4•1 year ago
|
||
Could you provide your device info like model, android version, patch version? Thanks.
Reporter | ||
Comment 5•1 year ago
|
||
I've already said it above, but it's a Pixel 7 with its stock Android 13 + security update up to September 2023.
Reporter | ||
Comment 6•1 year ago
|
||
It looks like the VPN app I use also adds a system proxy at non-80 port (127.0.0.1:xxxx), so it's consistent with baddy_movin's issue.
Comment 7•1 year ago
|
||
I'm having the same issue on my phone. I am using Shadowsocks with the V2RayNG and Clash apps.
I can use VPN and connect with all other apps and other browsers, only Firefox doesn't work. It instantly fails and doesn't even try to connect.
Can't even connect to 1.1.1.1.
I'm on a Note 20 if it matters.
Comment 8•1 year ago
|
||
Also I should note this issue only started in the last week or so. Before never had any issue with VPN for years, with same VPN provider and apps.
Comment 9•1 year ago
|
||
I also haven't updated Android in a few months, and the VPN apps didn't update before the error, so it's most likely a Firefox app issue.
Reporter | ||
Comment 10•1 year ago
|
||
If you go https://support.mozilla.org/ you can see lots of people having this issue since last week:
https://support.mozilla.org/en-US/questions/1425893
https://support.mozilla.org/en-US/questions/1426275
https://support.mozilla.org/en-US/questions/1422403
Could we consider increasing the severity of this bug since it causes Firefox to become completely unstable?
Thanks in advance.
Comment 11•1 year ago
|
||
I faced exactly the same issue after upgrading to Android 14 today. And actually this problem had happened before the upgrade several times on Android 13 on my phone, but a factory reset could fix that. However, even on a freshly installed Android 14 the issue exists.
As a workaround, one can install the foxyproxy standard add-on and set a proxy manually. Hope that this bug will be fixed soon.
Comment 12•1 year ago
|
||
The severity field is not set for this bug.
:jonalmeida, could you have a look please?
For more information, please visit BugBot documentation.
Comment 13•1 year ago
|
||
It should be fixed in Nightly 121. Feel free to reopen.
Reporter | ||
Comment 14•1 year ago
|
||
It is fixed, thanks.
I see it was backported to beta, would it be backported to stable?
Comment 15•1 year ago
|
||
(In reply to fireattack [:fireattack] from comment #14)
It is fixed, thanks.
I see it was backported to beta, would it be backported to stable?
I am already requesting it to 119. " approval-mozilla-release?" in bug 1858377 means it. Please watch bug 1858377
Description
•