Mozilla Firefox slows down when disconnecting from VPN GlobalProtect
I use Mozilla Firefox for work. Part of my work requires I use the GlobalProtect VPN client. When I log on to the VPN, everything appears to be fine. The problem arises when I log out of the VPN client, such as needing to switch to a different VPN.
When I log out of the VPN client, Mozilla slows down massively. I get the following errors when trying to access websites.
PR_END_OF_FILE Timeout
I thought it was a DNS issue, but the change I made previously did not prove to be a reliable fix, and I do not actually know the root cause of what is happening. Firefox returns to normal ONLY after a full computer restart. At this point I am considering switching browsers as, despite Firefox's functionality, it is starting to interfere with my work.
I have used other VPNs, such as Fortigate VPN, and not encountered anything like this.
Any advice or guidance would be appreciated.
Vybrané riešenie
The solution: It was a specific website I was visiting when disconnecting from the VPN. Specifically I have a vCenter dashboard at the other end of the tunnel, and I have gone multiple days disconnecting from the VPN.
However all symptoms disappeared once I no longer kept the vCenter dashboard open. I think the dashboard was interacting with firefox in a bad way, especially as it requires an on-prem DNS server for routing. Once that tunnel is gone, it beats the browser into the ground and prevents it from functioning. I do not know if this needs to be elevated to the devs or not.
Either way I am closing out my question.
Čítať túto odpoveď v kontexte 👍 0Všetky odpovede (2)
Update: I waited about an hour and it seems the issue has resolved on its own? Was the browser waiting for something that the VPN disconnect interrupted?
Vybrané riešenie
The solution: It was a specific website I was visiting when disconnecting from the VPN. Specifically I have a vCenter dashboard at the other end of the tunnel, and I have gone multiple days disconnecting from the VPN.
However all symptoms disappeared once I no longer kept the vCenter dashboard open. I think the dashboard was interacting with firefox in a bad way, especially as it requires an on-prem DNS server for routing. Once that tunnel is gone, it beats the browser into the ground and prevents it from functioning. I do not know if this needs to be elevated to the devs or not.
Either way I am closing out my question.
Ak chcete odpovedať na príspevky, musíte sa prihlásiť do svojho účtu. Ak ešte nemáte účet, položte novú otázku.