• Resolved Dave McHale

    (@dmchale)


    I have this plugin running on multiple sites (love it, thank you!) and haven’t had an issue until now. I just tried to install on a new site and get the error above in the title when trying to enable Full WAF mode, when I tried using the wp-check code I found in another support post (https://nintechnet.com/share/wp-check.txt)

    I’m stuck trying to determine what “error #4” actually IS. In the code there is nothing setting NFW_STATUS to 4 directly, and no calls to nfw_quit() are made with a parameter value of 4. I assume the $ret value sometimes contains it but don’t know why/when that would be the case.

    Is it possible this is a simple database connection issue? I found another post which indicated a backslash character escaping a single quote in the database password could be an issue…. I checked the db password in use and there IS a backslash character, but it does not immediately precede a single quote. Are ALL backslashes “bad” for this plugin?

    My client’s team manages their database, so I’m hoping I don’t need to ask them to update the credentials just to get this plugin working – but if that’s the issue, I can try to go down that road. I just wanted to ask for help to know what exactly I was working with before troubleshooting further at this point.

    Thanks in advance!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author nintechnet

    (@nintechnet)

    The problem is that some users had passwords with single quotes [‘] and thus WordPress was adding a backslash [\’]. So we had to remove the backslash.
    That’s a pain to deal with.

    I will check how to fix this issue once for all in the next release which should be available next week.

    Thread Starter Dave McHale

    (@dmchale)

    Gotcha, that makes sense too. Thanks a lot, and I will keep my eyes open for the next update!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘NinjaFirewall is loaded but returned error code #4’ is closed to new replies.