![Improve ease of configuring Git to work with corporate proxy · Issue #2789 · desktop/desktop · GitHub Improve ease of configuring Git to work with corporate proxy · Issue #2789 · desktop/desktop · GitHub](https://user-images.githubusercontent.com/10623872/48085878-7c9adc80-e1c9-11e8-8263-297d3de1db55.png)
Improve ease of configuring Git to work with corporate proxy · Issue #2789 · desktop/desktop · GitHub
![git clone https://XXX, but,Failed to connect to github.com port 443: Connection refused,Why? - Stack Overflow git clone https://XXX, but,Failed to connect to github.com port 443: Connection refused,Why? - Stack Overflow](https://i.stack.imgur.com/hfqQz.png)
git clone https://XXX, but,Failed to connect to github.com port 443: Connection refused,Why? - Stack Overflow
![QuPath-extension-biop-omero can't import images after successful login - Usage & Issues - Image.sc Forum QuPath-extension-biop-omero can't import images after successful login - Usage & Issues - Image.sc Forum](https://global.discourse-cdn.com/business4/uploads/imagej/original/3X/2/1/2106310e8da49ec72868d5734327853d2ce42490.png)
QuPath-extension-biop-omero can't import images after successful login - Usage & Issues - Image.sc Forum
![ios - Can't update cocoa pods Error: Failed to connect to github.com port 443: Connection refused - Stack Overflow ios - Can't update cocoa pods Error: Failed to connect to github.com port 443: Connection refused - Stack Overflow](https://i.stack.imgur.com/eqBfd.png)
ios - Can't update cocoa pods Error: Failed to connect to github.com port 443: Connection refused - Stack Overflow
![Git push => fatal: unable to access 'http://gitlab-ci-token.....': The requested URL returned error: 400 - GitLab CI/CD - GitLab Forum Git push => fatal: unable to access 'http://gitlab-ci-token.....': The requested URL returned error: 400 - GitLab CI/CD - GitLab Forum](https://global.discourse-cdn.com/gitlab/original/2X/1/1722063b807cd7c805314fa5a5a9be19a219a263.png)
Git push => fatal: unable to access 'http://gitlab-ci-token.....': The requested URL returned error: 400 - GitLab CI/CD - GitLab Forum
![Improve ease of configuring Git to work with corporate proxy · Issue #2789 · desktop/desktop · GitHub Improve ease of configuring Git to work with corporate proxy · Issue #2789 · desktop/desktop · GitHub](https://user-images.githubusercontent.com/10623872/48085923-963c2400-e1c9-11e8-8719-7a3277d9efd9.png)
Improve ease of configuring Git to work with corporate proxy · Issue #2789 · desktop/desktop · GitHub
![I think I have a bad SSL certificate and I cant authenticate a User in wazo-react-native - English - Wazo Platform I think I have a bad SSL certificate and I cant authenticate a User in wazo-react-native - English - Wazo Platform](https://canada1.discourse-cdn.com/free1/uploads/wazo_platform/original/1X/f4aea162afea3dde70efbf5a84368febb9374654.png)
I think I have a bad SSL certificate and I cant authenticate a User in wazo-react-native - English - Wazo Platform
![Using the GitHub self-hosted runner and Azure Virtual Machines to login with a System Assigned Managed Identity | Cloud With Chris Using the GitHub self-hosted runner and Azure Virtual Machines to login with a System Assigned Managed Identity | Cloud With Chris](https://www.cloudwithchris.com/images/cloud-with-chris-banner.png)
Using the GitHub self-hosted runner and Azure Virtual Machines to login with a System Assigned Managed Identity | Cloud With Chris
![Failed to load resource: the server responded with a status of 502 (Bad Gateway) - Get Help - Metabase Discussion Failed to load resource: the server responded with a status of 502 (Bad Gateway) - Get Help - Metabase Discussion](https://discourse.metabase.com/uploads/default/original/2X/3/311e87608f83191d8489ff3c32c3e28fd03c0807.png)