Hi!
First of all thank you so much for helping. It works now! I’ll explain in detail so whoever stumbles upon this problem might find it helpful.
TL;DR
I’m 90% certain the problem is #2 and #3. Things that changed:
- Updated Nextcloud
v10.2.0→v10.3.0. - Issues with Caddy & Nextcloud conflict on
:11000port binding. APACHE_IP_BINDINGto0.0.0.0. I have tried this in the past with and without Caddy, maybe it wasn’t applied properly.
Here’s a diagram I created on my faulty setup:
In theory should it work though? I am just curious what’s with the
content-length: 0.
To answer your questions:
- Caddy reverse proxy:
- is used for local access mainly. I want to reach my own server when I’m at home without reaching the internet.
- Secondly, my VPS responds with
connection refused. That’s why I thought Caddy was necessary. Please see my other diagram below with Caddy from external access removed.
The issue I think is Apache is not binding to the right IP or Caddy port :11000 conflict. After changing the APACHE_IP_BINDING env to 0.0.0.0 again and removing that part from Caddy works flawlessly.
Once again, thank you for your help!