Can't access Nextcloud-aio

ℹ️ Support
1

OS: fedora 40 KDE
Nextcloud: Nextcloud-aio latest image in docker

What I tried: Couldn’t pass the domain check, so created a dummy domain “tailscale_ip my-nextcloud.local” in /etc/hosts, also made openssl certs and key for it, but still can’t access “https://tailscale_ip:8080”.

Docker Apache logs say:

``
2024-10-24T10:26:46.703410342Z {“level”:“error”,“ts”:1729765606.7029934,“logger”:“tls.obtain”,“msg”:“will retry”,“error”:“[my-nextcloud.local] Obtain: subject ‘my-nextcloud.local’ does not qualify for a public certificate”,“attempt”:4,“retrying_in”:300,“elapsed”:300.003909145,“max_duration”:2592000}

``

I know my-nextcloud.local does not qualify for a public certificate, and I don’t even wanna use it. Just setup my nextcloud on local network!!!

Any tips?

Thanks

2

Maybe this helps? Tailscale (and Caddy as a sidecar) Reverse Proxy · nextcloud/all-in-one · Discussion #5439 · GitHub

3

Cool, but can’t I just use Nextcloud-aio without doing any domain check? I am very happy to just use localhost:8080.

But I couldn’t get rid of the domain check screen, so I tried tailscale, but again, that path was dreadful enough

4

This is not possible

5

Maybe you want to check Nextcloudpi?
It is no problem running Nextcloud only local.

6

@geoW NextcloudPi is cool, I have experimented with it in past.

I also am pretty confident with using nextcloud (Non-AIO) method, where I define services in docker compose.
I know it won’t have official support as Nextcloud-AIO, but is it okay to use non-AIO method? will it get updates or AIO will be only way in future
Thanks for your time!

7

Your server - your rules.
See it as a wrapper of a nextcloud instance, the maintainer cares most about updating, that comfort is nice, but the vulnerable spot is the project is a one man show at most.
Nevertheless it is much worth running a nextcloudpi instance.

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.