• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Plesk API key not working

RafaExpert

New Pleskian
Server operating system version
Ubuntu 22.04.4 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.61 Update #5
Hello community!

I have installed a Laravel app in AWS LightSail instance with OS: Ubuntu 22.04.4 LTS and Plesk Obsidian 18.0.61 Update #5

Everything has been working perfect during some days as expected, but suddenly I got an error when the app creates new databases.

The Laravel app use an "API secret Key" that was generated during the installation and basically it create a unique Database for every new customer. Suddenly I couldn't create any customer database because an error.

Checking the server log I see this:
Screenshot.png
And digging more in the log, when it was working, I see this:
Screenshot2.png

As you can compare both logs, the IP used now is the "Private server IP" 172.26.x.x instead of the "Public IP" 13.38.x.x and the user is "" and not "admin".

I can't figure out why now it is using the Private IP and not the Public IP.

Anybody have any light on this issue, why this is happening and can help me?

Thanks in advance...
 
Back
Top