Preview Website doesn't work after latest updates

Submitted by burstsolutions on Sat, 07/08/2017 - 20:39

I just ran a full update and the preview website is no long working and returning a 400 Bad Request for all my sites on the server. I'm not using SSL for the sites. There is no errors reported in any of the /var/log files or in /var/log/virtualmin.

  • Operating system: Ubuntu Linux 16.04.2
  • Webmin version: 1.850
  • Usermin version: 1.720
  • Virtualmin version: 5.99

Preview Website URL:

https://104.#.#.#:10000/virtual-server/link.cgi/104.#.#.#/http://www.example.org/

Thanks!

David

Related issues: 
#52416: Preview Website doesn't work with 5.07.gpl
#51969: Preview website does not work with SSL enabled
Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Sun, 07/09/2017 - 12:43

What gets logged to the domain's log files under /var/log/virtualmin when you try to use the Preview Website feature?

Submitted by bjb on Thu, 07/27/2017 - 11:22

I also see this problem. Apache 16.04 up-to-date and latest Virtualmin/Webmin.

It seems to be apache which is blocking the proxy.

X.X.X.X - End user IP Y.Y.Y.Y - Host site IP Z.Z.Z.Z - Server primary IP

Here is the virtualmin log: X.X.X.X - username [27/Jul/2017:12:15:38 -0400] "GET /virtual-server/link.cgi/Y.Y.Y.Y/http://www.domain.com/ HTTP/1.1" 200 299

Here is the apache log for the event: Z.Z.Z.Z - - [27/Jul/2017:12:15:38 -0400] "GET / HTTP/1.0" 400 0 "-" "-"

However if I run this:

curl -l --http1.0 -A "-" http://www.domain.com

I see this in the apache log: Z.Z.Z.Z - - [27/Jul/2017:12:17:20 -0400] "GET / HTTP/1.0" 200 281 "-" "-"

The request looks the same, but it works. So there must be something wrong in the details of the request from the proxy. Is there a way to turn on more debugging of this (I ask before attempting to modify the link.cgi code).

Submitted by JamieCameron on Fri, 07/28/2017 - 01:19

We recently discovered the bug that causes this - it will be fixed in the 6.00 Virtualmin release.

Submitted by JamieCameron on Fri, 07/28/2017 - 01:19

Status: Active » Fixed

Submitted by IssueBot on Mon, 08/21/2017 - 19:42

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.