TomBursch
commented
3 months ago Your config and logs look good. It is most likely something wrong with your reverse proxy setup/config.
Closed thatso closed 3 months ago
TomBursch
commented
3 months ago Your config and logs look good. It is most likely something wrong with your reverse proxy setup/config.
thatso
commented
3 months ago Thanks for your confirmation of my docker file. I'm still wondering what's wrong, but at least now I can focus on the proxy. Do you BTW plan to publish the AIO container #373 anytime soon?
Karamellwuerfel
commented
3 months ago @thatso Did you find the error? I've the same issue with jwilder nginx proxy. My docker-compose config file looks like yours but I get an 502 error and can't find any solution. Thank you guys!
Karamellwuerfel
commented
3 months ago I found the solution for me in #201 and my compose file is:
version: "3"
services:
kitchenowlfront:
image: tombursch/kitchenowl-web:latest
container_name: kitchenowlfront
restart: unless-stopped
depends_on:
- kitchenowlback
environment:
- BACK_URL=kitchenowlback:5000
- VIRTUAL_HOST=kitchen.[hidden].de
- LETSENCRYPT_HOST=kitchen.[hidden].de
- LETSENCRYPT_EMAIL=info@[hidden].de
- WEBROOT=/var/www/web/kitchenowl
kitchenowlback:
image: tombursch/kitchenowl:latest
container_name: kitchenowlback
environment:
- JWT_SECRET_KEY=secret
ports:
- 5000:5000
volumes:
kitchenowl_data:
networks:
default:
external:
name: nginx-proxyNeeded the ports: - 5000:5000.
Thank you!
thatso
commented
3 months ago @Karamellwuerfel : this is great news!
Where did you find the webroot environment definition?
Also, according to this comment, I deemed the port 5000 definitions not necessary. Interesting find!
Still waiting for the AIO container though in the hope it will simplify the setup even more. :wink:
Karamellwuerfel
commented
3 months ago @thatso: I used the webroot and the other environment variables except BACK_URL from and for my nginx proxy configuration. The nginx proxy is from jwilder (Docker Hub).
I tried without port 5000 but it didn't work and I got the 502 error again. When I added it, everything works. 👍
The AIO was (I think) merged today and you can use the BETA in the docs. 😺
TomBursch
commented
3 months ago Awesome that you've found a solution. I've merged the docs for the AIO container and will publish the corresponding release later today 😃
thatso
commented
2 months ago For later reference and future readers: this is my currently working docker compose file with the npm network referring to a separate Nginx Proxy Manager container:
services:
kitchenowl:
image: tombursch/kitchenowl:latest
container_name: kitchenowl
restart: unless-stopped
environment:
- JWT_SECRET_KEY=[redacted]
volumes:
- data:/data
networks:
- npm
volumes:
data:
name: kitchenowl_data
networks:
npm:
name: nginxproxymanager_default
external: true@TomBursch: your AIO container seems to work fine, thanks! :+1:
Is this urgent?
No
What parts are affected
Frontend
What is the server version
docker latest
What is the client version
docker latest
What platform are you using
Web
What's the problem 🤔
I'm trying to run KitchenOwl in docker behind a ngnix SSL reverse proxy, however I only get
502 Bad Gateway openresty. Most likely, I'm only missing some detail. The docker compose file seems to resemble the one in the docs.Share your logs
Share your configuration