• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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