Cleb

I also tried installing nextcloud AIO using a Cloudlfare tunnel instead of Tailscale. I followed Spaceinvador One’s recent video guide on it, but ran into networking issues again. I had the same issue and fixed it by changing the unraid webgui port number from 443 to something else not in use. This can be done in the “Management Access” settings in the unraid webgui. If the webgui is already broken for you the following method will also work: I also faced the issue with Collabora being broken. From diving into container log files there was another network related issue (a wget for initial collabora setup was throwing errors, if I remember correctly). None of nextcloud’s other network related services (such as the plugins manager) was working for me either. I ended up giving up on nextcloud because it was causing too much trouble for me, and migrated to seafile instead. Hopefully the above info might help some of you get your installs working though.

Anyone had any luck with the blank screen issue that Fam and 2017jpe have described? I have the same issue and have no clue how to resolve it.

I've just finished setting up nextcloud as per the latest tutorial from Spaceinvador One, and I have everything working, except that my router does not support NAT loopback. This means I cannot access nextcloud via the domain name I set up from within my local network, but can still use the local ip address along with port 444. This obviously creates problems with devices that move in and out of my local network as I cannot have both addresses setup on them (as far as I know). Does anyone here know of a workaround for no NAT loopback? (Other than buying a new router as this isn't an option right now) From my research on it people have been able to get around this issue by running a local DNS which resolves the domain name used for external access into a local IP address, so the router never has to deal with it. I installed pihole to see if I could do this, but DNS doesn't resolve an IP address with a port number, just an IP. So this would only get me as far as having my domain name point to my server IP, but not to the nextcloud docker on port 444. I saw one or two people on other forums mention SRV records as a way to include ports, but information on that starts getting very technical and quickly goes over my head. Any help/suggestions would be great!