Multiple sites, Works with Https but not http

Question

Level 1

0 points

Multiple sites, Works with Https but not http

So I am running into an interesting issue which has me perplexed and confused dealing with one of my private websites.

I have only two websites hosted on my server with registered domains for each of them. One is a .net and the other is a .info. As of this moment neither site has a trusted SSL due to no need at this present time. But that is besides the point.

The issue is as follows:

If I go to http://example.info it will take me to http://example.net.

However if I go to https://example.info it will prompt for a password, sign in and it lets me in, and I see the proper site that I was anticipated.

Both sites have their own folders and when going to their Index.html file it works without issue.

When I go to Websites settings of Server, the Domain name shows properly, IP address is set to Any, Port 443, SSL Cert set to one that is for my server created when I installed the OS on my Mac Mini, Store Site Files points to the right folder where the index.html is located, Index Files: shows only index.html.

When I remove the SSL Cert nothing works properly.

As a side note the .info mail is working properly without issues.

This issue occurs both inside my network and outside my network, which leads me to believe that there might be an issue with a config file.

This was something that had worked up until 2 months ago. The change is that I had to remove a Cisco Firewall when I left my previous job, however even when I did that the site was still working internally but externally it was not due to not having the routing handled properly. Shortly after that I moved to a different state. Up until now I have not had time to work on getting everything. It was not until tonight that I realized that I found that it was not working. I have restarted my system, turned settings on and off. None of that has helped out at all.

I have learned early on that once my Mac Server is up and running that the best thing is to simply leave it be and it works without issue. I check in on it once a week to install an possible updates for it and reboot only as needed per an update but for the most part I rarely need to do any other maintenance. As a whole though noone else has access to it so I know noone else modifys it.

Tech info:

Mac Mini Server 2.3GHZ Intel Core I7

OS X Version 10.8.4

Server Version: 2.2.1 (169)

MAC MINI SERVER (LATE 2012), OS X Mountain Lion (10.8.4)

Posted on Jul 22, 2013 11:40 PM

Reply

Answer 1

Jul 23, 2013 7:14 AM in response to saross0219

I'm not sure I understand the question.

HTTPS expects TCP 443 and the target web server needs a cert. If you remove the cert, then attempts to connect via HTTPS can, should and will fail. HTTPS is also sensitive to correct DNS translations, as the certs are tied to the domain names, and the client verifies the certificate (which can include multiple domains) using the DNS translations, and the contents of the trusted roots.

Reply

Answer 2

saross0219 Author

Level 1

0 points

Jul 23, 2013 10:12 AM in response to MrHoffman

Two different sites, one with .info and one with .net. One works perfectly without issue and they each have similar settings in Server, however one only seems to want to work using https prefix. The sites are both different and therefore needs to be accessed with http at this point. The problem is when I go to http://example.info it takes me to http://example.net which is not what needs to be occuring. This occurs internally and externally. Before the move I did my server was doing DNS as well and those settings have not changed or been modified except when I had to change their outside static IPs.

Reply

Answer 3

Jul 23, 2013 11:18 AM in response to saross0219

Since the site configurations are similar, work through the settings of each, comparing the details.

Given the key detail for selecting the target server is the client's view of DNS, confirm that the client is getting the expected DNS name from whatever DNS server is hosting it. The target name that the client gets is the name that the web server will use to locate the virtual host; the web server's DNS configuration is not involved here.

It's also possible for a rewrite rule to toss the translation to a different site; that'll require a direct look at the httpd configuration files.

Reply

Answer 4

saross0219 Author

Level 1

0 points

Aug 11, 2013 10:17 PM in response to MrHoffman

So for some reason the site disappeared from the config and when I readded it fixed the issue. Guess in this case it was just re-adding the site into the websites part of Server. I did however check out the configs prior and everything was as they should be. Thanks!

Reply