When the new database is able to integrate with our servers, the system will be updated accordingly. Mod_GeoIP is a legacy database, and has been replaced by Mod_MaxMindDB, but at this time it does not integrate with the Apache web server.Multinational corporations often have an IP range based on where their headquarters are, this could result in false positive results for these users.Users can always get around a country allow/deny access by using a VPN/proxy.New IP ranges will take some time to appear in the database or may be mapped to the wrong country initially. The country database is estimated to have 99.8% accuracy, but that isn't perfect, so it should not be used for critical applications.The Mod_GeoIP database has been compiled by MaxMind, a third-party provider.This can be used to deny/allow access to your website. The default LSPHP that comes with a LiteSpeed Web Server installation is lsphp56, so you can solve the problem by replacing it with the higher version that is installed by Plesk.All our shared/enterprise/reseller hosting servers include Mod_GeoIP, which is a database that can be used to map a website visitor's IP address to their country. The issue occurs when Webmail uses PHP with minimal extensions, and some essential PHP extensions for the Webmail application are missing. In Plesk Obsidian 18.x, you may encounter an issue where the page returns a 500 error. Edit /usr/local/lsws/conf/httpd_config.xml, insert the line 1 anywhere between and, as seen in the screenshot below, then restart LSWS, killing lsphp if necessary.This occurs when open_basedir protection is set to, though this will not apply individual open_basedir to each subdomain. You may encounter random PHP 500 errors on domains with multiple subdomains. Now all of the handlers will use same lsphp binary that is controlled by the CloudLinux Selector. Be sure to change Handler Name to lsphp_selector for each suffix, as seen in the screenshot. Login to LSWS WebAdmin Console by accessing Follow the instructions in the CloudLinux support documentation to set up the lsphp_selector external app, as seen in the screenshot.Īfter the external app is created, go to the Script Handler page, and create multiple handlers php, php44, php51, php52, php53, php54, php55, php56, php70, php71, php72, php73. This will completely disable the Plesk PHP Selector, which means no matter which PHP you choose in Plesk Selector, it will have no effect at all, and only the setting in CloudLinux Selector will be obeyed. If Plesk PHP Selector is no longer needed, since CloudLinux PHP Selector pretty much covers all of the PHP settings and extensions, you could choose to use CloudLinux PHP Selector exclusively. Please note, you must choose fastcgi in order for LSWS to work properly. Use Plesk PHP Selector to choose an alt-php, such as alt-php51-fastcgi. There are two possible solutions for this issue. If this issue impacts you, no matter what PHP version you choose in CloudLinux PHP Selector, PHPinfo shows the PHP version that was selected in the Plesk PHP setting. This may interfere with LiteSpeed Web Server, Plesk PHP Selector, and CloudLinux PHP Selector. LiteSpeed Memcached LiteSpeed MemcachedĪ recent Plesk update changed the PHP configuration within the Apache configuration.LSCache Developers Guide LSCache Developers Guide.LSCache Without a Plugin LSCache Without a Plugin.Troubleshooting Troubleshooting Table of contents.WHM LiteSpeed Plugin WHM LiteSpeed Plugin.External Applications External Applications.LiteSpeed Web Server LiteSpeed Web Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |