ISPConfig
-
Dear Sir,
I couldn’t install it on ISPConfig VPS using Nginx, it keeps saying the path is not right, although it is picking the right path.
After I hit next and choose the php file, it comes back again to the path saying:
Error : please enter the full path to WordPress folder.
But the path that the firewall choosing is right!
Strange π
Thank you. Please let me know what to do.
Imad Daou
-
Hi,
This looks like you are having an issue with PHP sessions.
NinjaFirewall saves the WordPress folder path into $_SESSION[‘abspath’] and will check this variable when you click the “Next” button.
If $_SESSION[‘abspath’] is empty, it returns that error.Did you have any problem with PHP sessions?
Can you please provide me with a tool or howto to test the php sessions?
I don’t have problems with something else.
Do you want me to run a command to show you the log file? I run debian 7.
Thanks,
Imad
By the way, sorry but I forgot to say that I use memcached for php sessions.
Besides, do you believe your WAP plugin will conflict with Nginx NAXSI Module https://github.com/nbs-system/naxsi it’s similar to Apache Mod_Security WAP.
Thanks,
Imad
Hi,
It looks like your sessions expire very quickly, even before you have the time to get through the installation process.
Can you try to run this PHP script:<?php echo '<br />session.cache_expire : ' . ini_get('session.cache_expire'); echo '<br />session.gc_maxlifetime : ' . ini_get('session.gc_maxlifetime'); ?>Upload it to your website and go to http: //YOUR SITE/script.php.
Regarding NAXSI, there shouldn’t be any issue. All HTTP requests will be processed in that order:
Nginx > NAXSI > PHP > NinjaFirewall > WordPress > WordPress PluginsThank you so much for your prompt reply. I did upload the file and run it as you requested and the output is below. By the way, all this happening at a testing server in house. The main site that is live right now http://www.ccnahub.com is still running Apache.
I forgot to mention that my php.ini holds the following info as well regarding php session.
session.save_handler = memcached
session.save_path = “tcp://127.0.0.1:11211?persistent=1&;weight=1&;timeout=1&;retry_interval=15”script.php output.
session.cache_expire : 180
session.gc_maxlifetime : 1440Please let me know if you need me to provide you with more information.
Normally, you should use the “tcp://” substring with memcache, not memcached.
Can you try one of those 2 possibilities:
-Remove the “tcp://” substring:
extension = memcached.so session.save_handler = memcached session.save_path = "127.0.0.1:11211"OR:
-Replace memcached.so with memcache.so:
extension = memcache.so session.save_handler = memcache session.save_path = "tcp://127.0.0.1:11211?persistent=1&;weight=1&;timeout=1&;retry_interval=15"Thank you so much for your help, I am going to apply your suggestions. However, I would like to share with you that while I was waiting a response from your end, I have changed the php.ini settings as follows:
session.save_handler = files ;session.save_path = "tcp://127.0.0.1:11211?persistent=1&;weight=1&;timeout=1&;retry_interval=15"So I changed the session.save_handler to files and disabled session.save_path by semi colon.
then I did the following
service php5-fpm restart
service nginx restartAfter doing the following changes, I was able to continue with the plugin setup. However, I had to edit the php.ini manually sine the plugin failed to inset it’s setting by itself. That was easy though.
Besides, I have used APC instead of memcached on W3T caching plugin. I use Fast_cgi_caching as well.
I have de-activiated the plugin and delete it, during my deletion, I got server 500 error, once I started the php and nginx, everything was fine and the plugin was deleted.
service php5-fpm restart
service nginx restartNow I am going to tested again using the memcached but this time with your upper config suggestion and I will let you know how it goes.
Thank you again for your help.
I just finish the test and it worked! with memcached.
the following settings worked well
extension = memcache.so session.save_handler = memcached session.save_path = "tcp://127.0.0.1:11211?persistent=1&;weight=1&;timeout=1&;retry_interval=15"but as memcached and NOT memcache.
the interesting part that I still got the same error as
Error : please enter the full path to WordPress folder.
but, I have retained the php.ini settings in my php.ini file and I remembered that I have commented the settings after the I removed the plugin in my first test using APC instead of memcached, however, when I have un-commented the following:
; BEGIN NinjaFirewall auto_prepend_file = /var/www/clients/client1/web1/web/wp-content/plugins/ninjafirewall/lib/firewall.php ; END NinjaFirewallAnd the moment I pressed the button again on your plugin, it got enabled and everything was fine.
Is it that the upper code should be inserted inside the php.ini before checking the path? not sure exactly what happened. however, it’s working.
I am sorry but I mean the following code inside the php.ini was fine
extension = memcached.so session.save_handler = memcached session.save_path = "tcp://127.0.0.1:11211?persistent=1&;weight=1&;timeout=1&;retry_interval=15"memcached that ends with “d” and NOT memcache
without the “d” I got 500 error.
without the “d” I got 500 error.
Maybe you do not have the memcache extension installed (php5-memcache in Debian)?
If memcached works, then it is fine.
The topic ‘ISPConfig’ is closed to new replies.