Forum Moderators: phranque

Message Too Old, No Replies

MIgration issues.

         

jamescoy

11:07 pm on Apr 21, 2007 (gmt 0)

10+ Year Member



I just bought a new Macintosh and migrated all my files from my old Mac (including a binary for Mac version of Apache2.) I quickly discovered that that binary is no longer supported for the new Intel Macs. So, I found a site which gave me directions to install Apache 2.2.4 which I did. I then moved over all my htdocs and my httpd.conf file from the old installation to the new one.

A series of problems have arisen. Initially, when invoking my web site, I got the message that I didn't have permission to access the (/) [root i suppose?]. Then I fiddled with the config and ended up with the Apache page which says something like "surprised to see this page?" so I knew the server was working, but it wasn't accessing the htdocs properly.

It then occured to me that there might be remnants of the original binary Apache2 installation on my system, and sure enough, I discovered a startup item for the old version. I have removed that and now after starting Apache, my browser tells me I can't access a redirect I had set up. (When I originally set up the site, I had to redirect to port 8111 and use a "www2" before the name of my site.)

My DNS update software seems to be configured correctly and reports no errors. According to my httpd.conf file, Apache is listening on both port 80 and port 8111. Nothing has changed on my router, and I'm using the same IP config that I had on the old Mac. Now I'm stymied as to why I'm running into this issue.

Is my error in my httpd.conf file?
Should I not have just moved over the old httpd.conf file from the previous installation (2.0.59)?
Is there some other config file that I need to change?

Thank you for any suggestions.

coopster

1:37 pm on Apr 23, 2007 (gmt 0)

WebmasterWorld Administrator 10+ Year Member



Welcome to WebmasterWorld, jamescoy.

Although it takes a few more minutes of your time, I would highly recommend going through new configuration files comparing your previous directives to the new directives, adding and updating as necessary. <VirtualHost> containers included. And especially between major releases or revisions!

As always, watch your logs, they will be the first place to let you know where your errors start.