UDMPRO Connection closed! Why

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.