Closed JeremyKennedy closed 7 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Update, I took the exact same Docker setup, but switched to the official kimai/kimai2:apache
container, and mapped port 8001
as specified in their docs. I then deleted the kimai
folder, but did not reset the db. It works now. So, it seems to be an issue with the LSIO container specifically.
Same error here after updating the container on Unraid.
I had the same issue - had to downgrade back to 2.11.0-ls39, which resolved the issue for me until a permanent fix is found. Running on UnRaid 6.12.6.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Given we've had no other reports of issues since this, and this issue was on the back of an update, I am going to assume this is now resolved (and I have been working on this container/testing it recently with no issue)
If I'm wrong, please re-open and we can try to get to the bottom of what is going on.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
I've done a fresh install of Kimai and added a new user to my MariaDB. Kimai successfully connects to the db and runs migrations - I can see the changes in the db. However once Kimai startup finishes, accessing the UI results in a 500 Internal Server Error. I'm accessing it through its port 80 and 443, with the same results. As well, I've created the Kimai user as documented in your README.
Expected Behavior
I expect to see some startup page.
Steps To Reproduce
Environment
I'm running in Unraid, using your Community Apps template for Kimai and MariaDB. The DB connection is working. Kimai fails to load the home page after a fresh install.
CPU architecture
x86-64
Docker creation
Container logs
Kimai logs