Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

VPN network unaccessible with Firefox multiple profiles

  • 1 răspuns
  • 1 are această problemă
  • 5 vizualizări
  • Ultimul răspuns de 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?

Toate răspunsurile (1)

john277
john277 Deținătorul întrebării
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.