My journal’s register page is not working. when i try to register new user, i am getting below error :
PHP Fatal error: Uncaught GuzzleHttp\Exception\ConnectException: cURL error 28: Operation timed out after 150001 milliseconds with 0 out of 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) in /storage/www/ejournals/ojscrae/lib/pkp/lib/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:200\nStack trace:\n#0 /storage/www/ejournals/ojscrae/lib/pkp/lib/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php(155): GuzzleHttp\Handler\CurlFactory::createRejection(Object(GuzzleHttp\Handler\EasyHandle), Array)\n#1 /storage/www/ejournals/ojscrae/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))\n#2 /storage/www/ejournals/ojscrae/lib/pkp/lib/vendor/guzzlehttp/guzzle/src/Handler/CurlHandler.php(43): GuzzleHttp\Handler\CurlFactory::finish(Object(GuzzleHttp\Handler\CurlHandler), Object(GuzzleHttp\Handler\EasyHandle), Object(GuzzleHttp\Hand in /storage/www/ejournals/ojscrae/lib/pkp/lib/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php on line 200, referer: journalurl/user/register
Steps I took leading up to the issue
Register page of the journal
when I filled all the fields, went through recaptcha, and then registered.
recaptcha verification failed. and logs from the server show the above.
I tried pinging pkp.sfu.ca which shows good
ping pkp.sfu.ca
PING pkp.sfu.ca (208.70.244.23) 56(84) bytes of data.
I checked with the firewall team and they say they don’t filter outbound connection
is there an issue after the recent Orcid Plugin update? i just updated the Orcid plugin in the morning and users started complaining that the register page doesn’t go ahead and we are getting error that I have shared. Thank you
Hmm… There is an issue with ORCID plugin – the users are always led to the ORCID sandbox page, "ORCID authorization link has already been used or is invalid" issue · Issue #281 · pkp/orcidProfile · GitHub. But this should not have anything to do with that error and user registration.
We have also added a new option (‘allow_redirects’ => [‘strict’ => true]) to Guzzle request in ORCID plugin that should allow URL redirects, but I do not know why this would be connected with user registration – it is only relevant for ORCID requests
Thus, would it be possible for you to return back to your old ORCID plugin version and check if the error appears?
EDIT: It could be also something with reCAPTHA.
But going back to the previous ORCID plugin is also good idea, till we solve that issue above i.e. till the next release…
@bozana, what is best practise to downgrade plugin. Morevoer, some of our users were having problem with orcid plugin that’s why we had to upgrade it. So downgrading won’t help.
thanks for your quick reply. @bozana it’s v1.1.3.10 that was released on 17th October.
It says : Change the public API URL and add redirection ? anything changed with redirection that we need to set in firewall?
i’ll ask my teammate to disable recaptcha but i am not sure if its recaptcha because when i fill in the fields then go through recaptcha and register. the page takes time (which gives a time to recaptcha to expire) and then page sometimes throw 500
Hmm… I am not sure what you would need to set in firewall, but:
The ORCID public API URLs https://pub.orcid.org/ and https://pub.sandbox.orcid.org/, that were used till now, will now be redirected to https://orcid.org/ and https://sandbox.orcid.org/ by ORCID.
That new plugin v1.1.3.10 should actually already use the new API URLs https://orcid.org/ and https://sandbox.orcid.org/.
But, because we missed to change the API URL in the database table plugin_settings with that new plugin release, the plugin is always leading the users to https://sandbox.orcid.org/.
Could it maybe be that https://sandbox.orcid.org/ is not allowed in firewall?
If possible, maybe you can change the API URL of the ORCID plugin manually in the DB table plugin_settings, where setting_name = 'orcidProfileAPIPath' – I suppose the setting_value there is https://pub.orcid.org/ and you can change it to https://orcid.org/?
EDIT: However I am a little bit confused why ORCID plugin should be the problem, because at the new plugin release the ORCID button seems to be missing at the registration form, thus it seems ORCID plugin should not be used there…
hi @bozana , you are right it looks like recaptcha issue and works after i disabled recaptcha. any advice what we can do for that. it will be difficult without recaptcha
Hi @bozana - setting the API URL to https://orcid.org/ in the database table seems not to help (may also be caching issue) - the orcidProfile plugin v1.1.3.10 always relays to the ORCID sandbox.
I am sorry that I cannot help further but maybe your system admins would know something – maybe it is something with internet connectivity, proxy or firewall…
Do you use proxy?
hi @bozana this issue was solved by disabling recpactcha. then I enabled it again as problem went away for registration page. After this orcid update, we updated orcid again.
now when authors try to connect their orcid id or authorize orcid id for article , they get the same issue : PHP Fatal error: Uncaught GuzzleHttp
Exception
ConnectException: cURL error 28: Operation timed out after 150000 milliseconds with 0 out of 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
Both the ReCAPTCHA issue and the ORCiD issue on your other thread have the same cause: something like a firewall or a proxy on your server is preventing the Guzzle library that OJS uses from connecting to an outside service.
We have no way of knowing what your server’s config is, and the issue is outside of OJS, so it’s hard to help further here.
If you want to isolate the problem, you could try creating a simple Guzzle script outside of OJS and testing that. I found some instructions you could follow here. If you can replicate the problem with a test script like this, it’s likelier that you can show this to your server admin and get the help you’re looking for.
Regards,
Alec Smecher
Public Knowledge Project Team
I understand your point. However, why did the problem arise only after we upgraded the ORCID plugin? Last time, we also had issues only after updating the ORCID plugin. There must be something in the update causing the issue. Before updating to the current version, the ORCID plugin was working fine. The server configuration didn’t change during this time; only the ORCID plugin was updated.
but maybe your system admins would know something – maybe it is something with internet connectivity, proxy or firewall…