UDMPRO Connection closed! Why

deepbluesee

Over 1 Year my Monocle Gateway runs very fine!
Now that:
What happened
what can I do?


Okt 01 18:28:18 raspberrypi monocle-gateway[4408]: -------------------------------------------------
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]: INITIALIZE RTSP STREAM:  Auffahrt
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]: -------------------------------------------------
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  - NAME          : Auffahrt
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  - CAMERA.MFG    : Ubiquiti
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  - CAMERA.MODEL  : UVC G3PRO
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  - CAMERA.LABEL  : PRIMARY
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  - RTSP.URL      : rtsp://192.168.1.1:7447/kPml3ZJlMvvycfU7
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  - STREAM.ID     : STREAM:6805e9c1-1ac7-4334-9cfd-e271bc167146
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  - SESSION.ID    : b31e28e0-65c1-40ca-82a1-e7754762b85f
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  - LAST.MODIFIED : Sun Oct 01 2023 18:25:15 GMT+0200 (GMT+02:00)
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  - TAGS          : @fixaudio,@tunnel
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]: -------------------------------------------------
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  ATTENTION -> Next you should see log statements showing your camera
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:               establishing an inbound connection to this gateway instance via:
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  -> DNS URL: rtsp://9889bcab-8538-4ba6-95ed-4313438ab06b.mproxy.io:443/STREAM:6805e9c1-1ac7-4334-9cfd-e271bc167146
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  -> This DNS host address should resolve to: 192.168.1.95:443 on your network.
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:  NOTE: If you don't receive any inbound connection log statements,
Okt 01 18:28:18 raspberrypi monocle-gateway[4408]:        please see: https://monoclecam.com/monocle-gateway-troubleshooting

Okt 01 18:28:19 raspberrypi monocle-gateway[4408]: 2023-10-01T16:28:19.333Z [INFO]  [192.168.1.202:59436 <7WpK5aUfo>] RTSP CLIENT SOCKET CONNECTED
Okt 01 18:28:19 raspberrypi monocle-gateway[4408]: 2023-10-01T16:28:19.458Z [INFO]  [192.168.1.202:59436 <7WpK5aUfo>] RTSP CLIENT SOCKET CLOSED

Rich

I’m getting exactly the same issue. No obvious version update or change to Unifi Protect or Monocle gateway. Not sure if the echo updated overnight though? Any help would be greatly appreciated.

mjd

I’m also having issue with Unifi Protect. Seems like it started sometime after 6p CST for me. I did the standard reboot the Monocle gateway, UniFi Protect and Echo Shows. No luck.

pathfinder

Same here. version 0.0.6. Just posted in topic1314/unifi-cams-wont-work-with-alexa-since-today which seems to be the same issue. Same logs for me, too.

Rich

Tried to post my log, but it says it is being filtered as spam, really helpful!
The last two lines read the same as OP.
I have also rebooted Protect, Monocle and Echo.

Rich

@Monocle, any chance you could take a look or give us a hint/tip?

SchmuFoo

Same here, glad to know I am not alone

UniFi Protect: https://community.ui.com/releases/UniFi-Protect-Application-2-8-35/f5f77c21-9b10-46ed-94a6-577784d201f7

UniFi Network: https://community.ui.com/releases/UniFi-Network-Application-7-5-176/0a224764-0603-4a8b-a038-1a7d59c6615c

UniFi DMSE

Monocle

I think it’s an SSL certificate issue on the backend. I’ll look into it and should have it resolved sometime tomorrow.

Thanks, Robert

Rich

@Monocle Thank you, much appreciated.

Rich

Working for me now. Thank you.

Monocle

@Rich

Is it still working for you?

It’s not for me yet …

I have updated the SSL certificates. One had expired causing the issue. However, thus far, my Amazon Alexa device does not seem to be accepting the new certificate (which I have verified to be valid). Perhaps she is caching the old certificate and needs a little time to update any old cache. I think this happened last time as well, it took a day or two for Alexa to start accepting the new certificate. Let’s keep our fingers crossed that it will start working again soon for everybody.

Thanks, Robert

Rich

@Monocle, yeah still working for me. I restarted monocle before I tried it though, maybe that flushed my cache?

Thanks again.

rocketalf2012

@Monocle said in UDMPRO Connection closed! Why:

I think it’s an SSL certificate issue on the backend. I’ll look into it and should have it resolved sometime tomorrow.

Thanks, Robert

Hi Robert,
Problem solved ?

mjd

@Monocle Thank you for fixing the issue, works now for me. I did have to reboot my gateway.

deepbluesee

@Monocle
Work fine for me too!
Very good
Thanks you very much!

Monocle

Glad to hear its working again! Something else must be wrong on my end as its still not working for me using an Echo Show 8. Probably some custom config on my network applied while developing or testing :-)

warbeforepeace

@Monocle mine did not get fixed automatically. I tried restarting the container which did not resolve the issue either. The only thing that fixed it was to stop the container and then start it a minute later. Now everything is back to working.