Closed bstyx09 closed 2 years ago
Have you checked nginx logs? I guess that this problem caused by reverse proxy. 500 and 404 errors are releated to web server.
I do see the requests with the response codes in the access log file, but unfortunately no details listed in the error log file. The error log doesn't show any data when the failing requests come through.
I am hitting the host directly to access the UI for the moment so there shouldn't be anything in front of nginx that could be causing this
Hmm, looks works fine. Maybe try: as root:
UPDATE: very first red line, error 401 - Unauthorized. I think there main reason. I do not understood where not authorized? Database?
Went ahead and ran the upgrade command, then also rescanned the filesystem, rescanned faces, and then had it train faces. In the admin area I see that scanning faces failed when I tried to run it, but the train faces job was able to train 2 of them according to that page:
There are 398 faces in the "/var/lib/librephotos/protected_media/faces" directory so it seems like it's seeing them but just not able to pull them out for whatever reason. The face recognition page still shows no faces.
I was able to see some errors in the ownphotos.log file:
Please check the folders / files permissions:
ls -l /librephotos/folder/protected_media
Owner and group must be librephotos:librephotos. And mode 775.
UPDATE:
standard installation path:
/var/lib/librephotos
Change owner / group to librephotos and permissions:
chown -R librephotos:librephotos /var/lib/librephotos
chmod -R 775 /var/lib/librephotos
That did it! For whatever reason I assumed it used www-data user account instead of one specific to librephotos.
Thanks a ton, it's working pretty well so far!
The folder on the drive shows that it did scan some faces so it seems like the scan process worked, but navigating to the faces page returns a 404 and a 500 level error.
all of the logs I've found seem fine and don't have any indication that something isn't working. I'm not really sure what else to look for.
The face cluster page is also returning a 500 error too: