FF 6.1.22 500 Internal Server Error

[pupilov]

Support guidelines

• I've read the support guidelines

I've found a bug and checked that ...

• ... the documentation does not mention anything about my problem
• ... there are no open or closed issues that are related to my problem
• ... it's definitely a Firefly III issue, not me

Description

Hello. After upgrading from 6.1.21 to the latest 6.1.22, Firefly keeps crashing with 500 Internal Server Error :(.
Going back to 6.1.21 fixes the problem, and Firefly starts working again.
I have attached the full log file, it seems it has something to do with the new date/time entries in the DB.

I will stay on 6.1.21 for now, as I can't afford losing current DB. But maybe my logs can help solve a developing problem.

Debug information

Debug information generated at 2024-11-11 01:26:00 for Firefly III version v6.1.21.

System information
Item	Value
Firefly III	6.1.21 / v2.1.0 / 24 (exp. 24)
PHP version	8.3.12 (64bits) / apache2handler / Linux x86_64
BCscale	12
Error reporting	Display: Off, reporting: ALL errors
Max upload	67108864 (64 MB)
Database drivers	*mysql*, pgsql, sqlite,
Docker build	#1131, base #91

Firefly III information
Item	Value
Timezone	Europe/Bucharest + Europe/Bucharest
App environment	production, debug: false
Layout	v1
Logging	notice, stack / (empty)
Cache driver	file
Default language and locale	en_US + equal
Trusted proxies
Login provider & user guard	eloquent / web
Login headers	N/A + N/A
Stateful domains
Last cron job	never (never)
Mailer	log

User-specific information
Item	Value
User	#3 of 1
User flags
Session start	2024-11-01 00:00:00
Session end	2024-11-30 23:59:59
View range	1M
User language	en_US
User locale	en_US
Locale(s) supported	en_US.utf8: ✅ en_US.UTF-8: ✅
User agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36

Expected behaviour

No response

Steps to reproduce

1. update to 6.1.22 from 6.1.21
2. check for db errors

Additional info

_firefly_iii_core_logs.txt

[JC5]

Hi, thanks for opening an issue!

The code to upgrade the database is part of the docker container. Please remove the Firefly III container and image completely, and start it again. That should solve the issue.

[H3wastooshort]

i had the same issue which got resolved by re-running the migrations completely: https://github.com/orgs/firefly-iii/discussions/9460#discussioncomment-11280163