How to use the same registrar you already setup, with different credentials

[Himeko]

Is there any way to add a secondary Resellerclub registrar with different ID/ApiKey?

[brian!]

1 hour ago, Himeko said:

Is there any way to add a secondary Resellerclub registrar with different ID/ApiKey?

yes, use the NetEarthOne or Stargate/UK2 registrars - they just redirect to the resellerclub registrar module anyway, so you'd be able to enter different login details for them... all three are LogicBoxes resellers and use the same software and API.

[Himeko]

Thank you. I tried the Stargate one, and it seems to be working but when I list the domains for a client under this reseller, the expiry dates dont seem to be acquired upon sync, is that a known issue or limitation?

[brian!]

17 hours ago, Himeko said:

I tried the Stargate one, and it seems to be working but when I list the domains for a client under this reseller, the expiry dates dont seem to be acquired upon sync, is that a known issue or limitation?

there shouldn't be any issue or limitation with this - I use the Stargate module myself for Resell.biz (though I don't domain sync).

although remember that the Domain Sync only synchronises 50 domains at a time, so if you have a lot of domains within WHMCS, then its possible that these Stargate domains haven't been scheduled for syncing yet (as it starts with the oldest - e.g those you added first to WHMCS, not necessarily the longest registered).

you could check the activity log to see if the cron is running correctly and not showing errors... and/or you could double-check with Support that there are no known sync issues - but the solution has been previously suggested by WHMCS themselves, and i'm not aware that there has been any change in that advice.

... if Support tell you otherwise, feel free to update the thread with their reply. 🙂

[Himeko]

The cron seems to be running correctly, also I have tried invoking it manually from ssh with no errors reported, but still the dates all show 0000-00-00

 

Quote

2019-01-14 08:00    
Automated Task: Starting WHMCS Updates
System    
2019-01-14 00:02    
Cron Job: Backup Complete
System    
2019-01-14 00:02    
Cron Job: Email Backup - Sent Successfully
System    
2019-01-14 00:02    
Cron Job: Backup Generation Completed
System    
2019-01-14 00:02    
Cron Job: Starting Backup Zip Creation
System    
2019-01-14 00:02    
Cron Job: Backup Database Dump Complete
System    
2019-01-14 00:00    
Cron Job: Starting Backup Database Dump
System    
2019-01-14 00:00    
Cron Job: Starting Backup Generation
System    
2019-01-14 00:00    
Cron Job: Completed Daily Automation Tasks
System    
2019-01-14 00:00    
Automated Task: Starting WHMCS Updates
System    
2019-01-14 00:00    
Automated Task: Starting Data Retention Pruning
System    
2019-01-14 00:00    
Automated Task: Starting Domain Expiry
System    
2019-01-14 00:00    
Automated Task: Starting Client Status Update
System    
2019-01-14 00:00    
Automated Task: Starting Server Usage Stats
System    
2019-01-14 00:00    
Automated Task: Starting Email Marketer Rules
System    
2019-01-14 00:00    
Automated Task: Starting Delayed Affiliate Commissions
System    
2019-01-14 00:00    
Automated Task: Starting Inactive Tickets
System    
2019-01-14 00:00    
Automated Task: Starting Fixed Term Terminations
System    
2019-01-14 00:00    
Automated Task: Starting Overdue Terminations
System    
2019-01-14 00:00    
Automated Task: Starting Overdue Suspensions
System    
2019-01-14 00:00    
Automated Task: Starting Cancellation Requests
System    
2019-01-14 00:00    
Automated Task: Starting Domain Renewal Notices
System    
2019-01-14 00:00    
Automated Task: Starting Invoice & Overdue Reminders
System    
2019-01-14 00:00    
Automated Task: Starting Credit Card Charges
System    
2019-01-14 00:00    
Cron Job: Late Invoice Fees added to 0 Invoices
System    
2019-01-14 00:00    
Automated Task: Starting Late Fees
System    
2019-01-14 00:00    
Automated Task: Starting Invoices
System    
2019-01-14 00:00    
Cron Job: Products Updated for Current Rates
System    
2019-01-14 00:00    
Automated Task: Starting Product Pricing Updates
System    
2019-01-14 00:00    
Automated Task: Starting Currency Exchange Rates
System    
2019-01-14 00:00    
Cron Job: Starting Daily Automation Tasks
System

 

[brian!]

3 hours ago, Himeko said:

The cron seems to be running correctly, also I have tried invoking it manually from ssh with no errors reported, but still the dates all show 0000-00-00

is the domain synchronisation feature enabled in the automation settings ??

if using a pre v7.6 version, have you added a domain sync cron ??

https://docs.whmcs.com/Domain_Synchronisation#Setting_it_up

[Himeko]

7 hours ago, brian! said:

is the domain synchronisation feature enabled in the automation settings ??

if using a pre v7.6 version, have you added a domain sync cron ??

https://docs.whmcs.com/Domain_Synchronisation#Setting_it_up

yes, under "Domain Sync Enabled"

Quote

Cron Status OkLast Run: 2019-01-14 23:50

I'm on latest version 7.6.1

cron is setup as "php -q /home/brian/whmcs_crons/domainsync.php"

[bear]

12 hours ago, Himeko said:

I'm on latest version 7.6.1

cron is setup as "php -q /home/brian/whmcs_crons/domainsync.php"

If that's the one that came with WHMCS, I believe that file does nothing in versions past 7.5. It's there as a placeholder only, and has no functions in it. 

[brian!]

1 hour ago, bear said:

If that's the one that came with WHMCS, I believe that file does nothing in versions past 7.5. It's there as a placeholder only, and has no functions in it. 

@bear is right - if it's v7.6.1, then that sync functionality is now within the main cron and no secondary domain sync cron is necessary.

i'd probably suggest opening a ticket with Support and get them to check why the main cron isn't running the domain sync processes.

[Himeko]

This issue seems to have been fixed since I updated to 7.7.0. Thank you for the help.

Edited January 24, 2019 by Himeko

[brian!]

9 hours ago, Himeko said:

This issue seems to have been fixed since I updated to 7.7.0. Thank you for the help.

i'd glad we got there in the end! 🙂