Docker compose new install failed "550 Internal Server Error...."

[hungrytree]

• New install using Docker compose
• Followed instructions from the web site: https://docs.firefly-iii.org/how-to/data-importer/installation/docker/

1. Downloaded the 4 files and renamed as instructed
2. Performed the 4 edits to the files ensuring the passwords matched exactly
3. Ran Docker compose using the provided command

Install failed with "500 Internal Server Error...."

Detailed error:
"Could not poll the database: SQLSTATE[HY000] [1045] Access denied for user 'firefly'@'172.20.0.4' (using password: YES) (Connection: mysql, SQL: select id, name, data from configuration where name = is_demo_site and configuration.deleted_at is null limit 1) "

"This error occurred in file /var/www/html/app/Support/FireflyConfig.php on line 65 with code 0."

I went through this procedure three times. The second time using the same resource. For the third attempt I deleted everything from Docker, downloaded the 4 files afresh and did the edits again.

The result was the same.

Most of the configuration files make little sense to me - out of my depth. I can edit as required but not diagnose the problem. The log file is very big but I can provide selected highlights on request :-)

Anyone help?

[JC5]

Hi,

This is a common issue. Did you also delete the volumes when you started over? And are you sure the database password is the same in both cases?

[hungrytree]

Thanks for the speedy response.

The first two attempts the passwords were identical copy/paste from one to the other.

For the third attempt I used a different password, but again identical in both places.

No, I didn't deleted the volumes explicitly, I assumed that happened automatically when I removed the container. I am relatively new to Docker and may have missed something there. I will investigate that. Even so, why did it fail?

Thanks

[JC5]

Because docker doesn't remove volumes by default (thank them later lol) the previous password is kept. If you made a mistake, even without realizing it, you run into this issue.

[hungrytree]

Thanks JC5, that was the answer - got the login page now.

On investigation there were loads of old volumes around. As I am now to Docker I have been doing a lot of trial and error which appears to be still lying around, hidden unless you know where to look.

Thanks again for your swift response

[JC5]

Sure thing!