▎ Since about 22 October, pkp-pn.lib.sfu.ca (142.58.232.187, also pkp-pln.lib.sfu.ca / lib-pkppln.dc.sfu.ca) refuses connections on port 443 (“No route to host”) from our host (Hostinger) and from an unrelated network in Pakistan. pkp.sfu.ca works fine from both.
Our daily Depositor task logs: “There was an error connecting to the PKP PN”. Our 15 deposits were accepted on 21 Oct but remain in staging state depositedByJournal, and we see no harvest requests from PkpPlnBot.
The PKP PN was impacted by the PHP security issue last week:
The PKP PN is back to functioning again, but I suspect that it may be delayed in processing automated requests being made by journals. @jonasraoni may be able to speak further to this.
From our side the PN still isn’t reachable: https://pkp-pn.lib.sfu.ca (142.58.232.187) gives “No route to host” on port 443 from our host (Hostinger, server IP 145.79.14.40). It also times out from an unrelated network in Pakistan, as of today (26 Oct). Our daily Depositor still logs “There was an error connecting to the PKP PN”. Is the PN currently limited to certain networks, or do journal IPs need to be allow-listed?
Same situation on our side (OJS 3.5.0.5, PKP PN 4.0.1.0, journal UUID F5B0E716-634B-4AE6-8C30-61E21632942E, https://arteducation.pro/artedu).
The “Update” terms button in the plugin settings hangs for several minutes. One difference: we have no Depositor log at all in files/scheduledTaskLogs (other tasks such as ProcessQueueJobs and DepositDois do log, cron runs scheduler.php and jobs.php every minute). Issues published in 2025–2026 have never been added to the deposit list; the last deposits are from 2025-03-18, before our upgrade to 3.5.
Is there a way to trigger the Depositor task manually to check it?