@Elzershark
We did find a DNS issue on our end this evening … so feel free to try testing it again now.
Instead of the wildcard domain for DNS rebinding; you technically only need to allow the single DNS hostname that is displayed (FQDN) when you first start the Monocle Gateway service:
Example:
-------------------------------------------------
MONOCLE RTSP SERVICE - INITIALIZED
-------------------------------------------------
FQDN = ef231161-9698-486f-8686-19d565749c09.mproxy.io
HOST = 10.1.1.21
PORT = 443
-------------------------------------------------
Or course, if you move your Monocle Gateway or generate a new monocle.token, you may also have to update your DNS rebinding options in the future.
PS: If you can’t allow or don’t want to allow DNS rebinding, you could alternatively override the host entry in your router’s DNS server for this DNS host to always point to the internal IP address of your Monocle Gateway server.
Thanks. Robert.