I’ve been running Litespeed Web Server for 2 weeks on a trial license with no problems. As soon as the trial ran out my sites went down so I purchased a license and activated it on my server but my sites are still down. LSWS shows the license as being fine. There has to be come configuration problem. I’ve tried looking at what logs I know of, restarting the service, the server but nothing is working. The LSWS panel and Interworx both show everything as being fine but as I said, no sites will load.
I’ve checked the firewall and that’s fine. Apache is of course disabled. I even tried reinstalling LSWS and it shows that it’s running but I don’t see any errors and it won’t serve up anything on 80 or 443. I can’t even switch back to Apache to get my sites back up and running. It won’t serve anything either.
If anyone can help me troubleshoot this I’d be grateful.
If your 100% sure your services are running and no blocks on port 80/443, then it has to be higher up the network path outside of the server
Have you cleared your cache
Are your DNS records correct and resolving correctly
Are your siteworx accounts been hosted in the correct IP address
Does a tracert correctly goto your server
Does your server correctly show IW-cp and can you login to IW
Have you checked what service is using port 80/443
If you want to pm me a domain, I can test if live from here, as given your post, and knowing your very knowledgable, seems strange which is why I think it might be at a higher level which is blocking your port 80/443
I have checked a little (but could be entirely on wrong domain/Ip), but it looks like your IP address ending .205 is displaying correctly, ie litespeed but your IP address ending .206 is not
Have you checked to make sure this is included in litespeed
If your not using .206, and only .205, then your DNS is wrong
As I said, I could be wrong as its guess at your server for checking, but to confirm if I’m correct, is twilightservers correct
eh. I kept reading 206 as 202. checked ifconfig and I think the subnet mask somehow got messed up since i can’t reach 206 (The shared IP of the server)
HI synthetisoft
Makes sense, and glad I was on correct domain/IP.
Hope it helped to track the issue, and should be easy to resolve now.
Please see pics of 2 traces, one to 205, and one to failing 206, so you can see where it fails, but without knowing your setup, could be on your system.
If you need anything further, please let me know
Many thanks
John
Where do I change it? there’s no ifcfg-eth0:1 :2 :3 and so on files as I would expect and you can’t change it from within interworx. Does interworx have some list of virtual adapters or a script I need to edit?
If so, the filename is slightly different in name and can be generic to your server. Also, you may have a bridge etc depending on your vps software for server
If full dedicated, then your file name is usually correct, but depends upon your server and number of nics on server.
Some of our servers have minimum of 4, and are not called eth
Can you post a screenshot of your folder /etc/sysconfig/network-scripts
I think from memory anyway
There is also a virtualhost file, from etc/ I think but you may have to look for it, which sometimes contains multiple entries, and just needs manually checking/correcting
Strange… IW would not remove those and if 202 and 205 are on same server, where are they held
Your still offline so you may need to restart your network but a word of warning, if your network is wrong, and you restart network, you may lose all connections unless you have separate access like KVM switch
If this does not work and your network comes backup, in the short term I would reset DNS and siteworx accounts to use 202 and not 206, as 202 is working.
Then take the time to fully look over what’s happened and bring back 206
Strange… IW would not remove those and if 202 and 205 are on same server, where are they held
Your still offline so you may need to restart your network but a word of warning, if your network is wrong, and you restart network, you may lose all connections unless you have separate access like KVM switch
If this does not work and your network comes backup, in the short term I would reset DNS and siteworx accounts to use 202 and not 206, as 202 is working.
Then take the time to fully look over what’s happened and bring back 206
Many thanks
John[/QUOTE]
This doesn’t make any sense though because ifconfig shows all the IPs on my system. I just rebooted the system and it had no problem bringing them up. So where are they coming from? I’ve looked through every file I can think of in /etc
the interface config isn’t setup for dhcp. Also, I remember setting them up in interworx but I didn’t use the wrong netmask and they were working before. I have no idea what’s going on. I could go shifting IPs around and deleting them but I think that will break my SSL and be a pain. But if for some reason I have no choice. I don’t get it…
Sorry, your making changes I guess, as twilightservers 205 is no longer working, but trace is fine
I have to go for a little while, but I’ll check back later
You may want to open a support ticket with IW, as IW support would have access to your server if you did, and could quickly work out what’s gone wrong and correct, whereas I don’t have access sorry
I figured it out this morning and finally crashed to sleep. I feel ridiculous for spending so much time on it. It was just a null route by my ISP for an abuse report I hadn’t noticed. Thanks for the help. I would still like to know where those network entries are though.
