-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Nginx reverse proxy configuration gives 502 bad gateway #38
Comments
Possible error during docker compose up: That might be linked to 379d74a : EDIT Quickfixing the previous sed issue will not solve my problem. |
Can you confirm what version you are using? I am not seeing it on the past few releases. |
compose.yml : |
Can you try using a tagged release - |
I do have the same results with Sed error:
Connection still refused (I forced wildcard * in the hosts to ne sure this was not the problem):
|
Thanks - to look into the erroneous sed command as a bug fix on Monday. |
I am not able to recreate the sed error on my copy here. It was an issue in earlier releases but not in the latest I wrote about above. I will keep looking. |
Summary
Getting 502 bad gateway. Docker container seems rejecting the requests.
Steps to reproduce
What is the expected correct behavior?
Collabora access; not a 502 Bad Gateway.
Relevant logs and/or screenshots
Question
I am not able to make the container work with a nginx reverse proxy (that is working with other services).
Would you have an example of a working nginx configuration ?
Looking a my nginx log there is a
111: Unknown error
but I was not able to get more intel on docker log side (even increasing the log level tiinformation
).Any advice welcome :)
The text was updated successfully, but these errors were encountered: