`Access denied for user 'nextcloud'@'xxx.xxx.xx.x' (using password: YES)` on a fresh install

[F1zzyD]

`Access denied for user 'nextcloud'@'xxx.xxx.xx.x' (using password: YES)` on a fresh install

[joshtrichards]

The "Access denied" is presumably coming from MariaDB not Nextcloud.

Any chance you started up the stack (or at least the db container) once before? Such as with a different config/password.

Docker does not delete names volumes when stopping (or even removing) containers by default. If a previous volume is found, MariaDB will just ignore (nearly) all the config parameters specified in Compose (since everything is already set up).

[F1zzyD]

The "Access denied" is presumably coming from MariaDB not Nextcloud.

I've gone through and deleted all Maria databases and I'm still receiving the error on a fresh install. Seems to be a problem with Nextcloud

Any chance you started up the stack (or at least the db container) once before? Such as with a different config/password.

I did, but as I said I've even done docker system prune -a when I shutdown Nextcloud. I'm putting in the fields exactly what's in the docker compose Nextcloud still gives me this:

Error while trying to create admin account: An exception occurred in the driver: SQLSTATE[HY000] [1045] Access denied for user 'nextcloud'@'xxx.xxx.xx.x' (using password: YES)

The logs say this:

[Warning] Access denied for user 'nextcloud'@'xxx.xxx.xx.x' (using password: YES)

Not sure how this is such a problem...

[F1zzyD]

Update: I changed the volumes from db:/var/lib/mysql and nextcloud:/var/www/html and it went and installed, but not to those directories. What would cause Nextcloud to take the volume changes but not actually use the directories I pointed it to? There was nothing in those original directories to begin with.

[arialdomartini]

Getting exactly the same error.

Edit: I managed to make it work adding

    environment:
      - MYSQL_ROOT_PASSWORD=nextcloud

Edit2: amazing, I cannot make it work anymore.

[arialdomartini]

Works using the MySQL image instead of MariaDB.

[joshtrichards]

I've gone through and deleted all Maria databases and I'm still receiving the error on a fresh install. Seems to be a problem with Nextcloud

Deleting the databases is not enough. You have to delete the named volume db in Docker.

I did, but as I said I've even done docker system prune -a when I shutdown Nextcloud.

That command doesn't touch volumes.

Update: I changed the volumes from db:/var/lib/mysql and nextcloud:/var/www/html and it went and installed, but not to those directories. What would cause Nextcloud to take the volume changes but not actually use the directories I pointed it to? There was nothing in those original directories to begin with.

I'm not sure what you mean by "those directories". Do you means the ones to right of the colon? Those aren't directories on your host. They're directories in the containers. You can't change them.

You can, however, rename the named volumes (the left of the colon). That would have the same effect as deleting the named volumes created during a prior attempt to start things up... If that worked, then the cause was exactly as I suspected: you previously started up a mariadb container and it was re-using the prior db volume it had been associated with (and therefore the prior config).

This isn't a Nextcloud matter. Just standard Docker stuff.

Getting exactly the same error.
Edit: I managed to make it work adding

@arialdomartini Well, yeah, that parameter requires a value as stated in the docs. It can't be left blank. :-)

Edit2: amazing, I cannot make it work anymore.

It's a one-time parameter. Please go familiar yourself with either the MariaDB or MySQL Docker image documentation.

Works using the MySQL image instead of MariaDB.

Yes, because it's a fresh deployment of a new container again.

I'd encourage you both check out the Docker docs on volume management/etc. - e.g.

• https://docs.docker.com/storage/

as well as the MariaDB and MySQL Docker image docs.

The Nextcloud Community Help Forum: https://help.nextcloud.com is also a great resource for discussing these types of situations. That said, if you see an opportunity for improving this image's documentation, either submit the change yourself (ideally) or at least describe where it seems to fall short.

P.S. You don't have to take my word for it nor guess. Look at your db container's start-up logs. It tells you if it's initiating from scratch or using an existing db/volume.

[F1zzyD]

I got it fixed by changing it to where I wanted to install, which for me was home/user/nextcloud where I store all of my docker containers, so now it looks like /home/user/nextcloud:/var/lib/mysql

[joshtrichards]

Happy to hear you got it working!