Finalizing firefly-iii install

[ca3du5]

Greetings,

I am kind of a newbie with this stuff but am slowly learning bit by bit. My issue is that I think I have followed most of the step by step procedures you have outlined, but when trying to get firefly-iii to get access to the mariadb database I have setup I am running into an issue. It is causing php to fail whatever process is being done in the "upgrade-database" command. Whenever I try to run it I get a bunch of "PHP Deprecated:" along with a bunch of file paths and then this output which says it ran into an exception.

Illuminate\Database\QueryException

SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for db failed: Name or service not known (Connection: mysql, SQL: select table_name as name, (data_length + index_length) as size, table_comment as comment, engine as engine, table_collation as collation from information_schema.tables where table_schema = 'firefly' and table_type in ('BASE TABLE', 'SYSTEM VERSIONED') order by table_name)

What am I supposed to do with this? It just appears like a bunch of gibberish to me.

[JC5]

Hey, thanks for starting this discussion.

It looks like it tries to reach "db", but that address does not exist. You say you set up a mariadb. Are you running Firefly III locally, on your own machine? Or are you using Docker?

Cheers,
James

[JC5]

Mmm, that surprises me. Is the error exactly the same, or is it different "gibberish"?

What you can try is a simple reboot, often that's the easiest trick.

[ca3du5]

Here is the error I got after trying to rerun the first php artisan command
Illuminate\Database\QueryException

SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for db failed: Name or service not known (Connection: mysql, SQL: select table_name as name, (data_length + index_length) as size, table_comment as comment, engine as engine, table_collation as collation from information_schema.tables where table_schema = 'firefly' and table_type in ('BASE TABLE', 'SYSTEM VERSIONED') order by table_name)

at vendor/laravel/framework/src/Illuminate/Database/Connection.php:822

I was thinking about retrying a reboot and might have to do that if there's no other solution. Is there not a command to have firefly rexamine the .env file and make changes?

Tim

[ca3du5]

Ok I figured out part of what was going on. For some reason it didn't click in my head that the .env wasn't in the same location as the /var/www/firefly-iii and it was using the default .env file which explains why the errors were the same. I have copied the .env file I thought it was using all along into that directory and now I am getting the following error when I try to run php artisan firefly-iii:upgrade-database

Illuminate\Contracts\Container\BindingResolutionException

Target class [hash] does not exist

What does this mean? sorry to keep peppering with questions but I can't help but feel that I am very close.

[JC5]

No not a problem. Did you run composer install in the Firefly III installation directory?

https://docs.firefly-iii.org/references/faq/install/#error-class-auth-does-not-exist

[ca3du5]

Am I supposed to that even though I am using a locally hosted setup and not docker?

[JC5]

Officially, no. All dependencies should be there. But you never know.

[ca3du5]

That is so bizarre. I never would've thought that would fix it but it seems to be running through the correct sequence now. After it's finished I'll run the other commands and see if I can get it up and running. Thank you!

[JC5]

Not a problem, let me know!

[ca3du5]

Alright I ran the four commands and now I can pull up the webpage using my apache server but it is giving me this notice.

Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.4.0"

I find this strange since i have multiple versions of php on my computer, one of which is 8.4 so it should work. Do I need to tell composer or some other application to only use 8.4 and if so how do I do that?

[JC5]

Hi! This is a automatic reply that tells you how to get more debug details. Share and enjoy

1. Please collect some log files. Go to storage/logs and open the latest log file. It should be called something like ff3-fpm-fcgi-*.log. In it, you should be able to find the error along with its "stacktrace": this will tell me where Firefly III broke down. If you run Docker, use docker logs <container>.
2. You may also enable debug mode to make sure the log files catch everything and try again.
3. Make sure you clear your browser cookies and clear Firefly III's cache files by running php artisan cache:clear or by visiting /flush on your installation.

If you do not want to share log files or other details on GitHub, please send them to me over (encrypted) email.

[ca3du5]

I looked over the log file and it didn't seem to show anything beyond the issue I was talking about at first. The rest of the log file is blank other than the extended php artisan output that was erroring out at first.

I am suspecting there is something wrong with my apache configuration.

As far as I know I need to get it it to point to /var/www/firefly-iii/public as the DocumentRoot and then specify a listening port. I cannot use port 80 as I have something else my server listens on port 80 for so I specified 8000 with a VirtualHost config named firefly-conf and then enabled the conf file.

But for whatever reason it is not working and I suspect there is something in the firefly config that I need to also tell it to put itself on port 8000 but I am not sure how to do that.

Am I on the right track do you think or just completely lost?

[ca3du5]

I set APP_DEBUG to true as I saw recommended in another forum and it looks like it has a permissions problems with one of the files in the storage folder. Permissions in ubuntu always confuse me so I guess I should ask, who needs to own this file and what should the code for the permissions be? (e.g. 755, etc)

[ca3du5]

I got it to work. Found some old forums with exactly my issue and remedied the problem. Thanks for your help though! Without you I don't think I would've gotten on the path to victory.

Really appreciate it. Thanks!

[JC5]

Very nice, I'm glad to hear it! Now let's see if it was worth the trouble 😉