Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 2 subscribers
  • Views 4891 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

User Portal - External Access

Dickiebird1974
I know this question has been asked before but for the life of me I cant seem to get it to work outside of the LAN.

I have the UTM set up with some services like SSL VPN and webserver protection running so to set up the user portal outside of the LAN I am forced to use another port like 4443, I have set the listen address to ANY and allowed ANY networks to connect.

It works internally but not externally, I cant see anything in the logs indicating that there is a connection even being sent through.

One note... I have quite a few additional IP's set up under Interfaces as I have a /28 range coming in.

Any ideas


This thread was automatically locked due to age.
  • 0
    I have the port set up on 1443. 
    Allowed networks: any
    Listen address: any

    So mostly the same settings as you have. Are you querying the correct ip/hostname?

    the new sophos board sucks... :-( please give us the old one back.

  • 0
    Is there any router or firewall in front of your UTM that might block your custom port?
    May your ISP be blocking your custom port?

    ----------
    Sophos user, admin and reseller.
    Private Setup:

    • XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)
    • UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
  • 0
    Well, you got me thinking....

    I tried it on my phone over 3G and it worked, then I tried it from another location other than where I was testing from (azure machine) and it worked from there also, so it must have been firewalls on the Azure side.

    Thanks again fro your help.
  • 0
    If you try from the location from where you are testing and you are connecting from the inside through the outside address back inside you will have to create a full-nat rule.

    Managing several Sophos UTMs and Sophos XGs both at work and at some home locations, dedicated to continuously improve IT-security and feeling well helping others with their IT-security challenges.

    Sometimes I post some useful tips on my blog, see blog.pijnappels.eu/category/sophos/ for Sophos related posts.

Cookie Information Banner