keithm Posted November 27, 2011 Share Posted November 27, 2011 Hello, Since upgrading to v5, the Nominet domain sync now fails to login with the following error: Login Error: Command syntax error I've double checked the password (although it had not changed) and this is correct. I've also checked the IP address for EPP (this is unchanged as well) Other sync's work with other registrars. Keith 0 Quote Link to comment Share on other sites More sharing options...
Si Posted November 28, 2011 Share Posted November 28, 2011 Got exactly the same problem here 0 Quote Link to comment Share on other sites More sharing options...
shotgun Posted December 4, 2011 Share Posted December 4, 2011 Same here too 0 Quote Link to comment Share on other sites More sharing options...
kenwardc Posted February 15, 2012 Share Posted February 15, 2012 What was the fix for this one? 0 Quote Link to comment Share on other sites More sharing options...
Moc Posted February 16, 2012 Share Posted February 16, 2012 http://forum.whmcs.com/showthread.php?t=14017 0 Quote Link to comment Share on other sites More sharing options...
kenwardc Posted February 16, 2012 Share Posted February 16, 2012 Moc that wasn't helpful in the slightest. I have search as deeply as I could for the answer and STILL have not found it. If you know the answer, wouldn't it have been better to point me in the right direction rather than at a post saying "Don't ask until you've looked" ?? 0 Quote Link to comment Share on other sites More sharing options...
Moc Posted February 23, 2012 Share Posted February 23, 2012 The topic title of this bug report states it has been fixed. The post I linked in my previous reply states: Bug fixes are not often released immediately - they are collated and then released in the next point release or main build. However, if a bug that is showing as fixed is affecting you, you can open a ticket to enquire if a fix is available for the current version. You can simply open up a ticket and find out if they have the updated files available for you. If not, there is no other option but to wait for the next release. 0 Quote Link to comment Share on other sites More sharing options...
smurf Posted March 30, 2012 Share Posted March 30, 2012 Did anyone get this fixed? 0 Quote Link to comment Share on other sites More sharing options...
Moc Posted April 1, 2012 Share Posted April 1, 2012 Did you open a support ticket to get the fixed files? 0 Quote Link to comment Share on other sites More sharing options...
smurf Posted April 3, 2012 Share Posted April 3, 2012 We've opened a ticket and submitted debug info. We think we've seen the issue in their code and highlighted it to them. Will update this post. 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.