brotherbeagle

I'm in the same boat. Nginx is passing traffic along as expected to both, both containers are available to each other (pingable, wget pulls an index.html, etc...). That said, the OnlyOffice container is not behaving correctly (it refuses to acknowledge its modified http port and continues to refer to '8080' (hovering above the Webgui link in the dashboard shows it's identifying at 8080, vs my directed 8088) and the log clearly states the refused connection: 2020/02/20 18:12:50 [error] 699#699: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.19.0.6, server: , request: "GET /healthcheck HTTP/1.1", upstream: "http://127.0.0.1:8000/healthcheck", host: "docserver.xxxx.xxx:443") <-- and that's annoying as connecting directly to https://docserver.xxxx.xxx gives me a big, ol' happy: Document Server is running. I haven't looked beyond this yet and probably won't have a chance until next week -- but I thought it would be worth it to mention that it doesn't appear to be an issue with the Nextcloud container (which is working fine on my end -- though, it is much slower/less responsive than it was before 18.0.1 and that's on a fresh install with the database housed on my stable, production MariaDB instance over on one of my Proxmox nodes...).