I’ve NEVER had this many problems with a docker container before, this is getting WAY past the point of being ridiculous.

I’m trying to set up the nextcloud AIO for docker behind NGINX Proxy Manager. Right now, I have everything set up such that I can go to the URL that I set up and get to a nextcloud page.

But the only page I can access is an error page that looks like this:

I have no idea how to fix this. I’ve already set 'maintenance'=>false in my config.php file. I’m completely at a loss here, I can’t do ANYTHING else in nextcloud other than look at this stupid error page. The AIO documentation is completely worthless here, it doesn’t give any guidance. And google isn’t helping either, every thread either says to add the above to my config (which I obviously already did) or just restart apache (which I’ve also done). I’m getting seriously annoyed with this and I’m about to give up altogether unless someone here knows how to get past this stupidity.

Edit: Okay I’ve done something REALLY stupid now. I figured I could just re-install nextcloud to see if I could fix this. So, I removed all of the containers, deleted the data and database folders, re-made the folders, and re-deployed everything. Now NOTHING works and I can’t get nextcloud to re-do its initial setup. But it looks like now maybe it is? IDK I’m lost here, I’m annoyed and it’s late and I should probably stop.

So apparently nuking everything and letting nextcloud re-install itself fixed this, somehow. I have no idea why.

  • hollyberries@lemmy.blahaj.zoneEnglish
    7·
    1 year ago

    I can’t troubleshoot your exact issue, as you seem to not see what is happening in the background and are relying solely on error pages. We need to get to the container logs.

    So, I removed all of the containers, deleted the data and database folders, re-made the folders, and re-deployed everything. Now NOTHING works and I can’t get nextcloud to re-do its initial setup.

    Did you remove the old containers and volumes?

    Clean up unused containers, networks, images, and volumes

    docker container prune
docker network prune
docker image prune

    DANGER ZONE LOSS OF DATA IF YOU DONT HAVE BACKUPS

    docker volume prune

    That will give you a clean environment to start over with your compose files.

    If youre still having issues, inspect the live container logs to find the errors.

    docker container logs  --follow

    Then post the errors.