After updates to beta 3.50 I have no access to SignalK via VRM portal. Currently at 3.50~13, I believe this worked at an earlier 3.50 version, but not 100% sure. Accessing via local IP address:4334 is still working. Is there a setting I have missed after the changes in 3.50 or do others have same issue?
Hi @HcGrande , that is strange; it works for me.
Running v3.50~13.
What VRM mode do you have enabled, and what security mode?
@mpvader, For security mode, i have standard settings “unsecured”. VRM Mode is set to “full”. Not sure if this is something, but “Use secure connection(HTTPS)” is also enabled.
Hi @HcGrande
By port 4334 you mean 3443? I see the public VRM access of your Signal K redirects to port 3443. This seems to be something that Signal K is doing, which it shouldn’t when accessing it through VRM.
This relates to running Signal K in TLS mode. Can you tell me more about your Signal K configuration, and anything that relates to TLS/SSL?
Sounds like i mixed up the Portnumbers 
It is a standard “large” install, enabled in the Cerbo GX. Only “task” it is doing is to run som N2K mapping. Will do another test when I am onboard.
Any special settings I should look for?
Anything related to ‘encrypt’ ‘https’, ‘tls’, ‘ssl’, inside signal K itself.
We are looking into making Signal K available with https, but the fact that your installation already does https, is unexpected, especially if you don’t recall setting it.
I confirmed the behavior when I set this:
However, this (enabling Signal K TLS breaking usage on VRM) should have also already happened on earlier Venus OS versions.
Can you confirm that you did not change your Signal K settings?
Thanks for assistance. The SSL was turned on. I cannot remeber fiddling with this, but it may have happened accidently… All seem to work fine Now 