Errorr server 500 due to server cannot to pkp.sfu.ca

Software Support
1

Describe the issue or problem
When I try to login to my admin dashboard, I get the server error 500. when I turned the error display on, I got the following message:

Fatal error : Uncaught GuzzleHttp\Exception\ConnectException: cURL error 28: Failed to connect to pkp.sfu.ca port 80 after 127253 ms: Couldn’t connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) in /home/uotly/public_html/journals/lib/pkp/lib/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:200 Stack trace: #0 /home/uotly/public_html/journals/lib/pkp/lib/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php(155): GuzzleHttp\Handler\CurlFactory::createRejection(Object(GuzzleHttp\Handler\EasyHandle), Array) #1 /home/uotly/public_html/journals/lib/pkp/lib/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php(105): GuzzleHttp\Handler\CurlFactory::finishError(Object(GuzzleHttp\Handler\CurlHandler), Object(GuzzleHttp\Handler\EasyHandle), Object(GuzzleHttp\Handler\CurlFactory)) #2 /home/uotly/public_html/journals/lib/pkp/lib/vendor/guzzlehttp/guzzle/src/Handler/CurlHandler.php(43): GuzzleHttp\Handler\CurlFactory::finish(Object(GuzzleHttp\Handler\CurlHandler), Object(GuzzleHttp\Handler\EasyHandle), Object( in /home/uotly/public_html/journals/lib/pkp/lib/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php on line 200

I tried
PING pkp.sfu.ca (208.70.244.23) 56(84) bytes of data.

from different servers
but there is no response
23 packets transmitted, 0 packets received, 100.0% packet loss

The firewall is not blocking the connection,

I would highly appreciate your assistance.

What application are you using?
I am using, OJS 3.3.0-8

Regards

2

Hi @nwesri

It is fine that you cannot ping our server, as we filter out ICMP packets. What is probably happening is that your server itself has an outdated SSL package containing an old root certificate authority record. Please talk to your systems admin and/or update your system SSL packages.

Best
Jason

3

Port 80 as indicated in the error log isn’t SSL (HTTPS), but simply HTTP.
It rather looks like the provider has locked outgoing HTTP requests in the firewall.

4

Thank you for your reply.

The admin site returned to work normally.

Regards