-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Incorrect use of Plesk API to get list of domains #4735
Comments
Please upgrade to the latest code and try again first. Maybe it's already fixed. |
@eg321 can you please tell which Plesk Edition you are using? It looks like Plesk has different behaviours in their editions: Web Host/Web Pro/Web Admin, see: https://www.plesk.com/editions/ You can find this information in your Plesk Admin Panel here: [Tools & Settings -> Plesk -> About Plesk] |
@lufi42 it's a shared hosting on reg.ru provider, so it's a definitely I don't have other Plesk versions to check, but it's definitely strange that you request webspaces to get domains. Is it really returns also all domains on your version? or maybe it works, because you have only single domain in that webspace and they have same name? |
Steps to reproduce
I'm using acme behind PFSense's Acme service. So my STR is simple:
Actual result
Operation failed with message:
Are you sure that this domain is managed by this Plesk server?
Error add txt for domain:_acme-challenge.yyy.com
Additional info
As I can see, there is incorrect call to Plesk API to get list of domains - it's trying to get list of webspaces instead of domains. Webspaces it's like "subscription" in Plesk term and can contain several domains inside. Webspace name is not website name in general case.
It looks like it was broken by @lufi42 with that commit: a6b58bc
I've reverted this specific commit and it's working for me again.
@lufi42, can you check if your case can be fixed in other manner, not broking case described above please?
Please let me know, if you need any additional information.
Debug log (i've replaced some domain names, usernames and other private info)
The text was updated successfully, but these errors were encountered: