Arming Envisalink panel from MSR

[toggledbits]

It uses document.location.hostname (Javascript DOM), so it's already doing what you ask, it seems. Open the console log. It logs the URL it's trying to open.

The server also logs connection attempts to reactor.log, and will note any conflict with the allows_ips list, if you've configured that.

[therealdb]

I'm currently out of my home network, so no access to logs. But, Javascript's console is giving me this error:

ClientAPI.js:324 API: starting Reactor client API
ClientAPI.js:228 API: opening ws://msr.mydomain:8111/wsapi
ClientAPI.js:278 API: attempting ws connection to ws://msr.mydomain:8111/wsapi
ClientAPI.js:280 API: got socket 1639471421927```

So, it's definitely trying to reach port 8111 on ws:// protocol. I'm using Synology Reverse Proxy to temporary get access to the web UI restricting by domain name and IP address and it's a very easy way to get access (in theory) when on the road (I'm using it with Vera as well).

[toggledbits]

OK. This doesn't show an error. Was there one? What it does show is the URL it's trying to connect to (does that seem right under the circumstances? Can that name resolve?) and a socket attempt and success. These will usually be followed by API: connected to and API: initial structure loaded, if the WebSocket negotation/conversion is successful. I have no experience with this proxy, so I have no idea if it would even support WS connections.

You might look at these to see if there's any help there:

https://mlohr.com/websockets-for-synology-dsm/

Synology Inc.

What can I do if I see

Synology Knowledge Center offers comprehensive support, providing answers to frequently asked questions, troubleshooting steps, software tutorials, and all the technical documentation you may need.

May 26, 2020

Synology DSM Reverse Proxy

⚠ This guide has been migrated from our website and might be outdated. Feel free to edit this guide to update it, and to remove this message after that. Synology NAS is the perfect companion to running Home Assistant. But by default, the DSM Reverse Proxy does not configure its NGINX settings to...

[therealdb]

@toggledbits I've already mapped websockets, but the problem is that it's trying to reach ws:// under 8111. Code is obfuscated, but I guess this line is probably writing the port as well

var _0x577573 = _0x36251f(0x107) + document[_0x36251f(0xd9)][_0x36251f(0x13b)] + _0x36251f(0x11f);

Looking at logs, it's writing:

API: opening ws://msr.mydomain:8111/wsapi

so it's something related to the port being added. I'm still out of home network, but I'll definitely look at logs when I'll be back.

[toggledbits]

Per my earlier post, it's using document.location.hostname. What's the URL that's showing in your browser when you access Reactor through the proxy? Does it change the port from 8111 to something else?

[therealdb]

@toggledbits nope, it's msr.mydomain:80 or 443 (I've tried both). So strange.

[toggledbits]

No worries, that's an easy fix. If I use document.location.host rather than document.location.hostname, it will include the port if it's other than the standard. That will be in the next build.

[therealdb]

wow, thanks! I'll update tomorrow and test from the office!

[therealdb]

So, it's working, but only under HTTP. When under HTTPS, it tries to connect to ws:// instead of wss:// and it's failing. It's OK for me, since it's a private DNS and a reverse proxy, and I'm usually using it while in office to avoid the use of VPN. Thanks again for the quick fix!

[toggledbits]

I'll look into that.