PKP PLN plugin enabled — journal not recognized or archived

Software Support
1

I have enabled the PKP PLN (Private LOCKSS Network) plugin in my OJS installation, but my journal does not appear to be recognized or archived in the PKP PLN network. The plugin is active, and I have entered all required journal information (URL, ISSN, contact email), but archiving has not progressed.

In the PKP PLN plugin status, no items are being deposited or processed. The journal does not show any archiving activity in the PKP PLN network.

I expected that after enabling the plugin and configuring the settings, the archiving process would begin and show progress/status updates.

Steps I took leading up to the issue

  1. Installed and enabled the PKP PLN plugin in OJS.
  2. Verified and entered all required journal information (URL, ISSN, contact email).
  3. Confirmed plugin settings were saved correctly.
  4. Waited several weeks — no progress or change in archiving status shown.
  5. Verified journal configuration and compared with PKP PLN documentation.
  6. Verified that the OJS instance is working properly and regularly updated.
  7. Searched PKP forum and PKP documentation for similar issues but found no clear solution.

What application are you using?
OJS 3.3

Additional information

  • Journal URL: https://journals.uol.edu.pk/jucmd
  • I am the founder and managing editor of this journal.
  • We would like the journal to be properly archived in PKP PLN but have not been able to get the plugin to start archiving.
  • No errors appear in the plugin, but also no deposits or archiving progress is seen.
  • No error messages in the error log (checked system logs).

I would be very grateful if you could advise what additional steps we may need to take, or if there are known issues with PKP PLN integration in this version of OJS.

Thank you very much for your assistance.

3

Hi!

Your journal cannot be contacted because the process is automated and you’re using the the Cloudflare Firewall. It’s needed to setup Cloudflare to accept requests coming from pkp-pn.lib.sfu.ca.

Once you do it, I can re-check.

Best,
Jonas Raoni

4

Hello Jonas,

Thank you for identifying this issue. Yes, our university network operates behind a firewall, and we had to exempt OJS in order to ensure smooth operation of our university journals. I will make sure to also exempt pkp-pn.lib.sfu.ca from the firewall before getting back to you. I truly appreciate your help in pinpointing the root cause—especially since I had tried every other solution without success.
Regards,
Mariyah

5

Hello Jonas,

Hello Jonas,
We have disabled Cloudflare and verified seamless connectivity between PKP and our institutional system. The restriction has now been lifted from our end. Kindly check from your side and assist us further.

6

Hi!

It’s still not working for me, this is the response I get from your server:

$ wget -S https://journals.uol.edu.pk
--2025-07-02 05:48:44--  https://journals.uol.edu.pk/
Resolving journals.uol.edu.pk (journals.uol.edu.pk)... 104.22.78.237, 104.22.79.237, 172.67.25.153, ...
Connecting to journals.uol.edu.pk (journals.uol.edu.pk)|104.22.78.237|:443... connected.
HTTP request sent, awaiting response...
  HTTP/1.1 403 Forbidden
  Date: Wed, 02 Jul 2025 12:47:10 GMT
  Content-Type: text/html; charset=UTF-8
  Transfer-Encoding: chunked
  Connection: close
  accept-ch: Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model, UA-Platform-Version, UA-Platform, UA
  cf-mitigated: challenge
  critical-ch: Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model, UA-Platform-Version, UA-Platform, UA
  cross-origin-embedder-policy: require-corp
  cross-origin-opener-policy: same-origin
  cross-origin-resource-policy: same-origin
  origin-agent-cluster: ?1
  permissions-policy: accelerometer=(),autoplay=(),browsing-topics=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=()
  referrer-policy: same-origin
  server-timing: chlray;desc="958e400aaa477104"
  x-content-type-options: nosniff
  x-frame-options: SAMEORIGIN
  Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  Expires: Thu, 01 Jan 1970 00:00:01 GMT
  Strict-Transport-Security: max-age=2592000; includeSubDomains; preload
  Server: cloudflare
  CF-RAY: 958e400aaa477104-YVR
  alt-svc: h3=":443"; ma=86400
2025-07-02 05:48:44 ERROR 403: Forbidden.

Best,
Jonas Raoni