Hi,

It was all working fine when I finished yesterday.
But now I can't access via HTTP at all.

My .htaccess is empty, as it was yesterday.
I really haven't changed anything in the default apache install, apart from adding a couple of virtual hosts after which it was all working fine.

Konqueror returns '178.79.180.194: Connection refused'

Windows (meh) diagnostics returns;
'The device or resource 178.70.180.194 is not set up to accept connections on port "The World Wide Web service(HTTP)" '

Can anyone suggest a reason for this, please?

EDIT;
An install of ISPConfig failed yesterday, and I haven't yet got it to install properly.
Perhaps that is related, does ISPConfig mess with your settings (even before the install hangs

Sounds like your webserver isn't running or at least listening on that port.

1) Try restarting your web server
2) If that doesn't work what's the output of netstat -lpnt say?

_________________
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

ISPConfig does install or change firewall scripts. It may have changed your IPTables. iptables -L and see if port 80 is open. Although I believe port 80 is open by default. ISPConfig may have failed before it opened the port again.

Thanks @obs and @The Other Air Force.

Tried server restart but still the same.

I can't even log in via ssh.

I think it must be the ISPconfig install fail.
I followed the docs on here, but notice that it says somewhere that they don't always work.

I think best plan is to flatten entire install and do it again.
Ho hum.

Thanks again for your help, guys.

Try logging in with Lish and see if you can fix it up. The Linode directions are inaccurate for ISPConfig. The developers specifically stated in their forums that Linodes instructions will most likely result in a broken installation. It's likely all firewall trouble. Try logging in and flushing iptables and see if you can ssh in then. Keep in mind that doing so will remove all your firewall rules.

If you want to start over with ISPConfig i'd recommend starting fresh if you can and googling ISPConfig + your Linux distro. You should get results from Howtoforge with a step by step. You will have to skip the first few pages because they describe installing Linux and configuring networking which Linode will have taken care of. Avoid stackscripts and just do a bare install.

If you can't start fresh try posting the results of the ISPConfig install script and the failure. You can always run the install again. Check the ISPConfig logs in /var/log and see if it mentions a particular point of failure. Its pretty good at recovering I think. Never had any big issues myself.

@The Other Air Force,
Thanks for your thoughtful words.

Very useful suggestions which would have been invaluable had I had to fix what I had rather than starting again. I was installing ISPconfig onto a fresh server and LAMP install, so starting again from scratch seemed the best option - it's all good practice.

I did try running the ISPconfig install again, but it hung at the same point.

For anyone else that finds this useful, there are instructs for ISPconfig on Ubuntu 10.04 here;
http://www.howtoforge.com/perfect-serve ... onfig-3-p3

I tried using ISPConfig to setup rules, and ended up locking my server. Unlike TOAF, I was still able to get in through PuTTY using SSH and reset IPTables back to the settings Linode gave. Thus allowing me to have another go. (Being a little more careful this time lol)

I tried again, this time I made sure I included the port I chose to connect to via ISPConfig (default 8080) and ISPConfig is still running. Everything seems to be working ok now. (Wonder how long I will have to hold my breath for? )

_________________
My VPS system:
(Ubuntu 14.04 LTS, Kernel 3.15.4-x86_64, Apache 2.4.7, MariaDB Server 5.5.40, MariaDB Client 5.5.41, PHP 5.5.9, ISPConfig 3.0.5.4p5, Webmin, PureFTP & Quota, phpMyAdmin, postfix, dovecot, amavis, clamav, spamassassin, awstats, fail2ban, Jailkit, bind9, vlogger, webalizer)