OpenLiteSpeed Wordpress Droplet Blocking My IP (Rest of the world works fine)

June 21, 2019 1.2k views
DNS PHP OpenLiteSpeed WordPress 1-Click WordPress Ubuntu 18.04

Hi There,
Yesterday without doing any updates to Ubuntu, OpenLiteSpeed, or Wordpress/Wordpress plug-ins, I suddenly started getting 503 errors when trying to access my website. However, things worked fine from my phone with the wifi off.

So, from any computer connected to my broadband connection with my current IP address:

  • I can not access my wordpress site at http://domain.com or https://domain.com
  • I can access the OpenLiteSpeed control panel at https://xx.xx.xx.xx:7080
    From this I assume access to the server is working, and something on the virtual server is blocking me
  • I can not access my website using https:///xx.xx.xx.xx From this I assume it is most likely more than just a domain issue
  • I can access the OpenLiteSpeed control panel at https://domain.com:7080 From this I assume DNS is fine and that something locally is most likely not blocking me.
  • I can not access PhpMyAdmin at http://domain.com/phpmyadmin or http://xx.xx.xx.xx/phpmyadmin *From this I assume its not a Wordpress issue as phpmyadmin exists outside of the wordpress directory

I have tried changing the virtual server to a new folder with a blank index.html file. This still did not work.

Is there anything built in to OpenLiteSpeed that would ban my ip address from accessing that virtual server? I’ve gone through every setting in the control panel and even added my ip to any whitelists i could find.

Thanks for your time!

1 comment
1 Answer

Hi Jack,

I saw the same question posted in OLS forum, so I just copied the response again in case you missed it.

503 errors are often caused by a malfunction in PHP, and are not related to Web Server nor IP banned.
In this case, you can check the error log, and past the log here or DM me. 

More debug method for 503:
https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:503-errors

Best,
Eric

  • Hey Eric,

    So, it ended up clearing itself up exactly 24 hours after it started. So, some part of my setup… somewhere must of banned my IP for 24 hours.

    Thanks for your help! :)

    -Jake

Have another answer? Share your knowledge.