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

Publish website on standard port and redirect to different port

RolfKunst

Hi everyone,

My case:
I have 3 websites on my webserver, those websites are on different ports: 8081, 8082, 8083. All 3 websites have their own domain.

I want for 1 website that it is published with ssl enabled
The other 2 can be accessed by port 80.

So it should be:
https://website1.domain.com to internal website1.domain.com:8082
http://website2.domain.com to internal website2.domain.com:8081
http://website3.domain.com to internal website3.domain.com:8083

What have I tried?
RealWebserver HTTP:
Port 80
Realwebserver HTTPS:
Port 443

Virtual Webserver
Website 1:
Interface: External WAN
Type HTTP
Port: 8082
Real Webservers: Webserver HTTPS

Website 2 and 3:
Interface External WAN
Port 8081, 8083
Real Webservers: Webserver HTTP

And also the other way around. The Realwebserver is port 8081, 8082, 8083 and the virtual webserver Port 443 and port 80 on the created real webservers.

Always Error 404 not found. The websites work internally perfect on the specific ports.

Please help!

With regards,
Rolf Kunst



This thread was automatically locked due to age.
Parents
  • 0

    Unknown said:

    And also the other way around. The Realwebserver is port 8081, 8082, 8083 and the virtual webserver Port 443 and port 80 on the created real webservers.

    Real webservers objects should be configured with 8081,8082 and 8083 (like in reality), and virtual webserver objects should be configured with 80/443 ports.

    Try to configure only one server at first, and post more information (screenshots and log files) here.

  • 0 in reply to vilic

    Hi Vilic,

    Thank you for your answer.

    I have attached an image with my configuration. I hope that you have a solution or can point me in the right direction.

    Do I have to configure nat also? I have not done that for those ports. That I redirect the ports 8081, 8082, 8083 to my webserver?

    Additional information: The websites work perfect internally

    With regards,

    Rolf

  • 0 in reply to RolfKunst

    There is no need for creating any firewall or DNAT rules when publishing internal web services with WAF (sentence copy/pasted from my previous forum post...;).

    Anyway, I am 99% sure that redirection from 443 to non-standard port is not supported in UTM9. It is not documented but I remember a forum post from (Sophos Staff) confirming this.

    Can you test it without SSL ?

  • 0 in reply to vilic

    Hi,

    You're confusing stuff.
    My post regarding redirection of non-standard port numbers was about the HTTP to HTTPS redirect. If you set the type in the Virtual Webserver edit form to 'Encrypted (HTTPS) & redirect' and use a port number that is not 443, the HTTP redirect to HTTPS is not working.

    This is totally unrelated to the port number used for the real webserver. There, you can use whatever you want.

    For debugging purposes I would also recommend to test with HTTP first. Please post the corresponding log lines of the reverseproxy.log.

    Sabine

  • 0 in reply to Evianne

    Evianne said:

    ..... If you set the type in the Virtual Webserver edit form to 'Encrypted (HTTPS) & redirect' and use a port number that is not 443, the HTTP redirect to HTTPS is not working.

    Sorry for my confusion, can you point me to the official Sophos KB where is above statement documented ?

  • 0 in reply to vilic

    There is no official Sophos KB regarding this issue.

    If someone has this problem he should open a support ticket.

    Sabine

Reply Children
No Data
Unfiltered HTML