Nominet module error

[ivaserver]

Not related to this thread.

 

The answer is listed in the wiki manual here:

http://wiki.whmcs.com/Nominet

 

Cheers

 

Si

 

Hi Si

Was this related to my post as I can't find a solution in the wiki

I have it setup as per the wiki

[ivaserver]

I am sorted, it was server firewall

[penguin]

We're intermittently still experiencing the 'Command syntax error' issue. We've traced this to the registrant name getting lost somewhere between the customer supplying this (as it's a required field) and the order being placed. For anyone that gets this, I'd recommend checking to see fi you're experiencing the same as us. When you view the domain details in WHMCS, if your registrant name field is blank, enter this, save the page and then re-submit the domain for registration. This seems to solve the issue, however we obviously need this to be corrected so that the details are correctly stored in the first place.

[roop]

Thanks Penguin - those steps just fixed my problem. I knew the module/config work as I could modify existing domains, just not register new ones!

 

Can I ask how/where you found the problem, as I was getting nowhere fast with the "Command syntax error" error message when trying to register a domain.

 

Thanks again, Rupert

[penguin]

We've been doing some investigation in conjunction with Nominet as to the issue as the EPP error messages aren't particularly informative They can manually check what caused the error, and this has been down to the registrant field being blank on submission, hence when you manually populate this field the registration then goes through.

[BionicInternet]

Command syntax error is normally caused by invalid details. For example, They didn't put the registrant right etc. A simple correct and save and then retry resolves this pretty quick.

 

An Error Occured

Error: Connecting to ssl://epp.nominet.org.uk on port 700.

The error message was 'Connection timed out' (code 110)

 

This error is caused by a firewall blocking port 700.

 

Our EPP modules works *perfect* - simple answer might be to check the data entry by the client.

[penguin]

Registrant is a required field in WHMCS, and this issue does not crop up with every registration - we only get them every now and again. Seeing as it is a required field though, a customer cannot proceed without entering this field, therefore this is not customer error, however it's then missing from the database after the registration fails

[Si]

This nominet module is really beginning to bug me. Intermittent errors all over the place and I'm at a loss as to why. It can't be user error. Sometimes registrations go through, sometimes they don't.

 

Yesterday, I had intermittent sucesses and failures with Nominet renewals and registrations and today, in my WHMCS, ALL of my customers domains show

 

An Error Occured

Error: Connecting to ssl://epp.nominet.org.uk on port 700.

The error message was 'Connection timed out' (code 111)

 

I've been guessing it's been user error in selecting company registration and not supplying company registration numbers (but surely WHMCS double checks that?) etc etc, up until now. At least with PGP we had confirmation emails. I ahve to go in and check the error logs and todo lists now and manually checking on renewal dates (even in the whois) to see that things are actually getting done with this module. No peace of mind here.

 

Any one else feeling the same way?

 

Si

 

P.S. I know the error above is a firewall issue and is easy sorted....it's just all of the other stuff that is getting to me that is really bugging me at the minute about this mod. I like the nominet mod and the way customers can update contact info etc (don't get me wrong matt), I don't want to go back to PGP, (not really), I just want to see the nom mod working with some stability.

Edited December 9, 2008 by Si

[Matt]

I've only ever seen 3 reasons for failure - 1 invalid address details, 2 whois opt-out selected for a reg type that doesn't allow it and 3 no company ID supplied for a company reg type.

 

In 3.8, there is an update to prevent #2 ever occuring by overiding that selection to off for any reg type that does not allow it, regardless of the user selection. For #1 you get that from time to time with all registrars, and there's not really anything we can do about it. And for 3, it's not currently possible for custom domain fields to have conditional requirements - ie. if this custom field equals this, then this custom field is required - which is what would be needed for requiring a company ID only for selected reg types. But again, that's something that affects all .uk registrations and isn't module specific.

 

I'm not aware of any actual problem causing issues within the module but I agree with many I've spoken with that Nominet's error responses could be a lot more helpful in letting you know exactly why a registration failed.

 

Matt

[othellotech]

today, in my WHMCS, ALL of my customers domains show

An Error Occured

Error: Connecting to ssl://epp.nominet.org.uk on port 700.

The error message was 'Connection timed out' (code 111)

 

P.S. I know the error above is a firewall issue and is easy sorted

 

So doesn't the question become ... what did *you* change that caused *you* to break your billing system, and what are *you* doing to prevent it

[Si]

So doesn't the question become ... what did *you* change that caused *you* to break your billing system, and what are *you* doing to prevent it

 

eh, well, duh no actually, the issue was at Nominet's end (not mine) so I didn't do anything to break the billing system and there's nothing I can do to prevent Nominet doing it again other than chase them up IF it happens again.

 

I think the issue was temporarily with the server I was connecting to use their API.

 

epp.nominet.org.uk. 300 IN A 213.248.201.170

 

Perhaps they restarted the firewall or something blocking incoming connections? Or they restarted some other kind of service? Either way, it's fixed now.

 

On a side note:

 

Thanks for addressing the other issues Matt and letting me know that 3.8 is looking at a fix for at least one of them.

 

Si

Edited December 10, 2008 by Si

[ivaserver]

I am now getting Command syntax error on all UK domains.

 

Has been working fine until now.

 

customers can not update namesevers and no name servers show in WHMCS

 

Has anyone found a fix for this?

[pjs32]

Yep - all uk domains are now showing Registrar Error

Command syntax error - even though they have been working fine for the last few months.

 

Must be a problem with Nominet?

[DigitalEnigma]

Hi,

 

Were getting the same Command syntax error now even though all was fine until Nominet made some updates today from looking at their announcements.

 

I have emailed Nominet and waiting on a reply, shame the error message isn't a little more helpful.

[ivaserver]

My problem is resloved now

 

Nominet must have fixed whatever was the problem

[DigitalEnigma]

Hi,

 

I got a reply from Nominet saying there was a problem with the EPP system and they were looking into it. All seems to be back now.

[CSNM-Carl]

Is anyone else getting Command syntax error this morning for new registrations? What is the best way to troubleshoot these errors - does WHMCS have a more detailed log?

 

I was under the impression validation had been put into 3.8.1 to stop the WHOIS opt-out tick box being chosen for domains that have a entity type other than individual?