raatt Posted June 9, 2014 Share Posted June 9, 2014 After upgrading to 5.3.7, the e-mails titled "WHMCS Enom Domain Synchronization Report" only have the following body, instead of having a domain/date listing: Enom Domain Sync Report --------------------------------------------------- 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Ryan Posted June 9, 2014 Share Posted June 9, 2014 How often are you running the sync script? It is recommended that you only run the script every four hours or you may overload eNom's servers which could result in eNom blocking your access. --Thanks 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Chance Posted June 10, 2014 Share Posted June 10, 2014 Hey raatt, Are you still using the enomsync.php file in your cron or are you using the domainsync.php file. We have moved away from using the individual registrar sync files and have moved to a singular domain sync file: http://docs.whmcs.com/Domains_Tab#Domain_Sync_Enabled The new domainsync.php should be setup in your cron and run about every 4 hours as Ryan mentioned. The script does 50 domains at a time and caches the next 50 to do on the next run so that it does not overload the system or the registrar. Should you need any further assistance with this, please open a ticket to support so we can look further into it. Thanks 0 Quote Link to comment Share on other sites More sharing options...
bear Posted June 10, 2014 Share Posted June 10, 2014 The script does 50 domains at a time and caches the next 50 to do on the next run so that it does not overload the system or the registrar. Mine shows a smallish amount (average 14/50) get synced (Namecheap), then the rest all say "Sync Not Supported by Registrar Module". Pretty sure they all eventually get done, but is that the expected response there? 0 Quote Link to comment Share on other sites More sharing options...
raatt Posted June 10, 2014 Author Share Posted June 10, 2014 Hey raatt, Are you still using the enomsync.php file in your cron or are you using the domainsync.php file. We have moved away from using the individual registrar sync files and have moved to a singular domain sync file: <snip> Thanks Well, derp! I was still using enomsync. I've set up domainsync and will keep an eye on it. Thank you both for the information. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Chance Posted June 10, 2014 Share Posted June 10, 2014 Hey, @bear So the domain sync not supported error shows up on my personal WHMCS against NameCheap as well. I am not sure as the exact reasoning but I think it has something to do with NC's servers. I only run the cron every 12 hours as I don't have a lot of domains to sync and it only appears to be an issue with funny TLD's like .mobi, .pw etc as the domain sync also uses the whois server to pull the data needed and if the whois server isnt responding you will get that response. Ive noticed on the next domain sync run, it then shows up just fine. @raatt, if you still have issues with it, open a ticket to support so we can get some logins and such to have a further look at it. Thanks guys! 0 Quote Link to comment Share on other sites More sharing options...
Troy Posted June 10, 2014 Share Posted June 10, 2014 Bear/Chance: I think you are running into the registrar blocking your requests after a certain threshold. I had something similar happen with ResellerClub in the past. 0 Quote Link to comment Share on other sites More sharing options...
bear Posted June 11, 2014 Share Posted June 11, 2014 I only run the cron every 12 hours as I don't have a lot of domains to sync and it only appears to be an issue with funny TLD's like .mobi, .pw etc as the domain sync also uses the whois server to pull the data needed and if the whois server isnt responding you will get that response. I have a few hundred in WHMCS, and very few are unusual extensions. Seems to average 14-15 then flakes out, so I'll get up with NC again. They tried saying it wasn't them, and asked me to use the old sync script they'd created. It ran without error, though it wasn't connecting to WHMCS properly so I sandbox tested instead. No errors. I think you are running into the registrar blocking your requests after a certain threshold. I think you're right, and it's pretty low. Maybe this opens a connection for 50 at once, and NC sees it as a flood and kills a bunch after the first 30% or so. 0 Quote Link to comment Share on other sites More sharing options...
bear Posted June 19, 2014 Share Posted June 19, 2014 So the domain sync not supported error shows up on my personal WHMCS against NameCheap as well.I am not sure as the exact reasoning but I think it has something to do with NC's servers. Finally got some resolution from Namecheap. They supplied me with the GitHub link to their latest version of the files that resolves it. It still had a small glitch where domains in WHMCS that were mixed case or all caps failed to be found, but I let them know and they said they're going to fix that also. They also said they were talking with WHMCS to get this included in the release version of WHMCS going forward. 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.