allow to run it in a subdirectory with reverse proxy

[tramir]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Steps to reproduce

1. Set up reverse proxy following the guidelines for nginx, with the only difference that the location is /nextcloud instead of /
2. Create the AIO container with the suggested settings (APACHE_PORT=11000)
3. Start the AIO container. Type in the domain that will be used for Nextcloud.

Expected behavior

The setup continues and the nextcloud containers are created.

Actual behavior

Error: Domain does not point to this server or the reverse proxy is not configured correctly. See the mastercontainer logs for more details. ('sudo docker logs -f nextcloud-aio-mastercontainer')

Host OS

Synology DSM 7.1

Nextcloud AIO version

Nextcloud AIO v1.4.1

Current channel

N/A

Other valuable info

I suppose this behavior is to be expected, because the domain itself points to something else. Only the subdirectory would point to the nextcloud instance. But the setup process doesn't allow me to enter a domain/subdirectory (error: Domain is not a valid domain!). The setup continues if I change my reverse proxy setup to point / to the nextcloud instance. But I'd really like to be able to use a subdomain. How should I proceed?

[szaimen]

The easiest workaround for now would be pointing another subdomain onto your home network...

[szaimen]

okay great! This looks good in general! However it seems like the mastercontainer is not able to connect to the configured subdomain to get the correct value. Maybe for a test try to restart the mastercontainer and see if it works now?

[tramir]

Thanks for the quick reply! I restarted the container, but still have the same error. One thing I noticed is that, if I try to wget the same address that aio-domaincheck seems to be using (https://XXXXX:443), I get a certificate error unless I use --no-check-certificate. Does aio-domaincheck require a valid certificate?

[szaimen]

Does aio-domaincheck require a valid certificate?

yes. Don't you have one?

[tramir]

I didn't. I do now :) And I'm able to move on. Maybe this should be added to the documentation? I know it's easy to get a Letsencrypt cert, but it wasn't obvious to me that it was needed. But maybe it's just because it's late here :)

In any case, many many thanks for all the help -- and for a great idea and product!

[szaimen]

I'll try to improve the logging with #859

[szaimen]

Another possibility is this: https://github.com/nextcloud/all-in-one/tree/main/manual-install

[tramir]

Thanks for suggesting this. I took a look at the manual install and I'm not sure what I should tinker with to get this done. It seems the process still requires a domain ($NC_DOMAIN) with no possibility that I can see for a subdirectory. At least that's what the Caddyfile and the test in start.sh seem to do. Would you have any guidance?

[tramir]

I'd really like to get this working because I think AIO is a super great idea. And I had nextcloud running in a subdirectory until now on a debian machine with the same reverse-proxy setup as the one I'm trying now. I have no experience with caddy though...

[ManOki]

see #1672 and this