-
-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error 500 On Fresh Install Of 1.3 #1117
Comments
Hm, that shouldn't happen. Actually the caches should be pre-filled before you open the page the first time. I'll give it a try and see if anything changed. |
I didn't dive into the whole tree structure, but I saw that (mypath)/kimai2/var/cache/prod had somehow reverted from :www-data to :mygroup following the install step. I just ran the recursive chown/chmods to fix it again. |
Can't remember when I added the change to the documentation, introducing the The permission change is not necessary before the install command, as all is done by the same user. |
What I want to say is: I changed the order: first install, then change permissions. Thanks for posting, yes it helps! That was important feedback and it will likely help to prevent a lot of questions by less experienced bash users ;-) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. If you use Kimai on a daily basis, please consider donating to support further development of Kimai. |
Describe the bug
Minor/documentation. There appears to be new files/paths created between the documented step of changing file ownership/permissions and the console installation.
kimai-1.3-error.log
To Reproduce
Steps to reproduce the behavior:
chmod -R g+r .
chmod -R g+rw var/
Additional context
Re-running the ownership/permission changes following the install step clears the error.
The text was updated successfully, but these errors were encountered: