Failed - Try again in 60 mins (after about 20 hours)
JohnAJ opened this issue Β· 21 comments
Hi,
I was getting the "failed to enable crypto" error, and now I get: -
Message: Script failed, likely cause is the recent addition of the IP address to the Nominet test bed due to the large amount of people currently setting up. Please try running the script in 60 minutes time again.
However I set up the IPs in my Nominet account yesterday evening, so around 20 hours ago - could this still be the issue?
What setup are you running it on? I created a new server, added the code to it, added my IP to Nominet and waited an hour and it started working, my guess was that it was the issue. I'd recommend a centOS droplet from Digital Ocean.
It's also worth double checking the IPs are correct
It's on a reseller account on Clook.net. IPs are correct, but Clook have a lot of firewall rules - they say they allowed it, which stopped an earlier error, but I think there still might be an issue somewhere...
I've got a local dev machine running centOS so tried from that instead, with success (I already put my own IP in my Nominet account, just in case!) :)
That's great news, I'd recommended not using shared hosting for this, will dampen our already small chances! Please remember to contact Nominet to confirm you have met the requirements.
I still get the same issue "Script failed, likely cause is the recent addition of the IP address to the Nominet test bed due to the large amount of people currently setting up. Please try running the script in 60 minutes time again." using ubuntu DigitalOcean server and I already put my own IP in my Nominet account yesterday, I have just created a new centos server and added it's new IP to Nominet will wait 1 hour to test again.
I'm 100% sure the problem is with the IP being processed at Nominet and nothing else, I've helped five people today who have connect correctly. Please make sure the config is correct, double check your EPP testbed password.
Hi, firstly thanks for making this publicly available it looks great! I've tried setting this up however I'm still receiving the error 'Message: Script failed, likely cause is the recent addition of the IP address to the Nominet test bed due to the large amount of people currently setting up. Please try running the script in 60 minutes time again. ' I've used openssl and the connection and login allows me in via this route however not when I use this? Any ideas? Any help is greatly appreciated! :)
I'd recommend using a digital ocean droplet, and making 100 percent sure it's that IP you have in the test bed and your credentials are right, it took a good hour for it to start working in the week due to nominet, i presume the same is at the weekend, however it may take longer for them to approve them as its busier, this has been tested and ran successfully by many people and it seems to be the approval from nominet, have you connected to the test bed correctly via ssl from the same server?
@0219dives Have you resolved this, I've ran another two tests succesfully to make sure.
Hi, Sadly havenβt had chance to move it to digital ocean yet, tested using ssl on the same server using an OpenSSL connection and that worked however not using this webpage strangely. Will try and test tomorrow see if I have any luck. Just a quick question does the webpage hosting the page have to use ssl too? Thanks Dan
Hi Aaron, I'm not getting that issue here. The message I am receiving is as below:
Error logging into EPP, please check your config and Nominet settings.
I've added my server IP to testbed and DAC, I've also opened port 700 for incoming and outgoing connections with my firewall, running from a LON1 DigitalOcean droplet as that's what I use anyway. Any clues? I've opened a ticket with Nominet to see if they can run through the connection logs to see if I'm actually connecting.
Hi Aaron, I'm not getting that issue here. The message I am receiving is as below:
Error logging into EPP, please check your config and Nominet settings.
I've added my server IP to testbed and DAC, I've also opened port 700 for incoming and outgoing connections with my firewall, running from a LON1 DigitalOcean droplet as that's what I use anyway. Any clues? I've opened a ticket with Nominet to see if they can run through the connection logs to see if I'm actually connecting.
Have you checked the log file ?
What's its saying in the logs...
Hi Aaron, I'm not getting that issue here. The message I am receiving is as below:
Error logging into EPP, please check your config and Nominet settings.
I've added my server IP to testbed and DAC, I've also opened port 700 for incoming and outgoing connections with my firewall, running from a LON1 DigitalOcean droplet as that's what I use anyway. Any clues? I've opened a ticket with Nominet to see if they can run through the connection logs to see if I'm actually connecting.Have you checked the log file ?
What's its saying in the logs...
Hi,
Yes the logs are giving me an Auth error, however I've double and triple checked my testbed passwords etc. and I've most definitely added the right IP address to both DAC and EPP. Really confused
Hi Aaron, I'm not getting that issue here. The message I am receiving is as below:
Error logging into EPP, please check your config and Nominet settings.
I've added my server IP to testbed and DAC, I've also opened port 700 for incoming and outgoing connections with my firewall, running from a LON1 DigitalOcean droplet as that's what I use anyway. Any clues? I've opened a ticket with Nominet to see if they can run through the connection logs to see if I'm actually connecting.Have you checked the log file ?
What's its saying in the logs...Hi,
Yes the logs are giving me an Auth error, however I've double and triple checked my testbed passwords etc. and I've most definitely added the right IP address to both DAC and EPP. Really confused
What server are you testing this on ?
how long ago did you add the ip ?
When did you add the IP?
β¦
On Thu, 20 Jun 2019, 18:04 Ben Ravetta, @.***> wrote: Hi Aaron, I'm not getting that issue here. The message I am receiving is as below: Error logging into EPP, please check your config and Nominet settings. I've added my server IP to testbed and DAC, I've also opened port 700 for incoming and outgoing connections with my firewall, running from a LON1 DigitalOcean droplet as that's what I use anyway. Any clues? I've opened a ticket with Nominet to see if they can run through the connection logs to see if I'm actually connecting. Have you checked the log file ? What's its saying in the logs... Hi, Yes the logs are giving me an Auth error, however I've double and triple checked my testbed passwords etc. and I've most definitely added the right IP address to both DAC and EPP. Really confused β You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5?email_source=notifications&email_token=AAGRD7OGW3YN55CELRMWHJ3P3O2BBA5CNFSM4HYHXEA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGAVIQ#issuecomment-504105634>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGRD7JTPASPSXUD3D2W7U3P3O2BBANCNFSM4HYHXEAQ .
Ooh, I added the IP roughly 4 days ago as I'm using EPP for WHMCS to register domains for my clients etc. come to think of it though, that was having problems also. I'll know more when Nominet get back to me. They asked for further information and have already told me my IP is whitelisted, so I'm not sure what exactly is going on.
Make sure your tag and password are correct for the epp testbed, again changes to that can take time to update
β¦
On Thu, 20 Jun 2019, 18:10 Ben Ravetta, @.> wrote: When did you add the IP? β¦ <#m_1999632500552120738_> On Thu, 20 Jun 2019, 18:04 Ben Ravetta, @.> wrote: Hi Aaron, I'm not getting that issue here. The message I am receiving is as below: Error logging into EPP, please check your config and Nominet settings. I've added my server IP to testbed and DAC, I've also opened port 700 for incoming and outgoing connections with my firewall, running from a LON1 DigitalOcean droplet as that's what I use anyway. Any clues? I've opened a ticket with Nominet to see if they can run through the connection logs to see if I'm actually connecting. Have you checked the log file ? What's its saying in the logs... Hi, Yes the logs are giving me an Auth error, however I've double and triple checked my testbed passwords etc. and I've most definitely added the right IP address to both DAC and EPP. Really confused β You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 <#5>?email_source=notifications&email_token=AAGRD7OGW3YN55CELRMWHJ3P3O2BBA5CNFSM4HYHXEA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGAVIQ#issuecomment-504105634>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGRD7JTPASPSXUD3D2W7U3P3O2BBANCNFSM4HYHXEAQ . Ooh, I added the IP roughly 4 days ago as I'm using EPP for WHMCS to register domains for my clients etc. come to think of it though, that was having problems also. I'll know more when Nominet get back to me. They asked for further information and have already told me my IP is whitelisted, so I'm not sure what exactly is going on. β You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5?email_source=notifications&email_token=AAGRD7KQKJNMMZIKAKDPJFTP3O2ZRA5CNFSM4HYHXEA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGBF2I#issuecomment-504107753>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGRD7M4KF6YMQHGYAALQXTP3O2ZRANCNFSM4HYHXEAQ .
Thanks Aaron, I have triple checked the data and things are ok. I've SSH'd into my server and tried to ping Nominet's servers and it isn't responding. So I'm wondering why.
Come to think of it, I think Nominet block traceroute/ping to their boxes, I really can't think what else it could be. I'll try again in a few hours and update you. By the way Aaron, I owe you a coffee.
Hello Aaron,
Just an update. Not sure what was causing the auth error, but it's fixed. Managed to create the test domain just fine.
Great news, I believe it's Nominets end, closing thread now.