API Service down?!
-
Hey guys. I checked the service monitoring and it shows everything should work, but i keep getting
“[Monocle Error] Unexpected server response: 302” from my monocle gateway working in a docker container.Container is in HOST Network mode, i can ping the host, i disabled DNS-Rebind Blocking in my router and i have a pihole working as my own dns server that is showing no blocked querys at all.
If the api is up and running i have to search in my network config but as far as i can see everything should be working here.here is a bit of the log:
------------------------------------------------- MONOCLE RUNTIME ENVIRONMENT ------------------------------------------------- VERSION = 0.0.4 OS/ARCH = linux/x64 PROCESS = monocle-gateway (PID=1) TIMESTAMP = 2020-09-07T13:19:44.019Z ------------------------------------------------- MONOCLE GATEWAY SERVICE (Version: 0.0.4) ------------------------------------------------- [Monocle Starting] [Monocle Connecting] [Monocle Started] [RTSP Server Starting] [RTSP Server Listening] 0.0.0.0:8555 (RTSP) [RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS) [RTSP Proxy Started] (PID=14) [RTSP Server Listening] 0.0.0.0:8554 (PROXY) [RTSP Server Started] 2020-09-07T13:19:44.491Z [ERROR] [Monocle Error] Unexpected server response: 302 [ '[Monocle Error]', 'Unexpected server response: 302' ] [Monocle Disconnected] [Monocle Reconnecting] ... in 7 seconds (attempt #1) [Monocle Connecting] 2020-09-07T13:19:51.821Z [ERROR] [Monocle Error] Unexpected server response: 302 [ '[Monocle Error]', 'Unexpected server response: 302' ] [Monocle Disconnected] [Monocle Reconnecting] ... in 11 seconds (attempt #2) [Monocle Connecting] 2020-09-07T13:20:03.146Z [ERROR] [Monocle Error] Unexpected server response: 302 [ '[Monocle Error]', 'Unexpected server response: 302' ] [Monocle Disconnected] [Monocle Reconnecting] ... in 16 seconds (attempt #3) [Monocle Connecting] -
Please try rebooting your Monocle Gateway instance if it’s still not connecting.
There was a short period of time this morning (about an hour) where this service was down for maintenance. But it should all be up and running now.Thanks, Robert
