AIO wont start after server reboot

Nextcloud version (eg, 20.0.5): unsure, System is down
Operating system and version (eg, Ubuntu 20.04): Debian 12
Apache or nginx version (eg, Apache 2.4.25): unsure
PHP version (eg, 7.4): unsure

The issue you are facing:
After server reboot I could not access next cloud interface or the AIO interface. Tried restarting again, Says connection refused when trying to access AIO interface.

Is this the first time you’ve seen this error? (Y/N): Yes

The output of your Nextcloud log in Admin > Logging:

Cant login

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

https://pastebin.com/iRqnHjAR

The output of your Apache/nginx/system log in /var/log/____:

nothing in /var/log for apache/nginx

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.

none as this is a docker app and cant login...

I deleted all containers but still get this error

root@nextcloud:/opt/nextcloud# docker-compose up -d
Creating network “nextcloud_default” with the default driver
Creating nextcloud-aio-mastercontainer … error

ERROR: for nextcloud-aio-mastercontainer Cannot create container for service nextcloud: Conflict. The container name “/nextcloud-aio-mas tercontainer” is already in use by container “5336f3125357b738fbddaee4ed9435f81a5c6eb4b3b9ea58d547a0c002bbe91f”. You have to remove (or r ename) that container to be able to reuse that name.

ERROR: for nextcloud Cannot create container for service nextcloud: Conflict. The container name “/nextcloud-aio-mastercontainer” is alr eady in use by container “5336f3125357b738fbddaee4ed9435f81a5c6eb4b3b9ea58d547a0c002bbe91f”. You have to remove (or rename) that containe r to be able to reuse that name.
ERROR: Encountered errors while bringing up the project.
root@nextcloud:/opt/nextcloud# docker inspect nextcloud-aio && sudo docker inspect nextcloud-aio-mastercontainer
[
{
“Name”: “nextcloud-aio”,
“Id”: “5ca171644ab42fba8310f616625b70f7f15fca7dea9a7764e1bbdfb23587d8b8”,
“Created”: “2024-05-10T08:33:33.803697567-04:00”,
“Scope”: “local”,
“Driver”: “bridge”,
“EnableIPv6”: false,
“IPAM”: {
“Driver”: “default”,
“Options”: null,
“Config”: [
{
“Subnet”: “172.18.0.0/16”,
“Gateway”: “172.18.0.1”
}
]
},
“Internal”: false,
“Attachable”: false,
“Ingress”: false,
“ConfigFrom”: {
“Network”: “”
},
“ConfigOnly”: false,
“Containers”: {},
“Options”: {},
“Labels”: {}
}
]

Should i prune docker images also, Dont want to lose my nextcloud data. As long as I don’t delete the volumes I should be safe correct?

nvm, Crowdsec over-rode the default 8080 port and screwed up the ports. It is working now that I disabled crowdsec.

1 Like

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