We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Firefix 119.0.1 on Android connecting to wrong port on proxy server

  • 4 replies
  • 0 have this problem
  • 1 view
  • Last reply by mozilla235

mozilla235
mozilla235
more options

As of yesterday (1st Nov 2023), Firefox started reporting "Proxy Server Refused Connection" when trying to browse websites over Wifi.

I have a proxy server configured in my phone wifi settings, and this has worked before, and still works in other apps (Chrome, etc)

Checking with tcpdump on the proxy server itself, I see my phone trying to connect to port 80, rather than the configured port (8000)

Firefox version: 119.0.1 Phone: Samsung Galaxy S22 Android version: 13

As of yesterday (1st Nov 2023), Firefox started reporting "Proxy Server Refused Connection" when trying to browse websites over Wifi. I have a proxy server configured in my phone wifi settings, and this has worked before, and still works in other apps (Chrome, etc) Checking with tcpdump on the proxy server itself, I see my phone trying to connect to port 80, rather than the configured port (8000) Firefox version: 119.0.1 Phone: Samsung Galaxy S22 Android version: 13

Chosen solution

I've switched to using the 120 Firefox Beta, and it's now working.

That will do as a work-around until it's fixed on 119, or 120 is released.

Read this answer in context 👍 0

All Replies (4)

mozilla235
mozilla235 Question owner
more options

Update: reconfiguring the proxy to also listen on port 80 is a temporary workaround. Not a long-term solution though.

Modified by mozilla235

mozilla235
mozilla235 Question owner
more options

Chosen Solution

I've switched to using the 120 Firefox Beta, and it's now working.

That will do as a work-around until it's fixed on 119, or 120 is released.

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Thank you for letting us know, hopefully this is included in Firefox for Android 120 which is due out very soon.

mozilla235
mozilla235 Question owner
more options

Note: now fixed in the stable Android Firefox release, version 119.1.1