Support

Admin Tools for WordPress

#30303 – Optimize WAF with Litespeed + suphp technology?

Posted in ‘Akeeba Admin Tools for WordPress’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Friday, 28 September 2018 11:10 CDT
Chacapamac
Optimize WAF with Litespeed + suphp technology?

Can it work?
 
Monday, 01 October 2018 02:33 CDT
tampe125
Hello,

there's only one way to find it out: try it :)

Seriously, please give it a try and tell us if you get any issue. I'd strongly suggest to try it on a test site, since things may break.

Thanks again for your tests!


Davide Tampellini

Developer and Support Staff



Italian: native

English: good



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Monday, 01 October 2018 10:32 CDT
Chacapamac
Should I choose:

—> Litespeed/Asapi

or

—> Apache + sulpha

I have to test live, if it “break” what I do?


Just a remark: (I think it’s the same in Akeeba backup in Wordpress)
I sometimes get that error when clicking a save button (only in Safari)

White page with error:
Safari can’t open the page “https://mywebsite/wp-admin/admin.php?page=admintoolswp/admintoolswp.php&view=HtaccessMaker”.

The error is: “The operation couldn’t be completed. Software caused connection abort” (NSPOSIXErrorDomain:53)
 
Monday, 01 October 2018 10:49 CDT
nicholas
You need to use the Apache + CGI/FastCGI or Apache + suPHP option (they are, in fact, the same). These apply to all servers which use CGI or FastCGI to load PHP. Since you're using suPHP your PHP is configured to run as CGI or FastCGI (suPHP can't work otherwise), hence my suggestion.

Regarding your intermittent issue, it actually has nothing to do with our software. It's your Mac failing to resolve the domain name (DNS failure). This typically happens when your network is momentarily disconnected. If you're using WiFi that would be the case. I had that problem every time I was using a wireless baby monitor. The darned thing was using the same 2.4GHz band as my ISP's WiFi router. I have since stopped using the WiFi-killer baby monitor and moved to a better (and much more expensive, ouch) NetGear access point which solved this problem. Finally, the problem may also be caused by third party software, see https://appuals.com/error-nsposixerrordomain-on-mac-os-x/


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Monday, 01 October 2018 13:11 CDT
Chacapamac
You need to use the Apache + CGI/FastCGI or Apache + suPHP option (they are, in fact, the same). These apply to all servers which use CGI or FastCGI to load PHP. Since you're using suPHP your PHP is configured to run as CGI or FastCGI (suPHP can't work otherwise), hence my suggestion.


I try both Apache + CGI/FastCGI & Apache + suPHP Option
Both, I get “Prepend activated” but coming back (after many minutes) bring back the choice “LiteSpeed/Asapi” with a warning —> Admin Tools is correctly setup but the changes have not yet taken effect. If you are using LiteSpeed as your web server or CGI/FastCGI interface, please wait a couple of minutes for the changes to take effect. Please refresh this page to check if the configuration was really applied.

I try LiteSpeed/Asapi and it seem to work, saying:
Admin Tools is now running before any PHP files, granting you the maximum protection.

The hosting support told me that they use —> Litespeed + sulpha technology ???


For the White page with error: It only happen in Safari Version 11.1.2 (11605.3.8.1) — Work perfectly in Firefox Dev edition 63.0b10 (64-bit) ???
 
Tuesday, 02 October 2018 10:17 CDT
nicholas
OK, use the one that works. Litespeed does not really have a good package I can easily test with. My experience with it is mostly debugging clients' sites and my own blog at Rochen.

Regarding the blank page, I told you what it is. You can Google the error message if you don't believe me :) I suspect that Firefox doesn't display the error because it actually retries to connect in the background, i.e. if your connection goes away momentarily it will keep retrying to connect. Even if it does display an error message after a while (I believe 30 seconds?) it keeps retrying and will display the actual page when the connection comes back. Not Safari. Safari seems to be very aggressive on power conservation so as soon as it detects a network issue it throws an error and that's it. It won't retry. It expects you to fix the problem and hit reload.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Wednesday, 03 October 2018 03:40 CDT
Chacapamac
Thank You Nico and good Day!
 
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.