User:Woozle/2017/08/16/https subdomain issue

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search

Final Fix

The .conf file for apparently needed to be rebuilt. Through VirtualMin, I removed SSL support from, then added it back in; this seems to have fixed the problem via wireless (and yes, I can confirm that the connection is using IPv6 -- which also breaks my session table just a bit, so it's GOOD that this happened).

Partial Solution

Somehow, the link to /etc/apache2/sites-available/ in sites-enabled had been replaced by an actual file, so updates to the sites-available version were not actually being implemented. I replaced the file with the proper link, reloaded Apache, and everything started working properly.

With my cellphone connection, however, the problem remains.

Test links:


At first, this only happened when trying to access the site via my cell connection; at home, everything worked fine.

As of today, the problem seems to have propagated to my home connection as well (though this may be because of the config fix I tried).

The problem is that while brings up the correct web site, responds as if I have requested (which is on the same server, configured through Virtualmin as a subdomain of

This does not seem to be browser-dependent. Here are results from wget:

woozle@SamEagle:~/scratch$ wget --no-check-certificate
--2017-08-16 18:45:17--
Resolving (, 2604:a880:400:d0::14c7:1
Connecting to (||:443... connected.
WARNING: no certificate subject alternative name matches
	requested host name ‘’.
HTTP request sent, awaiting response... 404 Not Found
2017-08-16 18:45:18 ERROR 404: Not Found.

Trying the same thing from Firefox shows that the certificate it receives is correct for; if you ignore the mismatch, you get content from

...and here's what that wget request looks like on the server side:

==> ./cloud.vbz.net_access_log <== - - [16/Aug/2017:22:45:18 +0000] "GET /admin HTTP/1.1" 404 4590 "-" "Wget/1.17.1 (linux-gnu)"

So clearly Apache has somehow decided that I'm requesting when I request -- but only when I request it through https.