Gateway cert (*.mproxy.io) expired

wblakegoins

wanted to flag that the *.mproxy.io certificate used by Monocle Gateway instances appears to have expired on November 28, 2025 and is still expired today, over 8 months later.

Setup details:

Gateway version: 0.0.6 (official monoclecam/monocle-gateway Docker image, host networking mode, running on Debian 13)
Gateway connects to api.monoclecam.com fine and initializes correctly ([Monocle Connected], [RTSP Server Registered])
DNS resolution for my gateway’s FQDN (6bc13cc1-6619-4191-a3f8-be07e910dbd9.mproxy.io) is correct, resolving to my local IP
Port 443 confirmed reachable from other devices on my LAN

Verified directly with:
openssl s_client -connect <my-gateway-ip>:443 -servername 6bc13cc1-6619-4191-a3f8-be07e910dbd9.mproxy.io

Result:
verify error:num=10:certificate has expired
notAfter=Nov 28 23:59:59 2025 GMT

Since Alexa correctly refuses to connect to a server presenting an expired cert, this blocks camera discovery/streaming entirely — shows as “camera not responding” on the Echo Show side. Everything else in my setup (network, DNS, RTSP conversion, camera tagging with @tunnel/@fixaudio) checks out fine; this is the only remaining blocker.

Is anyone still actively maintaining certificate renewal for *.mproxy.io? Happy to provide more logs/details if useful.