This will "trick" GitKraken into thinking a proxy is not necessary and will not attempt to use it for local traffic. Modify your Proxy Auto Configuration (PAC) file to return DIRECT (no proxy) for the GitKraken update servers.You should be able to perform actions as normal. Open GitKraken, wait for it to fully start. You can turn off all proxies via Internet Options > Connections > LAN Settings. Temporarily disable your proxy configuration when you open GitKraken.How can I resolve this and be able to interact with my remotes? It incorrectly re-uses the proxy configuration from the update check for internal repositories. When you attempt to perform an action on a remote this lookup does not happen again. In this case, you likely use a proxy for external internet access to this connection occurs via your proxy. Before it connects it determines how to connect to it via the PAC file. When GitKraken starts it connects to its update servers. GitKraken (or one of the libraries it uses) appears to be incorrectly assuming proxy settings. Why is GitKraken using an external proxy for internal addresses? GitKraken (or one of the libraries it uses) is reading this file and determining how to contact external systems. In your case it looks like you have configured a PAC file in the "Automatic configuration" section. GitKraken is automatically pulling proxy configuration from your system's proxy settings (Internet Options > Connections > LAN Settings). Why is GitKraken using a proxy when I haven't configured one?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |