Nextcloud is an open source, self-hosted file sync & communication app platform. Access & sync your files, contacts, calendars and communicate & collaborate across your devices. You decide what happens with your data, where it is and who can access it! If you have questions for use in a company or government at scale (>1000 users), do yourself a favor and contact Nextcloud itself - this community is mostly home-user focused!
Anyone able to see why I can't get the Nextcloud AIO working on docker in Windows?
I'm honestly just frustrated with Nextcloud at this point on Windows at least. I want to get it working on my Windows server because I use some programs like EAC for CD ripping into FLAC which does not exist on Linux to my knowledge, and it was working until 2 weeks ago out of nowhere with no changes and no use at all. I randomly started getting errors like this after not using nextcloud much:
[Wed Sep 04 21:54:24.888431 2024] [core:notice] [pid 765:tid 765] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND'
2024-09-04 15:54:24 {"level":"info","ts":1725486864.891314,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 7168 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details."}
After referencing that link and so many Nextcloud forum posts (such as this) and banging my head against the proverbial wall and multiple fresh installs later, I am now getting a new error on the AIO page.
The classic, "The domain is not reachable on Port 443 from within this container. Have you opened port 443/tcp in your router/firewall? If yes is the problem most likely that the router or firewall forbids local access to your domain. You can work around that by setting up a local DNS-server."
I have now come to the conclusion that I just can't seem to get it working on a docker container in windows for whatever reason. Nothing has changed on the domain name configuration I set up on Namecheap. I have opened up the 443 port on my TP-Link Deco app for the mesh router, and neither my ISP (Google Fiber) does not block that port nor do I have a firewall enabled.
I don't believe I need to set up a reverse proxy server or a local dns server as others have suggested since this WAS working in the past. What else could be the issue? I have spent weeks researching this issue on my own, and I need help now. Do I need to resort to setting up a Linux VM in Hyper V and running it from there?
Edit: I have been using this documentation for fresh installs (https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-run-aio-on-windows)
So I'm no networking expert, but my understanding is this: AIO is trying to reach your domain name using the DNS server it's being given. That's routing to an external DNS server, which is kicking back to your external IP address. When it goes to your modem/router it gets confused because the source is your internal network and drops the packets.
I'm not sure how it was working for you before, but when I set up AIO I got the same errors until I set up a Pihole and created a DNS record for my domain name pointing to my Nextcloud server.
You could try skipping domain validation, but based on what you describe I'm not sure it will work.
Yeah I don't understand it myself as I'm still learning the ins and outs of Nextcloud, but I got it working without any of that. I set it up as the AIO describes, set my public IPv4 as the A record on my domain in Namecheap, opened up the port 443, and voila it was working! It took me to the Welcome to Nextcloud page, and I was able to upload files and do whatever from there. That's annoying though if you have to set up a whole new container, a whole application, just to get around this error.
Thanks for the feedback! I'll look into PiHole. Hopefully it's not too difficult or time-consuming to set-up.
Try reinstalling nextcloud with tailscale, and no need to change router ports.
LinkedIn : https://www.linkedin.com/posts/r-quazi_stop-using-slackmicrosoft-teams-take-control-activity-7242929602292023296-U9As?utm_source=share&utm_medium=member_desktop
I’ve written a comprehensive guide here: https://dev.to/r-quazi/take-control-of-your-data-self-hosting-nextcloud-4enf