I see there’s a problem on the plugin when running under MariaDB, but it’s not critical (it’s happening at the last step, when the plugin already processed everything, and is just trying to do a cleanup), I’ll get it fixed, but that’s not going to address your problem.
In order to understand what’s happening, I’ll need you to change some things in the code, which will add more details about where the problem is happening. If you’re not very interested on that, then you can wait for the next minor release (3.4.0-5), which is coming soon and these better messages will be already included.
FYI, the other messages in the log should also disappear after upgrading to 3.4.0-5.
Hi team.
I have a question about security from pkp what is the range ip from pkp ojs and pkp pn for setup in the firewall from the university because now we have a problem with the port 80 is closed. We need a setup for any exceptions for example OJS . so I need identify the range ip from pkp and any services from ojs in the version 3.3.0.8 than we have in the journal site.
Can you whitelist the IP using a hostname? If yes, then use this pkp-pn.lib.sfu.ca, it will keep things working in case we change something in the network (that’s likely to happen soon).
If not, for now this is the IP: 142.58.232.187