1.29/ssl issue with dynamic dns

[kkrofft]

I hope I can explain this well enough to get some help...
I upgraded from 1.28 to 1.29 with minimal issues other than problems with the SSL certification.

My ZM server is also my home network firewall (shorewall) and media server not using a domain. When connecting from inside the network I am
seeing issues with the bookmarked URLs where the my previous http://<hostname>/zm redirects to https://zm which can't be found. Editing the bookmarks to https://<hostname>/zm works OK other than having to accept the "unsafe" certificate. (I have updated the local cert with genkey)
But I now see the URL as HTTPS: where the https is in red with a slash through it (Chrome). In Firefox if I enter https://<hostname>/zm, Firefox
exits but using the server IP address instead of the hostname works OK. (client boxes are all Windows with hosts file name resolution).

All of the above is workable with a little help to family members having to change the bookmarks. But we also monitor the ZM system remotely.
My home Roadrunner account has a variable IP so I have always used DNSexit for dynamic dns resolution. It has a url of <user>.linkpc.net:xxxx/zm which port forwards to the zm installation. This worked fine with http in 1.28. Now when I enter the url I get an error page where the url redirects to
https://zm which can't be resolved. Entering it as https://<user>.linkpc.net:xxxx/zm responds with error

"SSL_ERROR_RX_RECORD_TOO_LONG
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified."

So I am open to suggestions (and perhaps ridicule ) if you can tell me what I need to do to make these issues better.
Thanks!
KK

[bbunge]

My guess is that you are using Centos (7?)? Did you open the port in your firewall for SSL?

firewall-cmd --permanent --zone=public --add-service=https

[kkrofft]

CentOs 6.6 actually with Shorewall as the firewall.

Shorewall uses a different syntax but I think I have it correct.
To port forward you add this line to the rules file:

DNAT net <destination host IP>:<destination port> tcp <source port>

This means dynamic NAT packets from the internet to the destination machine on the desired port using TCP all incoming traffic addressed to the source port.

Mine looks like DNAT net 192.168.1.254:443 tcp 1111 this worked for HTTP when the port was 80 not 443.

[kkrofft]

Turns out that the issue with the dynamic DNS issue had to do with the VPN settings for the VPN I was using to test access from inside the local network. It is working now.