I am trying to install wordpress on my linode, having completed all the basics. The problem is that I cannot access the domain. Both firefox and chrome show a connection reset.

Now I should mention I'm not very familiar with Linux, but I did exactly follow the documentation, I've checked these forums, and I find most things in order. I have no idea what could have gone wrong, so any help is appreciated.

If it helps, the domain is hokpok.com

Firefox gives indeed an "Unable to connect" error.
You will have to give some more information:
What did you install: OS (debian, ubuntu, centos, ...) apache or nginx, mysql, php
Have you registered the domain name and added the linode DNS servers?
Have you added your site to the linode dns servers
...

cheers

Sorry for not being specific.

I have Ubuntu 10.04, Apache2, mysql, php. And an incomplete wordpress install because i never could open the site.

I have set the DNS and it appears to be correct. Set the nameservers, and added to the DNS manager as well.

I do not know when you have done this, but it can take a couple of hours (up to a day) before DNS changes take effect.
What you can do is a wget from the commandline on your server:
wget http://www.hokpok.com
or
wget http://hokpok.com
or
wget http://yourip
If this doesn't work, there surely is something wrong with your webserver.

Have you tried with just an index.html (with some text) to see if that works? To see if apache is set up correctly?

Next step info.php file (<?php phpinfo(); ?>) to see if php is set up correctly.

Restarted apache?

I am learning how to set up a webserver with nginx, so this is probably as far as I can help you.

A quick port scan shows nothing listening on port 80 so either
1) Your web server isn't running
2) Your firewall has port 80 closed
3) Your web server is running on a different port.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

wget gives me an error.



It does resolve the correct IP though (my linode's public IP)

Cannot access index.html either. Is there anything short of rebuilding that I can do?

@obs any way I can have port 80 running then? I don't think I installed a firewall.

Type "ps -C apache2" (without the quotes) into your terminal. You should see at least a few lines that say "apache2". If not, Apache is not running.

If Apache is not running, try restarting it with the command "/etc/init.d/apache2 restart" (without the quotes). You might need to prepend "sudo" if you're not logged in as root. Do you get any error messages? If not, does it work now?

It seems the problem really is with apache. Entering ps -C apache2 simply shows "PID TTY TIME CMD"

So I tried restarting apache with /etc/init.d/apache2 restart and it failed. This was the output I got:



what should i do next?

You probably have a syntax error in one of your Apache configuration files. Check for error messages in /var/log/apache2/error.log

Doesn't apache usually give a config file and line number when it has a problem with the configuration? It's been awhile since I've edited apache's config files on another server that I admin, it worked perfectly (a bit laggy at times) after I configured it awhile back, so I can't remember, but I though it always gave the config file and line of the incorrect setting?

It usually does, but I've read about cases where Apache just fails to start. There might not be anything in the logs, either.

Another possibility is that a PHP module is crashing. It happens from time to time, for no apparent reason. Opcode caching extensions (APC, eAccelerator, and XCache) are the usual suspects.

The init or startup scripts do not usually pass the error back, so you have to go look in the logs, but there, yes, you should get the file/line that is causing the issue.

all i get there is "Unable to open logs."

Should I try to rebuild?

A quick search on google suggest you may want to make sure that the /etc/apache2/logs actually exists.

A couple people solved the same error by simply making that folder.

I hope this helps and good luck!

*EDIT

In your case, the path would actually be /var/log/apache2/

I dont know why the forum I chose to copy from used the above path.

Also check your disk space if you haven't, make sure your not out.

Good luck again.