This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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.

VPN network unaccessible with Firefox multiple profiles

  • 1 reply
  • 1 has this problem
  • 5 views
  • Last reply by john277

john277
john277
more options

Hello,

I have Firefox with two profiles, Personal and Work. I also have a VPN provided by the company which is setup on Windows 10 as a Public Network, on both profiles the network settings are the same and while the Personal has anti ads and privacy plugins, the Work doesn't have a single plugin.

My issue is that the Personal profile is able to use the VPN and access the work network while the Work profile is not. With both network settings matching, are there any settings in the About:config that i can check that would co-relate with the issue that i'm having?

Hello, I have Firefox with two profiles, Personal and Work. I also have a VPN provided by the company which is setup on Windows 10 as a Public Network, on both profiles the network settings are the same and while the Personal has anti ads and privacy plugins, the Work doesn't have a single plugin. My issue is that the Personal profile is able to use the VPN and access the work network while the Work profile is not. With both network settings matching, are there any settings in the About:config that i can check that would co-relate with the issue that i'm having?

All Replies (1)

john277
john277 Question owner
more options

After a bit more investigation i've found out there's only some internal domains that i'm not able to access it, mainly because Firefox keeps forcing HTTPS into a internal domain that does not have the HTTPS port available.