Topic: Accessing SME web pages from local network

[Jason Judge]

Hi,

I'm having a bit of trouble accessing local sites on my SME 5.1.2 box. I'm sure it was working a few days ago, and now it is behaving strangely. Here is the setup (simplified to help describing):

The server is set up as a server and gateway. Internal IP is 192.168.1.1. External IP is 80.80.1.1
I have a local domain: me.com
I have set up an i-bay: ibay
I have a virtual domain: ibay.me.com which points to the site on ibay.

Now the fun begins.

On the local network I can ping me.com and get IP 192.168.1.1
On the local network I can also ping ibay.me.com and get IP 192.168.1.1

However, if I try to access the site ibay.me.com from the local network, SME thinks I am trying to access it from the EXTERNAL network. The httpd logs list the access as being to ibay.me.com with an IP 80.80.1.1

This means that I cannot access a local Intranet site unless I have opened it up to the Internet! Changing settings confirms this. I am sure this wasn't the case when I first installed this server. Something has gone awry, and I don't know what.

My workaround is to create LOCAL hosts, e.g. ibay on me.com, with a hard-coded IP address of the local side of my server (i.e. 192.168.1.1). Surely I shouldn't have to do this?

This problem affects my server-manager access too. I can no longer access the server manager at http://www.me.com/server-manager (access denied since it is not open to the Internet) - I need to use http://192.168.1.1/server-manager

-- Jason

[Jason Judge]

Now I'm getting segmentation faults on the server running PHP web pages.

I had this type of problem with SME 4 last year. The fresh install was fine, but the more I changed the configuration (note: ALL through the standard admin screens) the more flaky it got. Eventually it needed to be reinstalled. That one was not even connected to the Internet - just a local server.

I'll get to the bottom of this, but something isn't right. I'm not messing around with the core OS files - just setting up and changing i-bays, PHP sites through the i-bay shared directories and setting up virtual domains and hosts. I have a hunch something in there allows configuration errors to build up - and my hunches are normally right.

I'm getting this just before a bunch of segmentation faults (httpd_error_log):

[crit] (98)Address already in use: make_sock: could not bind to address 192.168.1.8 port 443
[notice] child pid 1311 exit signal Segmentation fault (11)
[notice] child pid 1318 exit signal Segmentation fault (11)
...

The browser accessing the page then gets a 'zero-length response' error from Apache. Not surprising considering a handfull of processes have died. They are all the httpd processes run as user 'www'.

-- Jason