This is an old revision of the document!


Why is my LSWS WebAdmin page unavailable?

On occasion you may run into problems accessing the LSWS WebAdmin Console. We have found that in most cases this is due to it being blocked by a firewall. LSWS uses port 7080 for the WebAdmin Console/Panel by default. This port must be open to be accessible from outside of your server.

With LSWS started, run the following command from your hosting machine to check if there are any processes listening on port 7080:

netstat -na | grep 7080

If so, take a further step to verify what that process is:

curl -i http://localhost:7080

If it returns the correct output, something similar to “Server:LiteSpeed”, then the LSWS WebAdmin Console is working as intended within your server but is likely being blocked by your firewall.

At this point you should check your firewall rules and either append allow rules or remove blocking rules as needed. Use the following command to list your current rules in iptables:

iptables -L 

If using cPanel and CFS, there are options to add this TCP port to the allow list.

In most scenarios, the above steps should have fixed the problem.

If you are still unable to access the WebAdmin Console, check your LSWS admin configuration to see if the default admin listener address value of “*:7080” has been changed. If so, open the correct port accordingly. You can find the admin configuration file in:

/usr/local/lsws/admin/conf/admin_config.xml

There is an option to restrict access to the WebAdmin. If you forget to add your IP address, or if it changes, you can edit it from the configuration file in /usr/local/lsws/admin/conf/admin_config.xml:

 <security>
   <accessControl>
     <allow>XXX.XXX.XXX.XXX</allow>
     <deny>ALL</deny>
   </accessControl>
 </security>

Put your IP address in the allow list. For multiple IP addresses it looks like this:

 <allow>XXX.XXX.XXX.XXX, XXX.XXX.XXX.XXX</allow> 

If after these steps you are still unable to access the WebAdmin Console page, it is possible that some external firewall may be causing the problem. If this is the case you will have to find it and change it accordingly.

  • Admin
  • Last modified: 2018/08/13 19:26
  • by Jackson Zhang