@tonyhir, the reason webroot/wp-admin works is because the loading of Ninjafirewall is done at the /webroot/.htaccess, and webroot/wp-admin/.htaccess will not have the load instructions. I just figured this one out myself with this bug, I think…
Now, what if you ARE using an alternative port, and the DBHost has x.x.x.x:1620? WordPress connects fine but I get the same fatal error as above. Why is Ninja ignoring the trailing port?
This could be a DMZ/Firewall issues. What IPs and Ports might I need to request/receive the API Key?
I am getting the same error, but its for a MDU / Multi Domain setup. A few sites I already setup that are stand alone aren’t exhibiting the error retrieving an API key.
