If you want to eliminate the fedora box as the cause very quickly,
enter this in your hosts file;
127.0.0.1 “www.yoursiteaddress.com”
(without quotes, of course)
Then FROM THE SERVER, enter your “www.youresitaddress.com” in the browser bar and, if it is working correctly, it will resolve to your site on the server.
more info , might be useful, maybe not.
Lastly, and I ask only to clarify, are your WordPress files and folders themselves chown’ed yourusername:webgroup ?
Or, are they too, apache:webgroup?
..and just a personal note: I have never had any problem quickly trashing the stability of every fedora distro I’ve ever attempted to use as a server. š Have you ever given CentOS a try?
I added the name of my domain to the /etc/hosts entry 127.0.0.1, and tried both “localhost” and “127.0.0.1” from the URL bar. Both resolved properly to the correct name (www.myhostname.com) but neither one loaded the page. So, I guess there’s a problem on the Fedora box somewhere. I just don’t know where.
The WordPress files and folders are chown’d to apache.web. Is that a problem?
Never considered CentOS, no. However, I’ve had a similar experience with Fedora; I’ve had to restore this sucker about 5 times in the last year. I just figured it was because I’m not a competent system administrator. Are you saying other Unix incarnations are more stable?
I’ve had a CentOS 4 servers setup for two years, going through three different sets of hardware. I also use CentOS at work.
@pweingart,
I’m assuming you had no problem with it using those same settings previously? The right way and the wrong way is a tough call sometimes. I guess it depends on your level of exposure. I still try to make sure my security measures are reasonable, just because I love to learn, but that isn’t my main focus, so take this with a grain of salt. Here is how I run my development servers (used for intranet exposure only) at home, and at work.
/www/html, chown root:root
/www/html/www.mysite.com, chown myusername:apache
folders 755, files 644
Apache runs as apache:apache under the default user/group. I then create a simlink for each of my sites to my home folder, and use WinSCP via SSH (yes, yes, I admit it. I’m glued to XP PRO way too much for my own good), across the network for file transfer. I’m sure you might get a few other suggestions, and depending on what you do with your server, it’s well worth some research into best practices.
Never considered CentOS, no. However, I’ve had a similar experience with Fedora; I’ve had to restore this sucker about 5 times in the last year. I just figured it was because I’m not a competent system administrator
Not unexpected. Fedora is Red Hat’s test bed. Bleeding edge and early app development if I’m not mistaken. I think CentOS is RHEL with the branding and support removed. Same critter, just rebuilt from source with a different paint job.
@jeremyclark13,
I’m an amateur in every sense of the word, but CentOS has really been a great education for me. I have all but tossed anything Debian (server-wise). We have CentOS 4 serving apps to multiple facilities all day, every day. Rock solid. I use 5.2 at work and at home as well.
All the best.
Cj.
I’ve eliminated DNS and IP setup as the source of the problem. I can ping my domain (“ping http://www.mydomainname.com”) and get timely replies. I can run index.php with a simple “php_info()” call, and it works fine. But when I attempt to reach the WordPress web page by any means, it hangs. I’ve tried browsing the URL (http://www.mydomainname.com), browsing “localhost,” and browsing the host’s IP address. In all cases I get the same result: 90 seconds of waiting, then a timeout.
Help! My web page has now been out of service 30 hours, and I’m losing readers.
Just ball parking here….
-fresh install: did you put an exception in your Linux box firewall for ports http/https
-did you try having someone access from outside your own network/or another terminal
-SELinux employed -and-or- being problematic?
-did you remember to add your user to the web-group (if all your access attempts have been from the server, and I’m laughing ’cause I don’t know if it really matters!)
-post your bog url, if you feel comfortable with that, and lets see what the outside world can see.
First question sounds like the right one. I did not create an exception for ports http/https.
What file would contain that exception?
I will assume you installed core 9 with the GUI. If not I apologize for the following. It’s been a couple weeks since I messed with Fedora.
System > Administration > Security and Firewall >
Firewall Options > tickboxes for http and secure (https)
(Sorry, man.. I’m running on Budweiser and swiss cheese brains at the moment…) I think that gets you there.
If you’re shellin’, I think you need to;
su -, (root password), system-config-securitylevel.
oww. my head hurts…
Sorry about your head.
Yes, that was the problem. And yes, I’m gui-ing. And I’m also documenting the steps, ’cause that one had me locked out for a whole damn day.
Thank you very much for your help.
You’re welcome!
I’m glad it turned out to be something simple.
