Visiting a port that isn't TCP 443

ethernet cable

Connecting to a non-standard port on https behind a Sophos UTM

Posted on 10 July 2019 by Beaming Support

Almost all websites you visit securely will be using TCP 443 which is the well-known port for HTTPS. However if you need to visit another, less well-known port for HTTPS, for example this will cause a UTM error.

To resolve this issue you can configure the below.

Go to  “Web Protection” -> “Filtering Options” -> “Misc”

Under “Allow Target Services” click the small plus button

Fill in the circled fields on the above image, the fields being fairly self explanatory.

Once you are happy with your changes press the save button and this will add your port to the “Allowed Target Services” list.  Then when you browse to  you should no longer get an error from the Sophos UTM.

Interested in Cyber Security?

Sign up to receive our quarterly UK Cyber Threat Report and get exclusive content delivered straight to your inbox before anyone else sees it.

  • This field is for validation purposes and should be left unchanged.