Facebook
Twittertodor_nikov
New Pleskian
- Server operating system version
- CentOS 7
- Plesk version and microupdate number
- 18.0.68
The API endpoint returns 500 Server Error: Internal Server Error for /api/v2/databases for the Plesk version over 18.0.68
-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies! -
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
Resolved 500 Server Error: Internal Server Error for /api/v2/databases
- Thread starter todor_nikov
- Start date
-
- Tags
- api error 500
Hello, @todor_nikov . I am assuming the error message you get is:
If that's the case, the behavior is recognized as a bug identified with ID PPPM-14904. More details and a possible workaround you can find in this thread. If not, please provide the exact message you are encountering and if there are any specific steps we should be performing to reproduce the issue. Thank you in advance.
If that's the case, the behavior is recognized as a bug identified with ID PPPM-14904. More details and a possible workaround you can find in this thread. If not, please provide the exact message you are encountering and if there are any specific steps we should be performing to reproduce the issue. Thank you in advance.
