Skip to content
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

MAC + Mozilla VPN broke after FF update with "The proxy server is refusing connections" #2610

Open
2 tasks done
lleevveell66 opened this issue Jan 28, 2024 · 1 comment
Open
2 tasks done
Labels
bug Something is broken!

Comments

@lleevveell66
Copy link

Before submitting a bug report

  • I updated to the latest version of Multi-Account Container and tested if I can reproduce the issue
  • I searched for existing reports to see if it hasn't already been reported

Step to reproduce

-2. Windows 10 Pro
-1. Solution with FF + MAC + Mozilla VPN, where each container is dedicated to an online identity's browsing and is set to exit through a different MozVPN egress. (e.g., JohnDoe container exits through Denver, JaneDoe exits through Miami, etc.)

  1. FF updated to 122.0 (64-bit)
  2. Checked updates for all extensions (there were no updates for them.)
  3. Check updates for MozVPN (also none)
  4. Every container now gives "The proxy server is refusing connections" for every site.
  5. Only non-containerized tabs will get anywhere (they are using the default egress for MozVPN)

Actual behavior

Every containerized tab now gives "The proxy server is refusing connections" for all sites. Only non-container tabs work. Those default to the main MozVPN egress point. I've tried changing some of the containers to use that egress to no avail.

Expected behavior

Open each user's container and go.

Additional informations

I've tried killing FF and bringing it back up, same with MozVPN, and same with entire machine. I've tried changing MozVPN egress to many things on each container. It's just not working. Nothing has changed with any proxy anything on this machine. That error appears to not really be referring to any proxy settings, as there are none (other than "auto").

I am unsure which wheel in this arangement is squeaking, but it feels like MAC, thus the bug report. Mostly, I conclude this because non-MAC tabs still work fine, and they go through MozVPN, as well.

Let me know if you would like any more information gathered. I am happy to provide it after some scrubbing of PII, of course.

Provide a copy of Troubleshooting Information page (optional)

No response

@lleevveell66 lleevveell66 added the bug Something is broken! label Jan 28, 2024
@lleevveell66
Copy link
Author

OK, well... nevermind. It just started working. I didn't change anything, only refreshed a containerized tab and -bam-. Possible MozVPN outage? But the normal tabs were working through it. No idea. Sorry for the bother!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken!
Projects
None yet
Development

No branches or pull requests

1 participant