Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]Problem with domain sync cron - Authentication/Authorization Failed #241

Open
sapillai opened this issue Jul 4, 2022 · 1 comment
Labels
bug can't reproduce Not able to reproduce

Comments

@sapillai
Copy link
Collaborator

sapillai commented Jul 4, 2022

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.

Active Domain Syncs
- *******-*****.art: Error: Authentication/Authorization Failed
- *****************.com: Error: Authentication/Authorization Failed
- ****.net: Error: Authentication/Authorization Failed

As per module logs, 'generateauthtokenrequest' is using an empty username and password.

To Reproduce
Steps to reproduce the behavior:

  1. Configure the WHMCS native cron in jailed shell.
  2. Check module log and cron report mail notification.

Expected behavior
Domain sync should work without problem despite running the WHMCS cron in the jailed shell.

Screenshots
image

Server info:

  • Distro: Almalinux 8.4
  • PHP: 7.2
  • Web server: Apache with FPM/FastCGI + Nginx as reverse proxy
  • Hosting control panel name and version: https://brainycp.com latest version

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)

image

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

@sapillai sapillai added the bug label Jul 4, 2022
@subedinfo-it
Copy link

We're having this bug as well, reported on ticket #1132110.

It's an intermittent situation. Either is throwing errors, or it works, can go either way without any criteria.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug can't reproduce Not able to reproduce
Projects
None yet
Development

No branches or pull requests

2 participants