ebmocwen Posted August 22, 2016 Share Posted August 22, 2016 We haven't quite get around to upgrading to WHMCS 6.x yet so we are currently still running 5.3.x. After reading this WHMCS blog entry posted 20th August regarding the Nominet module: http://blog.whmcs.com/?t=117270 This module will only be available for WHMCS 6.x but surprisingly, our WHMCS 5.x module works with Nominet EPP without any problems, so I was wondering if anyone knew why this was? Are we the last people running WHMCS 5.x? Has anyone else experienced the same issue? The reason I ask is, we plan to upgrade to WHMCS 6 to resolve this problem (which currently isn;t a problem for us) so I was wondering if we introduce the problem by upgrading? Thank you in advance for any assistance/advice you can offer! 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Technical Analyst WHMCS Edward Posted August 22, 2016 WHMCS Technical Analyst Share Posted August 22, 2016 This is interesting. Nominet announced last week that they were strengthening the TLS requirements for EPP connections to their service to require TLS 1.1 or higher. That should mean that any existing installations attempting to connect to the Nominet API would fail to connect without an update to the module. If you could open a ticket referencing this post, our team would be very interested to take a closer look at this. I will also add that Version 5 has reached end of life at this time and so you should strongly consider upgrading when you can. More information on our end of life policy can be found at http://docs.whmcs.com/EOL -Eddy 0 Quote Link to comment Share on other sites More sharing options...
ebmocwen Posted August 22, 2016 Author Share Posted August 22, 2016 Dear Eddy, Thank you for your reply. I am running WHMCS 5.3.14 and expected the EPP to stop working, but it's fine. I called Nominet today and they said they don't know why it is working as it's should have stopped. I wondered if there was a "change over" period where both TSL 1 and 1.1 would work together. They denied this was the case. I'm running WHMCS 5.3x, PHP 5.4 and Centos 6. I asked this question here because I was worried that if I upgrade to WHMCS 6, I need to then upgrade my PHP to 5.6 and i'm not sure if I can test all of this in time should the upgrade break my current live setup. Thanks. 0 Quote Link to comment Share on other sites More sharing options...
pjs32 Posted August 23, 2016 Share Posted August 23, 2016 We have installed the new Nominet module but are now getting Registrar Error Connecting to tls://epp.nominet.org.uk:700. The error message was '' (code 0) is it working for everyone else? 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Nate Posted August 23, 2016 Share Posted August 23, 2016 Hello PJS22, What version of openssl is your php compiled against? You can see this in your phpinfo setting, for example my devbox shows: "SSL Version OpenSSL/1.0.1t". Thanks, Nate 0 Quote Link to comment Share on other sites More sharing options...
pjs32 Posted August 23, 2016 Share Posted August 23, 2016 It is showing OpenSSL/1.0.1p 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Nate Posted August 23, 2016 Share Posted August 23, 2016 Interesting, @pjs32 please open a ticket so we can investigate this further. We are going to need ssh access to your installation and sharing those details is best done over the secure channels of a support ticket. 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted August 25, 2016 Share Posted August 25, 2016 it is interesting - i've just renewed a .co.uk through the old Nominet module on v5.3.14 and it worked without a hitch... like pjs32, I thought it would fail. 0 Quote Link to comment Share on other sites More sharing options...
ebmocwen Posted August 25, 2016 Author Share Posted August 25, 2016 it is interesting - i've just renewed a .co.uk through the old Nominet module on v5.3.14 and it worked without a hitch... like pjs32, I thought it would fail. My nominet module on 5.3.14 never stopped working. I suspect it will stop working after the upgrade to WHMCS 6. 0 Quote Link to comment Share on other sites More sharing options...
slim Posted August 26, 2016 Share Posted August 26, 2016 Why would a code update be required for this? It would be controlled by the hosting server wouldnt it? 0 Quote Link to comment Share on other sites More sharing options...
ebmocwen Posted August 26, 2016 Author Share Posted August 26, 2016 Why would a code update be required for this? It would be controlled by the hosting server wouldnt it? I'm not sure why the update is required either. The hosting server support TLSv1.1, i'm not sure why the Nominet module comes into it. Did anyone report their module actually stopped working? Or is this a problem that simply didn't happen? 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Support Manager WHMCS John Posted September 6, 2016 WHMCS Support Manager Share Posted September 6, 2016 Hi, We received one report of this being a problem look at our development tracker for this issue, and even in our communications with Nominet their technical teams seemed unsure as to why more users weren't experiencing a connection error. As a socket-based connection is used to connect to the Nominet module, a code update to the module is required in order to create a context stream with TLSv1.1 However it's always nice to be future-proof 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.