Hey everyone! I'm currently trying to set up Gotenberg alongside Paperless-NGX using Docker on WSL with Docker Desktop to manage my business documents. The Paperless-NGX setup works flawlessly, but as soon as I add the Gotenberg image to my Docker Compose file, I encounter a 502 Bad Gateway error during deployment. The error message indicates a problem when trying to access the API route, saying it can't find the required API version. I've shared my Docker Compose configuration below and would appreciate any help troubleshooting this issue. I've already confirmed that running Gotenberg directly with the Docker run command works fine, so it seems like the problem is isolated to the compose setup. Thanks for your insights!
1 Answer
It sounds like you're facing a reverse proxy issue that's causing the 502 error. Just to clarify, when you do a `docker pull gotenberg/gotenberg:8`, it works fine, but using it within Docker Compose is where things go wrong. Make sure to check your WSL and Docker settings too—sometimes, Windows networking quirks can mess things up. Try running `wsl --status` and `docker info` to see if anything stands out. Also, do you have any corporate proxies or caching that could be affecting the setup? That could definitely cause issues.
Haha, yeah, I actually do plan to set up a dedicated machine soon! So far, Docker Desktop has worked well for me, but I’ll definitely take a look at those commands to check my settings. No corporate proxies running here, so that shouldn’t be the issue.