UTM 9.4 - Unable to publish reverse proxy website - similar website works fine

Question

Hello, 
 
 I have 2 reverse proxy sites I am trying to publish via the WAF in Sophos UTM 9.4. One of the sites works great but the other refuses to publish although the set up of the 2 set ups is the same - Real/Virtual webserver, Additional interfaces (2 different IP's) and firewall profiles, etc. 
 On the client the site just times out. I am able to ping the external IP address when the interface is enabled. 
 Logs are: 
 2016:04:05-15:16:39 srv-utm1-1 reverseproxy: [Tue Apr 05 15:16:39.191359 2016] [mpm_worker:notice] [pid 8980:tid 4147328704] AH00297: SIGUSR1 received. Doing graceful restart 
 2016:04:05-15:16:39 srv-utm1-1 reverseproxy: AH00112: Warning: DocumentRoot [/var/www/REF_RevFroAaa1stTouch] does not exist 
 2016:04:05-15:16:39 srv-utm1-1 reverseproxy: AH00112: Warning: DocumentRoot [/var/www/REF_RevFro1stTouchTestt] does not exist 
 2016:04:05-15:16:39 srv-utm1-1 reverseproxy: AH00112: Warning: DocumentRoot [/var/www/REF_RevFroShareIntte] does not exist 
 2016:04:05-15:16:39 srv-utm1-1 reverseproxy: AH00112: Warning: DocumentRoot [/var/www/REF_RevFroShareIntLive] does not exist 
 2016:04:05-15:16:40 srv-utm1-1 reverseproxy: [Tue Apr 05 15:16:40.000521 2016] [mpm_worker:notice] [pid 8980:tid 4147328704] AH00292: Apache/2.4.10 (Unix) OpenSSL/1.0.1k configured -- resuming normal operations 
 2016:04:05-15:16:40 srv-utm1-1 reverseproxy: [Tue Apr 05 15:16:40.000687 2016] [core:notice] [pid 8980:tid 4147328704] AH00094: Command line: '/usr/apache/bin/httpd' 
 2016:04:05-15:16:40 srv-utm1-1 reverseproxy: [Tue Apr 05 15:16:40.000736 2016] [mpm_worker:warn] [pid 8980:tid 4147328704] AH00291: long lost child came home! (pid 8982) 
 2016:04:05-15:16:40 srv-utm1-1 reverseproxy: [Tue Apr 05 15:16:40.000761 2016] [mpm_worker:warn] [pid 8980:tid 4147328704] AH00291: long lost child came home! (pid 8984) 
 
 Thanks, 
 Mark.

Evianne · Answer

Hello Mark, 
 unfortunately, the HTTP redirect to HTTPS only works with the standard HTTPS port 443 at the moment. Please open a support ticket for this. Best, Sabine

Evianne · Answer

Hi Mark, 
 
 do you need to access it on port 9001 from outside? It's not necessary that the port number of the real webserver matches the port number of the virtual webserver. The WAF makes the translation. So you could try to change the port number on the virtual webserver to 443. 
 Sabine