You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am creating this issue on behalf of an Openprovider reseller. The reseller reported a problem with domain sync. Domain status sync job always fails with the error "Authentication/Authorization Failed". API credentials are correct and all other operations including domain registration, TLD price sync, etc. are working fine.
Additional context
The problem only occurs when the WHMCS cron job is running in the jailed shell. When the cron is run as root or in a normal shell, domain sync is working fine. List of packages available in Jail Shell (BraincyCP)
Domain synchronization is working fine in the jailed shell with other reseller modules for example Resellerclub. Possibly, being unable to access the module/binary for encrypting username/password is causing the problem.
Regards,
Openprovider Support
The text was updated successfully, but these errors were encountered:
Describe the bug
I am creating this issue on behalf of an Openprovider reseller. The reseller reported a problem with domain sync. Domain status sync job always fails with the error "Authentication/Authorization Failed". API credentials are correct and all other operations including domain registration, TLD price sync, etc. are working fine.
As per module logs, 'generateauthtokenrequest' is using an empty username and password.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Domain sync should work without problem despite running the WHMCS cron in the jailed shell.
Screenshots
Server info:
Additional context
The problem only occurs when the WHMCS cron job is running in the jailed shell. When the cron is run as root or in a normal shell, domain sync is working fine. List of packages available in Jail Shell (BraincyCP)
Domain synchronization is working fine in the jailed shell with other reseller modules for example Resellerclub. Possibly, being unable to access the module/binary for encrypting username/password is causing the problem.
Regards,
Openprovider Support
The text was updated successfully, but these errors were encountered: