brixomatic
opened 1 year ago
-
Never tested with HAProxy. Please disable SSL temporarily to see if the problem still exists.
-
I have tried various things now, like disabling all the options and timeouts I made in the haproxy.cfg, and the problem occurs only for HTTPS -> HTTP. The error will not occur, if I change the configuration to to HTTP -> HTTP, like this
# bind *:6444 ssl crt /usr/local/etc/ssl/mycertificate.pem bind :6444Of course I need to have an SSL connection, so I can't really run with this settings. But it might be valuable to find the root cause of this.
Also I've learned that the error can be triggered by just reloading the Server Log view.
I will investigate further and update my results here, shall I find any setting to solve this for future reference. Any help is of course greatly appreciated, that's why I posted the docker-compose file along with the config, so a lab can be quickly set up (just requires downloading the 'ssl-dh-param-file', as described, and putting it into its place at
/etc/haproxy/haproxy_dhparams.pem. A self-signed certificate for testing will probably suffice. -
For future reference: I did solve the problem eventually by creating a second backend to handle websockets:
acl hdr_connection_upgrade hdr(Connection) -i upgrade acl hdr_upgrade_websocket hdr(Upgrade) -i websocket acl websocket_url path_beg -i /wicket/websocket http-request set-header Upgrade websocket if hdr_upgrade_websocket http-request set-header Connection upgrade if hdr_upgrade_websocket use_backend onedev_websocket if hdr_connection_upgrade hdr_upgrade_websocket websocket_url default_backend onedev backend onedev mode http option forwarded proto host by by_port for option forwardfor http-request set-header X-Forwarded-Proto https if { ssl_fc } server onedev_http_server onedev:6610 maxconn 2048 backend onedev_websocket mode http option forwarded proto host by by_port for option forwardfor http-request set-header X-Forwarded-Proto https if { ssl_fc } server onedev_http_server onedev:6610 maxconn 2048 ws h2The "ws h2" setting was the vital part.
Now I just need to clean the config up.
-
Previous Value Current Value Open
Closed
-
Thanks for sharing! Definitely useful for users running OneDev behind HAProxy.
| Type |
Question
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Clicking through projects and builds, opening a build, my server logs gets spammed with errors like these:
HProxy config (parts):
docker compose.yaml:
System settings are set to:
Server URL:
https://my_domain.example:6444(using my real domain of course)
SSH root URL:
ssh://my_domain.example:6511Security settings set to:
CORS Allowed Origin:
https://my_domain.example:6444I don't see any obvious mistake in my setup. Requests are handled almost immediately, so don't think HAProxy's timeout is the problem. Also, as I'm still setting up the system, I'm the only user and there is no load on the System. What would cause this problem?