-
Notifications
You must be signed in to change notification settings - Fork 33
502 Bad Gateway - No streaming #19
Comments
I have same problem! |
@maleszbacsi can you provide your logs, I'm not aware of an issue. So it might be you cannot connect to your IP camera properly. |
@cedricve
|
could be related to the dns name you provided |
I am having the same problem. Chromium console says "Failed to load resource: the server responded with a status of 502 stream:1 (Bad Gateway). Using a RPi4. But I can see the IP camera stream in the browser. How is kerberos.io supposed to know the cameras local network address? |
hey @TomNeutrino, did you update the setting page? when accessing the web app you can see the settings page at the top. |
Experiencing the same issue. I am able to access the stream via |
After using the latest docker image, it appears that Kerberos doesn't work. Adding an IP camera provides nothing and a message with "No stream, is the machinery running?" After using the console inside Chrome to inspect potential issues, the result was:
GET http://whirlpool/stream 502 (Bad Gateway).
The docker container was created using
docker run --name camera1 -p 80:80 -p 8889:8889 -d kerberos/kerberos
after executingdocker pull kerberos/kerberos:latest
The text was updated successfully, but these errors were encountered: