Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 27 subscribers
  • Views 596 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

Unable to make HTTP/S traffic forwarding to internal webserver work with XG SFOS 18.0.3 MR-3 ( Azure Deployment)

Thales

Hi Everyone,

Currently we have a working solution when using SophosXG 17 , but currently it seems that port forwarding isnt working like we expected on XG 18, While it was massively simply before, we are unable to make it work on our Azure environment.

From our side, we followed the simple steps when clicking on Add firewall rule > Server access Assistant (DNAT) where:

Internal server IP address: our proxy server private IP

Public IP address: SOphosXG public IP ( using a port Alias defined with the external IP )

Services: HTTPS

External source networks and devices: Any


Its important to notice I have followed the documentation provided by the support/ youtube videos/ vimeo videos but still, not success at all.


So, the question would be, does anyone had success with port forwarding with XG18 deployed on Azure? We have been delaying the migration of our 17 to 18 just because of this blocker.



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to LuCar Toni

    Hi, yes, nsgs rules are fine too. For debugging purposes i even added new inbound rule to allow a wider port ranges to allow traffic from my IP addr ess, so i could text with other ports besides https.

    At this moment, NSG rules are the same that we have in place for our XG17.

Children