TLS blocked on non standard ports?



I'm having some customers report that my application cannot connect to my servers.

After some digging it appears that TLS traffic on non standard ports, like port 445, is blocked by Freedome.


Are my findings correct? Is there anything I can do in the application or on the server to make sure that TLS traffic on port 445 is not blocked?



  • Laksh
    Laksh Posts: 4,443 Former F-Secure Employee

    Hi Jensensen,


    As mentioned in this article, Freedome does not intercept SSL/TLS traffic.


  • Hello


    I'm seeing some odd behavior when using Freedome.


    If I move my server service to port 443 then everything works as expected.

    If I move my service to port 445, and don't use Freedome, then everything works as expected.

    If I enable Freedome and use port 445 then the server logs shows that the Freedome VPN server resets the TLS connection.

    I'm using self signed certificates.


    Any ideas?

This discussion has been closed.
Product & Pricing Info