Hi everybody!
We’re experiencing weird and unpredictable behavior on some of our services:
Cockpit:
- There seems to be random issues with the Websocket-Connection. Most of the time, the application will fail, however hitting F5 will eventually fix this issue (after multiple tries)
- it appears, pritunl-zero is swallowing some of the Websocket-messages after the first (micro-)seconds of the connection, making the page unusable and unpredictable.
Cockpit works fine: - inside the local Network
- outside the local network when running via nginx proxy manager
- outside the local network when running via cloudflare tunnels/cloudflare zero-trust
Pritunl-Zero logs do not show anything at all.
We’re running some OctoPrint instances:
- once again: accessing it locally, via cloudflare and via proxy-manager works perfectly fine
- the page will sometimes simply work, most of the time not work at all (502), sometimes show the login screen and then not proceed after Login.
- If one of the issues arise, hitting refresh will not help
- if the login shows, but the page won’t succeed, Browser dev-tools show a Websocket termination before connection was established
- if the page doesn’t work at all, we get “http: proxy error: net/http: timeout awaiting response headers\n” in the pritunl-zero logs → The webserver itself will not see the request at all.
- if the login fails, we get a Proxy Serve error with the following stack:
Is this a known issue and is there a workaround available?
Note that this is not a long request timeout issue.