😁To open, I need to be honest and say the scripting force is not a strong with me! (mostly to do with the hooves I have attached to my arms when I type, so I'll take my 'professional hat' off and reply as a 'bod' with an interest in this.)
ePO 5.9 shipped with Python 2.6, you have 2.7, why do I mention this? Well in ePO 5.9 the cipher suit used was updated and the older ones dropped/removed/deprecated, ePO does not use old ciphers anymore.
How to update the cipher suite used by Apache and Tomcat in ePolicy Orchestrator to remove outdated ciphers
Technical Articles ID: KB89291
& Transport Layer Security and cipher suite requirements for ePolicy Orchestrator 5.10.x Technical Articles ID: KB91296
Which is where 2.6 and I believe 2.7 become important to note.
I had a search around and noted a post on a forum a post that put simply identified the ciphers as the source of the issue, an issue that v3 Python also has.
That post pointed to another forum which can be read in the below link:
It offers a workaround to overcome this cipher situation with the older versions of Python, a condition I am assuming is where the 'Failed to reach the server ...' response stems from in your screen shot.
Anyone please do add anything to this, as I say scripting is not 'my thing', sorry! (Hail hydra!) 😁
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.