Hide Forgot
Description of problem: Chrome cannot login to registry console when System system proxy is set. Unset system proxy, it can login. The Chrome used is ver 54. For Firefox, a bit complex, see more info below See related attachments As comparsion, console such as openshift console does not have the issue. Version-Release number of selected component (if applicable): cockpit 118 registry.ops..../openshift3/registry-console 3.3 f8a757a055c5 10 days ago 223.8 MB How reproducible: Always Steps to Reproduce: 1. Set OS system proxy 2. Login to registry console with Chrome, input user/password. Actual results: 2. A circle is spinning a while, then the login fails and page returns "Reconnect". Expected results: 2. Should login successfully Additional info: For Firefox (version used is 49), in its Network setting: If check the option "Manual proxy configuration", input proxy, the problem does not occur, Firefox can login to registry console. If check the option "Use system proxy settings", and set OS system proxy, the problem occurs, Firefox can not login.
Created attachment 1221817 [details] Set-system-proxy-step1
Did your last attempt use a build with cockpit >= 122-3? Does your proxy support WebSockets?
I think the proxy you are using doesn't support websockets. How are you testing the openshift console? Unlike cockpit only some parts of the openshift console use websockets, so you have to navigate around. In my testing with your proxy settings, both cockpit and the parts of openshift that use websockets failed. You can see the failures in the network tab of chrome dev tools (see screen shot)
Created attachment 1222797 [details] Origin WS failure
Tried Origin websocket, got WS failure too. So seems the problem reported is not cockpit issue. May close it?
Thanks for verifying. I will close this as it's not a bug in Cockpit.