Hi, we currently aren’t able to open the site admin page in any of our instances. The all were upgraded to ojs 3.5.0.3
There’s warnings:
[20-Feb-2026 08:55:51] WARNING: [pool www] child 20 said into stderr: "[20-Feb-2026 08:55:51 Europe/Vienna] Failed t │
│ o retrieve the latest version info: cURL error 28: Failed to connect to pkp.sfu.ca port 443 after 130967 ms: Could not connect to server (see https │
│ ://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://pkp.sfu.ca/ojs/xml/ojs-version.xml"
now the file is accessible again and I get back to the admin pages. Though I’d really like to remove the dependency on this request. Is there an option?
Currently not – the “current version” XML is fetched from https://pkp.sfu.ca/ojs/xml/ojs-version.xml even if both of those options are disabled; with the enable_beacon turned off, no information about the server is sent upstream in the process, and without show_upgrade_warning, nothing is presented to the UI if it’s not the latest.
The interaction is kicked off in lib/pkp/pages/admin/AdminHandler.php around line 131:
// Interact with the beacon (if enabled) and determine if a new version exists
$latestVersion = VersionCheck::checkIfNewVersionExists();
The descriptor is cached for up to a year (!).
Note that trying to stop OJS from fetching outside content will most notably cause the Plugin Gallery to stop working; it needs to get the list of plugins periodically (if I remember right, it’s cached for a day).
Regards,
Alec Smecher
Public Knowledge Project Team
Yep, I had the same issue. I can make a pull request so it doesn’t check any more when both enable_beacon and show_upgrade_warning are off, seems like a proper fix. I can create a pull request if you think it is appropriate.