-
Notifications
You must be signed in to change notification settings - Fork 234
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 connecting to websocket on login page #134
Comments
Same error here. Also on Atom server (Intel D510MO) |
FYI, the project may be going to a new home as the former benevolent dictator has disappeared. Please see #137. |
The BACKEND_HOST should be from the point of view from the person opening the browser. So it should be an absolute url, something like 192.168.82.12 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I've been battling with Ownphotos for the last few days and trying to learn Docker in the process, and I'm at the stage where I need some help.
I have set up the Docker containers with docker-compose exactly as it appears in docker-compose.yml.template in this repo. So
BACKEND_HOST
is set tolocalhost:3000
. Btw, I'm accessing the frontend through an SSH tunnel (the containers are running on a headless server) to eliminate any issues with CORS or hostnames. Thus,localhost:3000
on my local machine is reallyserver:3000
, but appears to both the server and local machine as localhost.Anyway, I can load the login page fine, but after entering the details (the default
demo
anddemo1234
), the page doesn't load and it's as if nothing actually gets to the backend. Looking at the browser console, there seems to be trouble connecting to the backend websocket (these messages appear soon after the page is loaded):Upon clicking "log in", I get:
and then I get the "No connection to backend server" error.
In the logs for the ownphotos-backend container, it looks like a worker is failing to start. The following messages seem to loop indefinitey (I'm not sure if the SSE4.1 error is related - the server only has an Atom processor, so presumably dlib fails on import):
I tried pinging the containers from each of them to make sure the networking is okay, and that seems fine. I'm really not sure what to do at this point. I considered trying to compile dlib without SSE4.1, but I can't even find where it used (or located) in the backend container. But surely the frontend should still work even without a working dlib install?
Any ideas?
The text was updated successfully, but these errors were encountered: