-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Socket connection closed! - Docker image behind apache #306
Comments
could you try setting KeepAliveTimeout to some very high value? |
I tried after setting it to 3600 but still same error... I think it is the proxypass settings that are messed up and I don't know what these should be - I am just guessing it based on the caddy conf in your guidance you see...
|
oh, so it's not working at all? it's not just that the connection closes after awhile? |
Yep not working at all... just the web page showing the error reported in my first message |
Would you please be able to suggest apache config for websocket like you have done for caddy and I can give it a shot before completely giving up :( |
Running docker image behind apache server, I get the error:
running the docker on port 3010 and then doing a proxypass and proxypassreverse etc using following:
I have tried variations to above configuration by commenting line 4 and / or 5, removing websocket in end of 4 and 5 but no joy. I am certain it is the Apache config that is causing this issue but I dont know how / what do i need to change. I have to use Apache and cannot use Caddy as shown in the example
The text was updated successfully, but these errors were encountered: