Support intro
Sorry to hear you’re facing problems 
help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.
In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:
example
Or for longer, use three backticks above and below the code snippet:
longer
example
here
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can 
Nextcloud version (eg, 29.0.5): Latest
Operating system and version (eg, Ubuntu 24.04): Docker Desktop on Windows 10
Apache or nginx version (eg, Apache 2.4.25): N/A
PHP version (eg, 8.3): N/A
The issue you are facing:
I cannot get Nextcloud running at all no matter what. I posted about this situation on the r/Nextcloud subreddit, and got one response. I am told I need to set up PiHole to create a DNS record that points to my domain I setup on Namecheap. Here is the post for context. What I hope to get out of this post is what else I can do to get Nextcloud running. I have not been able to get this to run for several months now, and I’m close to giving up on Nextcloud altogether. Can anyone help?
Is this the first time you’ve seen this error? (Y/N): Y
Steps to replicate it:
Assuming I do not have PiHole installed
- Install the AIO as normal per the documentation link here for Windows.
- Do nothing for a few weeks
- Nextcloud container logs then show new errors like this which results in inability to login.
[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."}
Assuming I do have PiHole installed
- Run my docker commands as normal to create the mastercontainer:
docker volume create ^
–driver local ^
–name nextcloud_aio_nextcloud_datadir ^
-o device=“/host_mnt/e/Nextcloud” ^
-o type=“none” ^
-o o=“bind”docker run ^
–init ^
–sig-proxy=false ^
–name nextcloud-aio-mastercontainer ^
–restart always ^
–publish 85:80 ^
–publish 8080:8080 ^
–publish 8443:8443 ^
–volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config ^
–volume //var/run/docker.sock:/var/run/docker.sock:ro ^
–env NEXTCLOUD_DATADIR=“nextcloud_aio_nextcloud_datadir” ^
nextcloud/all-in-one:latest
- Login to the 8080 AIO page as normal.
- Now I get errors like this:
Nextcloud AIO v9.8.0
Domaincheck container is not running
This is not expected. Most likely this happened because port 443 is already in use on your server. You can check the mastercontainer logs and domaincheck container logs for further clues. You should be able to resolve this by adjusting the APACHE_PORT by following the reverse proxy documentation. Advice: have a detailed look at the changed docker run command for AIO.
How to reset the AIO instance?
If something should be going wrong, for example during the initial installation, you can reset the instance by following this documentation.
The output of your Nextcloud log in Admin > Logging:
N/A
The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):
N/A
The output of your Apache/nginx/system log in /var/log/____:
N/A
Output errors in nextcloud.log in /var/www/ or as admin user in top right menu, filtering for errors. Use a pastebin service if necessary.
N/A