Closed trev0r-STA closed 2 years ago
Please provide the error from error.log
.
Which one ? The nginx server log or the karadav debug file ?
21 nov. 2022 22:39:18 BohwaZ @.***>:
Please provide the error from error.log.
— Reply to this email directly, view it on GitHub[https://github.com/kd2org/karadav/issues/19#issuecomment-1322683851], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AEINUAJO32OUSGJIGOPNDYDWJPTXZANCNFSM6AAAAAASHCJJPU]. You are receiving this because you authored the thread.[Image de pistage][https://github.com/notifications/beacon/AEINUAJJJRPPQLZAJJ3HUDLWJPTXZA5CNFSM6AAAAAASHCJJPWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSO22G4W.gif]
The error.log file inside KaraDAV root directory.
No error.log file in the karadav directory nor karadav/www... Should I activate something in the config.local.php ?
No there is nothing to activate by default.
If you don't have a error.log file this means the error is in the web server, not in KaraDAV, you should look at the error log of the file server.
Nothing in the error log file of the webserver :-(
Maybe enable logs of your web server? I don't know your setup sorry.
If there's still nothing, does karadav has the right to write to its root directory?
You could try to update and configure the new option I added to choose where the error log should be saved? Maybe that will help?
Or enable http debug log in KaraDAV to see what's going on, but it won't show the 500 error anyway.
Maybe enable logs of your web server? I don't know your setup sorry. Logs are enable, I've entry's# in karadav.access.log, but nothing in the karadav.error.log since the rotation of the logs the 22 novembre at 0:00
If there's still nothing, does karadav has the right to write to its root directory? /usr/local/share/karadav owner www-data:root and permissions set to 755
You could try to update and configure the new option I added to choose where the error log should be saved? Maybe that will help? Or enable http debug log in KaraDAV to see what's going on, but it won't show the 500 error anyway. With the new version and enabling the error.log, I discover my database was owned by root and not writable to www-data... I'm confused
Then change the database file rights so that PHP can write inside it :)
yes, I've done it. I'm confused for opening an issue, and that's not the software, but my fault... You've lost time with me and you're not responsible... But all is OK, now
No worries :)
The error come: 1- when I want to create a new file 2- for existing file starting with a dot (hidden file in linux)
Debian 11, PHP 8.1, Nginx 1.18.0, NextCloud/OwnCloud latest version data directory: permission's 770, owner/group www-data:www-data (db.sqlite owned by root) Where could it come from ?