Issue Unable to grant the permission because it conflicts with the reseller plan.

[Krydos]

Server operating system version

AlmaLinux 9.5

Plesk version and microupdate number

Plesk Obsidian 18.0.69 Update #3

We've been using Plesk since 2021 and have always been able to grant remote database access and scheduled tasks permissions to our hosting service plans. Recently we tried to change some unrelated option on our hosting service plans, and the change failed because the option "Remote access for database users" has the error "Unable to grant the permission because it conflicts with the reseller plan." and the option "Scheduler management" has the same error "Unable to grant the permission because it conflicts with the reseller plan."



Obviously the first thing we checked was whether the reseller plan has those permissions, and found that it does.



The reseller plan has been the same since 2021, and we've been able to change hosting service plans plenty of times over the years without this error popping up. We're wondering if there is a bug with the recent versions of Plesk? We're running the fully updated Plesk Obsidian 18.0.69 Update #3 on the fully up to date AlmaLinux 9.5. If we uncheck the "Remote access for database users" and "Scheduler management" the plan will sync up. Then we can grant those permissions to subscriptions one by one, but then the subscription hosting service plan gets out of sync which causes issues changing the service plan later on.

Any ideas why this is happening recently? Is there a bug in Plesk?

 

[Krydos]

I think I may have solved it. These hosting service plans have existed since 2021 and we've just been copying and duplicating and editing them over each time. If I create a new hosting service plan from scratch I am able to grant the remote access for database users, and scheduler management as expected.

 

[Krydos]

After moving all of the subscriptions to the new hosting service plans we're still seeing the same issue. Scheduler management and Remote access for database users is still missing, and can't be enabled. In the meantime we've gone through and added these features to each subscription manually which locks the subscription from syncing. It would be nice if there is a better solution, and it would work like it used to before the recent Plesk versions were installed.

 

[scsa20]

If you've upgraded your license which includes resellers or if you've been using the reseller option and the service plan you're trying to update is associated with a reseller you'll want to make sure that the reseller plan itself has the same permission of the service plan you're updating. So go to the Service Plans section and go to the Reseller Plans and edit it.

 

[Krydos]

Yep, that is the second screenshot in my first post. Thanks.

 

[scsa20]

But did you check the settings for the reseller plan? I provided 2 screenshots so you know the process for the reseller plans.

 

[Krydos]

But did you check the settings for the reseller plan? I provided 2 screenshots so you know the process for the reseller plans.

Obviously the first thing we checked was whether the reseller plan has those permissions, and found that it does.

Yes, that was the first thing we checked, and I posted a screenshot showing that the reseller plan has the two permissions. Sorry, I must not have explained that clearly enough.

 

[Kaspar]

This sounds like odd behavior. I tried to replicate the issue on my server, but wasn't able to find anything out of the ordinary. You mentioned that you've created a new service plan from scratch. Do you remember the exact steps after that, when you ran into the issue again?

 

[Krydos]

It seems like the problem is with the reseller plan, or the reseller user itself. If we take an account that is on this reseller, and move it to a new provider then everything seems to be working so far.

 

[scsa20]

Weird, might wanna make sure none of the subscription's service plans are showing locked under that reseller otherwise I'm incline to believe there might be a database out of sync issue going on (you could try running a repair by SSHing into the server and using the command plesk repair installation. See if that helps.