Upgrading Failed

First time I have an upgrading issue:
Current version: 5.9.2
New version: 5.10.3

Getting the following error:

500:

Thats it, even with debug enabled in .env no further info is shown.

1 Like

Have you checked your laravel logs? Or your web server logs (nginx or apache2)?

Same problem here. The error message is slightly different: 503 Service Unavailable

Current version: 5.9.4
New version: 5.10.4

Debug enabled, but no information about this in the Laravel logs.

Well this type of information in the error_log:

[27-Jun-2024 06:55:03 UTC] PHP Warning: PHP Startup: Invalid date.timezone value ‘’, using ‘UTC’ instead in Unknown on line 0

Under settings, location, time zone Europe/Amsterdam set

@david do you have any ideas?

The migrations have not run.

php artisan migrate

Thanks for the reply. Can you help me a little further on what I should do next?

Invoice Ninja runs on a shared hosting provider. So I don’t have a console at my disposal.

Hello David,
shall i run the command in ssh before the update?

The migration is run after the update.

@david The error pointed out below appears similar to the date.timezone error that I noted here. Or am I mistaken?

Can you post the full error.

I think this is a php.ini config error on the php startup, not the app startup, but this will only be confirmed when I can see the full error log.

Getting a little lost here guys, seems we are mixing two issues.

So I should run the update, then when i get a 500 error i leave the error open and run php artisan migrate in ssh?

Or am i wrong?

@coolisio

After you see a 500, are there any errors in the logs (storage/logs/laravel.log)

No there aren’t but i want to some other logs and found:
[Fri Jun 28 07:35:21.449040 2024] [proxy_fcgi:error] [pid 3214230:tid 139723288647360] [remote xxxx:2422] AH01071: Got error '; PHP message: PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 36864 bytes) in Unknown on line 0', referer: xxxx

So i upped the memory limit for php because 1024 didn’t seem enough and that seemed to work, because the update took longer, but got another completely different error

then got stuck on the following error:

500: Call to undefined method Illuminate\Console\View\Components\Task::runTimeForHumans()

Update seems to have worked but after refreshing it seems that I am in the React version.

Running

UPDATE accounts SET set_react_as_default_ap = 0;

is not getting me back to flutter anymore

See my previous topic: https://forum.invoiceninja.com/t/react-to-flutter-ui/12864

@coolisio

The 500 would be a transient issue after the upgrade has completed.

If you prefer the flutter interface, we encourage the desktop apps to access this interface going forward.

Perhaps it is indeed a bit unclear, because I get through it with my 503 error: service unavailable. Should I otherwise create a new topic?