- Joined
- Feb 2, 2018
- Messages
- 1,401
Hi Blueether,
As a test, what is the answer when you connect your Nextcloud directly with HTTPS://10.1.1.55 ?
Do you have the same error message ? If you do, then the problem is clearly in the Nextcloud config. It may be the base URL of your cloud being /nextcloud, the need for a trusted name in Nextcloud's config.php that will match the name you use to call your proxy or similar.
Here, my Nextcloud is running from a Docker in a separate host, my reverse proxy is HAProxy and files are mapped from FreeNAS over NFS. My setup is pretty different but at the end, everything should go to the same variables.
As a test, what is the answer when you connect your Nextcloud directly with HTTPS://10.1.1.55 ?
Do you have the same error message ? If you do, then the problem is clearly in the Nextcloud config. It may be the base URL of your cloud being /nextcloud, the need for a trusted name in Nextcloud's config.php that will match the name you use to call your proxy or similar.
Here, my Nextcloud is running from a Docker in a separate host, my reverse proxy is HAProxy and files are mapped from FreeNAS over NFS. My setup is pretty different but at the end, everything should go to the same variables.