Server Information:
RHEL 7 fully patched
CF 2018 lastest update
Apache Httpd
This problem started this weekend when I enabled SSL for the CF admin and HSTS for httpd. All of the scheduled tasks that I have running that are hitting https:// are failing. These are the logs that I’m seeing:
“Information”,”DefaultQuartzScheduler_Worker-1″,”03/01/21″,”08:56:54″,””,”Task default.<scheduled task> triggered.”
“Error”,”DefaultQuartzScheduler_Worker-1″,”03/01/21″,”08:56:55″,””,”Connection Failure: Status code unavailable ”
Note: <scheduled task> is a redaction for security reasons.
If I reach that website using a broswer, it runs the task fine.
If I drop the link down to http:// and let the redirection transform it back to https:// it works fine.
Has anyone else had this issue and do we have any remedies? My Google-fu has not been strong this morning.
Newbie
1 posts
When you say “If I drop the link down to http:// and let the redirection transform it back to https:// it works fine.”, are you referring to what you do in your browser or in the task’s url? Many may assume you do mean the latter, which then would indeed be odd (because then that means somehow the request WOULD be working via https in the task).
If you are indeed confirming that you can’t run the tasks with an https url at all, then you’re in a situation that many have found themselves in, whether with cf scheduled tasks, or with cfhttp calls out to such https urls, or even connecting cf to mail or other services via ssl/tls.
And for such problems, the solution nearly always is far simpler than people realize: you may simply need to update the jvm that cf is relying on.
I have a blog post explaining things:
https://coldfusion.adobe.com/2019/06/error-calling-cf-via-https-solved-updating-jvm/
It applies to ALL versions of CF. Even people running cf2021 have had the problem, since even that new release came with an old jvm at its release (11.0.1, rather than the latest 11.0.10). I point to resources for choosing the right jvm for your cf version, and for implementing that change.
Let us know if this helps, or not, which would point us elsewhere.
Andrew, any update?
Just sounds like you need to install the certificate or CA of of the certificate into the JRE keystore
You must be logged in to post a comment.
23 Nov
10AM Pacific
Online
