Hello PKP team,
We run seven OJS installations for UNIFIP (Brazil). Five journals have been stuck at “The PKP PLN does not know about this journal yet” since 20 June 2026 — about 11 weeks now.
What makes this case useful for diagnosis: a sixth journal on the same server, same OJS version, same plugin version, same hosting and same Cloudflare zone works perfectly. The only difference is that it was registered on 4 June 2026, roughly two weeks earlier.
Environment
- OJS 3.3.0.21, PHP 7.4.33
- PKP PN plugin 2.0.4-5 (installed and registered in
versions,current = 1) - Shared hosting (Hostinger), all domains behind Cloudflare (Free plan)
Working journal (control case)
| Journal | UUID | URL | Status |
|---|---|---|---|
| coopex | 88FE43B4-4610-49B4-9955-F824BEA8FF49 |
https://editora.unifip.edu.br/index.php/coopex | is_accepting=“Yes” — 26 deposits transferred, 1 already at LOCKSS agreement stage |
Affected journals (all is_accepting="No")
| Journal | UUID | URL |
|---|---|---|
| bahe | C918A3EE-BC91-423E-A1C4-F421B15CAB86 |
https://bahe.unifip.edu.br/index.php/bahe |
| obdj | 79266764-AEC2-4BB1-B825-50E2B7DA4B1A |
https://dentistryjournal.unifip.edu.br/index.php/obdj |
| enfermagemesaude | 12D8399B-628F-48F8-9EE3-8FB62118B691 |
https://enfermagemesaude.unifip.edu.br/index.php/enfermagemesaude |
| integracao | 90168D90-7924-4EC8-8B6D-9B3B5AE2A287 |
https://integracao.unifip.edu.br/index.php/integracao |
| jmhp | 84516891-5F7A-4DFE-9D7B-E83748131575 |
https://jmhp.unifip.edu.br/index.php/jmhp |
Two other contexts in these installations are institutional repositories (theses), not journals — they have no ISSN and the plugin is intentionally disabled for them.
What we have already verified
- ISSN is set for all five (
onlineIssnpresent injournal_settings) - Terms of use accepted (
terms_of_use_agreementpopulated inplugin_settings) - Plugin enabled (
enabled = 1) base_urlis correct in everyconfig.inc.php(real public HTTPS URL, nolocalhost, nopkp.sfu.cadefault)- Scheduled task runs daily and completes without HTTP errors. Typical log:
[2026-09-02 16:30:09] [Notice] PKP Preservation Network Processor
[2026-09-02 16:30:09] [Notice] Depositor processing for The Open Brazilian Dentistry Journal.
[2026-09-02 16:30:09] [Notice] Retrieving service document.
[2026-09-02 16:30:10] [Notice] The PKP PN is not currently accepting deposits.
So the service document request succeeds (HTTP 2xx) — the PN simply answers that it does not know the journal.
Querying the SD-IRI directly confirms it:
$ curl -s "https://pkp-pn.lib.sfu.ca/api/sword/2.0/sd-iri" \
-H "On-Behalf-Of: C918A3EE-BC91-423E-A1C4-F421B15CAB86" \
-H "Journal-URL: https://bahe.unifip.edu.br/index.php/bahe"
<pkp:pln_accepting is_accepting="No">The PKP PLN does not know about this journal yet.</pkp:pln_accepting>
One thing we found on our side, and a question about it
Our Cloudflare zone returns HTTP 403 (Cloudflare error 1010 — Browser Integrity Check) for two legacy user agents:
| User-Agent | Result on /gateway/plugin/PLNGatewayPlugin |
|---|---|
Java/1.8.0_292 |
403 |
libwww-perl/6.43 |
403 |
curl/8.4.0 |
200 |
python-requests/2.31.0 |
200 |
GuzzleHttp/7 |
200 |
Symfony HttpClient/Curl |
200 |
LOCKSS cache |
200 |
| empty user agent | 200 |
| Googlebot | 200 |
Requests sent straight to the origin, bypassing Cloudflare, return 200 for all of the above.
Our question: does the PN staging server ping the journal gateway with a Java- or LWP-based HTTP client? If so, this would explain everything — including why the journal registered on 4 June works and the ones registered on 20 June do not, if the Browser Integrity Check was switched on between those dates.
We are happy to allow the PN server regardless. If you can confirm the hostname/IP range the ping comes from (we have pkp-pn.lib.sfu.ca / 142.58.0.0/16 from an earlier forum thread), we will allow it explicitly.
However, if the ping uses Guzzle or another client from the table above, then it is not being blocked by us, and the journals would need to be registered on the PN side.
Related reports
This appears to be affecting several unrelated installations recently, across OJS 3.3, 3.4 and 3.5:
- PKP PN does not recognize our journal – OJS 3.3.0-22 / PKP PN 2.0.4-5
- PKP PN is not currently accepting deposits on OJS 3.5
- OJS 3.5 PKP PN plugin: journal not recognized by PKP PLN
- "The PKP PN is not currently accepting deposits" – Request to whitelist our journal
Request
Could you please check whether these five UUIDs are registered on the PN side, and let us know whether anything else is required from us? Preservation in the PKP PN is a requirement we need to meet for DOAJ and for our national indexing bodies (IBICT/Qualis).
Thank you very much for your work on the PN.