GitHub Desktop forgets the GitHub Enterprise server URL
See original GitHub issueDescribe the bug
Our GitHub Enterprise server is behind the company firewall and only accessible via VPN.
With the recent versions of GH Desktop (Since 2-3 weeks ago approx), every time I log off of VPN, GH desktop forgets my enterprise URL and I have to type it again.
While its expected that GH won’t be able to communicate with the enterprise server when its not accessible, having to manually type in the URL every time I reconnect to VPN is tedious - And was not required with previous versions of the desktop tool.
Version & OS
Version 2.9.3 (x64)
Mac OS Big Sur
Steps to reproduce the behavior
- Confirm GH Enterprise server is configured in preferences:
-
Disconnect from VPN so that GH Enterprise is not available to GH desktop.
-
Try to fetch origin, error message is shown (correctly) since GH Enterprise is not reachable.
-
You get an error that the account token is invalidated. This is actually not entirely accurate - Account token is still valid, just that the service is not reachable:
-
Click “No” (Not on VPN now, no need to try again)
-
Connect to VPN again - GH Enterprise is reachable
-
Click “Fetch Origin” again - Error message shows up. Click “Open Preferences”
-
GH Enterprise is completely forgotten, need to type the URL again to use GH desktop:
Expected behavior
I should be able to use GH Desktop with and without access to GH Enterprise for local development, and not have to re-type the Enterprise URL every time.
Actual behavior
Need to provide the GH enterprise URL on every connection to VPN.
Screenshots
Screenshots added above.
Logs
2021-09-10.desktop.production.log
Attach your logs by opening the Help
menu and selecting Show Logs...
, if applicable.
Additional context
Add any other context about the problem here.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top GitHub Comments
Works like a charm! Thanks @sergiou87 and @steveward !
@sergiou87 - Confirmed! No GH headers whatsoever. Looking forward to testing your fix. Thanks so much for getting this resolved so quickly.