Certificate Errors

3yam5y2b0

Hello Monocle community,

I was just thinking about reviving and bringing my monocle proxy back to life. It didn’t work out right away, so I’ve been going through the steps. I seem to be getting an expired certificate error (28 November 2025) on the mproxy.io domain, and Alexa isn’t happy about that.

Is that the right issue, or is there another domain it should be using? Will this be fixed, or is this the end of the road for this service?

Thanks for all the years you’ve provided this service.

Regards

Joe

@3yam5y2b0, have you had connectivity in the past? I lost connectivity to my Alexa devices back in January. This has happened in the past and was always a server/certificate error on Monocle’s system. This last time, the problem persisted for weeks and there was never any response from Monocle regarding the problem. From what I have seen on other posts, Robert has not answered anything in over a year. I gave up & replaced the Monocle functionality by setting up a Scrypted server within Home Assistant, and it provides the same connectivity to Alexa that I had before. You don’t have to have Home Assistant to set up a Scrypted server. It will run on various OS.

pat

I’ve been meaning to set this back up for ages and your email notification made me check the forums. Not much activity here!

pat@pihole:~ $ sudo monocle-gateway --enable

 ******************************************************************
 *             __  __  ___  _  _  ___   ___ _    ___              *
 *            |  \/  |/ _ \| \| |/ _ \ / __| |  | __|             *
 *            | |\/| | (_) | .` | (_) | (__| |__| _|              *
 *            |_|  |_|\___/|_|\_|\___/ \___|____|___|             *
 *                                                                *
 ******************************************************************

<<ENABLING>> THE [MONOCLE-GATEWAY] SERVICE
● monocle-gateway.service - Monocle Gateway Service
     Loaded: loaded (/etc/systemd/system/monocle-gateway.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2025-12-03 06:27:44 AWST; 8s ago
   Main PID: 36301 (monocle-gateway)
      Tasks: 11 (limit: 8755)
        CPU: 1.084s
     CGroup: /system.slice/monocle-gateway.service
             ├─36301 /usr/local/bin/monocle-gateway
             └─36324 /usr/local/bin/monocle-proxy -p 8554

Dec 03 06:27:45 pihole monocle-gateway[36301]: [RTSP Server Started]
Dec 03 06:27:46 pihole monocle-gateway[36301]: [Monocle Connected]
Dec 03 06:27:46 pihole monocle-gateway[36301]: [RTSP Server Registered]
Dec 03 06:27:46 pihole monocle-gateway[36301]: -------------------------------------------------
Dec 03 06:27:46 pihole monocle-gateway[36301]: MONOCLE RTSP SERVICE - INITIALIZED
Dec 03 06:27:46 pihole monocle-gateway[36301]: -------------------------------------------------
Dec 03 06:27:46 pihole monocle-gateway[36301]: FQDN = [hidden].mproxy.io
Dec 03 06:27:46 pihole monocle-gateway[36301]: HOST = 10.10.10.51
Dec 03 06:27:46 pihole monocle-gateway[36301]: PORT = 443
Dec 03 06:27:46 pihole monocle-gateway[36301]: -------------------------------------------------

I need to update my RSTP endpoints as they have all changed. Just did one to test for you and am getting an Alexa device skill error so will need to redo that before I can see if monocle-gateway hands over the stream.

Looks like it’s all working though.

pat

@Joe

I’m an idiot!

Sorry mate - 0400 here. Just read @3yam5y2b0’s post properly.

Yeah, their domain cert has expired so that will be why I’m getting an Alexa skill error.

If there has been no posts in a year then I’ll switch to Scrypted too - thanks mate - sorry couldn’t edit my post or respond for 600secs

3yam5y2b0

Hi

A better subject for this topic to stop others getting distracted by my words. The SSL certificate for the cloud service hosted by monocle has expired and the features that depend on that (Alexa) are not working

@Joe , yes this worked great for a long time but my echo show went bonkers and started flickering like Max Headroom so I had to switch it off before we all went crazy. So crazy that I paid Amazon to provide me with a new “black friday” echo show and now I can enjoy their adverts on display in our home again.

However, the camera features was always a good thing - I had an automation that restarted it every morning and it sat running all day waiting for the Amazon delivery operative to knock and run.

I hope @Robert is keeping well. He was a fantastic help last time Unifi made breaking changes. I do use scrypted so that I can see my cams in Apple Home but I did not know it was possible to do the Alexa feature there. I will explore that option. thanks @Joe

3yam5y2b0

This post also talks about Alexa making changes to limit where we stream from: https://forum.monoclecam.com/topic/1426/now-they-have-been-hit-too