-
-
Notifications
You must be signed in to change notification settings - Fork 299
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
no response from backend #27
Comments
It looks like the backend server can't connect to the db, because it can't execute the command in the entrypoint.sh to create the admin user. Maybe it is a linking issue within the Synology Os? I would try updating the Synology docker add-on and trying it again. Do you use other services that are linked with docker-compose? No Problem! :D |
just checked db and redis
seems to work fine. docker and compose are the "latest" versions from synology. but they are old...
I was able to manual update the binaries to the real latest ones. I will give a try later. |
Okay it seems to be an old issue: hooram/ownphotos#10 |
I created a new image. Please do a docker-compose pull and then a docker-compose up. It should work now. If it does close the issue :) |
now it works! |
do you need some help with docs? |
Yes that would be great! Open a pull request or write me on discord if you have some docs :) |
First I don't know if this question has been closed, however yesterday when installing librephotos docker it presented the same error. |
You probably missed the step renaming librephotos.env to .env |
I ran the process of copying librephotos.env to .env and changed the folder variables and nothing. I don't know where I saw that the user is admin and the password is admin and that it could be changed in the .env but in the env there is nothing mentioning the user and password of the interface |
Hi,
I've got a problem, installing librephotos on my NAS. It's a Synology with an Atom.
I installed it using your compose-file. All containers are running. I just need to add the proxy to my brdige network and i was able to connect to the frontend over port 3000.
When I try to login, i've got the following error message. The browser never receives a response for the call to
*:3000/api/auth/token/obtain/
.I checked the log of the backend container and got the following:
Any idea whats going wrong?
BTW: Thanks for reviving the project!!! 😃
The text was updated successfully, but these errors were encountered: