After 5.0.4 upgrade, web servers are no longer reachable over the internet

Question

‹db› Author

Level 1

43 points

After 5.0.4 upgrade, web servers are no longer reachable over the internet

I upgraded Server to 5.0.4 from 5.0.3 yesterday. After upgrading, the server Websites panel reports the status:

Users may not be able to access websites from the internet

And for each of the individual web sites in the list server states:

Not reachable. This web site is not available over the internet

No further explanation as to what the actual problem is or how to solve it is given. What the ****, Apple?

I did a Time Machine backup just before upgrading, and haven't allowed another backup to be done, just in case I need to restore. But I really would like to get this up and running instead. After looking around at the configurations and finding nothing obvious wrong with them, I decided to try recreating the sites from scratch in the Server user interface.

First, I used the Server user interface to delete each of the site configurations in the Website panel list (except "Server Website" and "Server Website (SSL)" which cannot be deleted). I also removed corresponding configuration files (and any .prev and .orig files) in /Library/Server/Web/Config/apache2/sites. Then I reset the web service to factory settings with:

sudo serveradmin command web:command=restoreFactorySettings

Then I used the Server user interface to create a brand-new site configuration for one of my sites, setting the domain name, pointing it to the data files location, and so on. Yet even after saving the new configuration, the sites (both "Server Website" configurations as well as my new one) still say "not reachable".

Can someone please tell me what is wrong here?

Mac Pro, OS X Yosemite (10.10.5)

Posted on Oct 7, 2015 2:48 PM

Reply

Answer 1

Linc Davis

Level 10

209,541 points

Oct 7, 2015 5:39 PM in response to ‹db›

Is the site, in fact, reachable?

Reply

Answer 2

‹db› Author

Level 1

43 points

Oct 7, 2015 5:41 PM in response to Linc Davis

No, none of the sites are reachable. 😟

Reply

Answer 3

‹db› Author

Level 1

43 points

Oct 7, 2015 6:24 PM in response to ‹db›

Ok. I solved the issue myself. After trying to restore both /Applications/Server and /Library/Server/Web/ and not having good results, I decided to reinstall the new version of the Server application.

During initial startup after that I noticed the license agreement had a "Use Apple services to determine reachability for this server" (or something to that effect) check box at the bottom which was enabled by default. After disabling that checkbox and continuing first run, the web service was once again operational! 🙂

It looks like you can manually disable or enable reachability testing in the Server app under: server > Overview > Internet > Reachability Details.

Reply

Answer 4

Linc Davis

Level 10

209,541 points

Oct 7, 2015 6:41 PM in response to ‹db›

I'm glad to see that you solved the problem, but I don't understand how you solved it. Checking the sites for reachability wouldn't have any effect on whether they actually were reachable, as far as I know.

Reply

Answer 5

wineguy

Level 1

4 points

Oct 7, 2015 7:07 PM in response to ‹db›

I am having the same problem - websites no longer being served.

I tried toggling the reachability service, no change. Perhaps it was just your reinstall that worked.

Reply

Answer 6

‹db› Author

Level 1

43 points

Oct 8, 2015 8:55 AM in response to wineguy

I'm not sure what actually caused it to work again - and at this point I really don't care, honestly. You're probably right that the downgrade and re-upgrade had something to do with it. It seems like Apple's upgrade scripts are quite buggy!

Now I'm in the middle of figuring out why SSL connections are broken and a couple other things.

Apple really screwed this update up, IMHO.

Reply

Answer 7

wineguy

Level 1

4 points

Oct 8, 2015 9:01 AM in response to ‹db›

I solved my problem too. The hard way. I did a complete wipe and am starting over from scratched (backed up only the sites themselves). Nothing else seemed to work. Not reinstalling Server, not deleting or altering any of the Apache config files.

Long way to go to get it all back, but for now basic web service are restored and I can sleep (I am currently in Asia doing all of this remotely).

Reply

Answer 8

‹db› Author

Level 1

43 points

Oct 8, 2015 10:12 AM in response to wineguy

I feel your pain. 😟

Reply

Answer 9

‹db› Author

Level 1

43 points

Oct 8, 2015 10:54 AM in response to ‹db›

The drama continues...

Links to simple web pages like http://hostname/blah that used to work fine are failing saying the browser can't connect to hostname:34580/blah/.
Xcode now forcefully injects itself into base website URLs, turning them into http://hostname/xcode/.
Web forms like http://hostname/blah.php?param=blah that used to work now fail with proxy errors after the update.

This new web proxy nonsense has completely screwed up web serving in OS X Server.

I'm pretty miffed that Apple would make such a drastic change with little to no warning or explanation to customers, nor any sort of active support to help them with these issues.

I'm about ready to just buckle down and spend a day or so installing an entirely separate Apache stack because this stupid proxy situation is causing more headache than it's worth! I'm guess I'm somewhat lucky I am not hosting anything really critical in OS X Server's web service at the moment. But I do have several web sites hosted by OS X Server and do want them to function correctly - preferably without having to spend a day installing and configuring what was already set up correctly in OS X Server! And I don't think that is an unreasonable position for me to take. If I am honest, I feel completely jilted by Apple.

One thing is certain: I'll forever be extremely wary of OS X Server updates from now on! This one has not been worth it.

Reply

Answer 10

‹db› Author

Level 1

43 points

Oct 8, 2015 11:48 AM in response to ‹db›

Just a correction to my original post:

I upgraded from OS X Server 4.1.5 to 5.0.4.

I'm in the process restoring 4.1.5 from backup to see if I can get it up and running again. If so, I'll just refrain from upgrading again until I am absolutely sure Apple has fixed this complete mess.

Reply

Answer 11

‹db› Author

Level 1

43 points

Oct 8, 2015 12:16 PM in response to ‹db›

Just reporting back:

Restoring /Applications/Server and /Library/Server/Web from the Time Machine backup I made just before the update followed by restarting the machine got me back up and running with Server 4.1.5, and all web services are functioning perfectly.

Reply

Answer 12

Gandycz

Level 1

18 points

Nov 25, 2015 1:16 AM in response to ‹db›

Try edit those files /Library/Server/Web/Config/apache2/sites/

there is file call like 0000_127.0.0.1_34580_site domain.conf.

Just delete in 2nd line that hostname port. If your line is like example.com:34580 delete port and keep it like example.com

then restart web service in server.app and done.

Reply