Following a recent support call with JET, we have been advised that "there is currently no known workaround which would allow the Jet Hub Scheduler to function with SSL 3.0 disabled.”

SSL 3.0 was identified as an unsecure protocol in 2014 and then officially deprecated in 2015. I have to say I am quite astonished to learn that the JET scheduler is still dependant on this protocol. As such, this is something which should be addressed urgently!