Stop all containers if they are running from the AIO interface
Stop the mastercontainer with sudo docker stop nextcloud-aio-mastercontainer
If the domaincheck container is still running, stop it with sudo docker stop nextcloud-aio-domaincheck
Check which containers are stopped: sudo docker ps --filter "status=exited"
Now remove all these stopped containers with sudo docker container prune
Delete the docker network with sudo docker network rm nextcloud-aio
Check which volumes are dangling with sudo docker volume ls --filter "dangling=true"
Now remove all these dangling volumes: sudo docker volume prune (on Windows you might need to remove some volumes afterwards manually with docker volume rm nextcloud_aio_backupdir, docker volume rm nextcloud_aio_nextcloud_datadir)
Optional: You can remove all docker images with sudo docker image prune -a.
And you are done! Now feel free to start over with the recommended docker run command!
But now after running nextcloud-aio again, i do get an error when trying to submit my domain:
I see that he complains about my domain (in the form of (mydomain.ddns.net) ip-address on my mashine. Maybe the problem is, that when i execute:
dig +short mydomain.ddns.net
He does show me my local ip:
192.168.178.XX
But maybe it should be something public instead? But i am not totally sure why it resolves this to something local in the first place.
I did connect my local fritz box with my domain provider, so this should not be the problem.
Does any of you have an idea or opinion on this? Anything might be helpful!
A different way would be restoring a backup that you took before on the old AIO instance which would skip the domain verification. But obviously you need to know its location on the host and its passwordā¦
Hi szaimen, thanks for your answer!
Why is it local in the first place? I would change it if i knew how or why it is like that.
I assume you refer to the borg backup? The first installation was just a test pilot to see if AIO would work, which it did perfectly up until that point of failure of course. So my next top prioritiy is the borg backup
I donāt know as I do not know your network infrastructure. If you are sure that your domain definitely has the correct public ip-address set (which it does not look like), you should hopefully be able to overwrite the value during the docker run command with --add-host yourdomain.com:<public-ip-address>.
If you mean by my domain, my domain provider, than i did set it to the public ip of my router and installed a software on my local server to keep the ip up to date:
Iāve tried to override the IP Address but this time i have some other issue blocking my way. It did not start up correctly (even with my previous docker start command). When it starts up I get the following:
The new command with --add-host did work. But since i use a ddns domain i worry, that it will be out of sync with the ip at some point
I will monitor it.
At least now i know that indeed the internal IP was the problem And i can access my data again.
This should not be a problem since the mastercontainer should not make any access to your domain itself after the domain validation. So it should be fine if the A record gets outdated after a while
or why it is like that.
