Sorry guys, I wrote another post, but now cannot find it.
I really need help configuring my Plesk server to connect to the OVH Public Cloud S3 Object Storage.
I have created the containers, I have the Plesk S3 paid for Extension and if I use another provider, Back Blaze it works perfectly, but replacing the bucket and user details with the ones from OVH, it errors straight away
I've attached the screenshot to show how it's setup. the user has Administrator rights and is connected to the container
Ensure you're using the correct endpoint for OVH's S3 service. OVH typically requires a custom endpoint, such as s3.<region>.cloud.ovh.net. Double-check that the endpoint matches the region of your container.
Credential format: Verify that the Access Key and Secret Key are copied exactly as they appear in the OVH console. Also, ensure that the user has full permissions over the container.
Container permisssion policy: In the OVH console, review the policy associated with the container and the user. Ensure it allows operations such as GetObject, PutObject, and DeleteObject.
Check the system logs in Plesk to identify the exact error. Look for details in /var/log/plesk/panel.log or the specific logs for the S3 extension.
Note: If the OVH endpoint doesn’t have a valid SSL certificate or Plesk doesn’t recognize it, the connection might be blocked. Temporarily disable SSL validation in Plesk to see if it resolves the issue. If it works, configure an endpoint with a valid SSL certificate.
I've tried all of the above and I get the same error, however there is a few discrepancies.
My server is based in Lim (Limberg Germany) but there is no container location there, only Frankfurt - which I have tried - but still wont connect.
I cant see where to view and check the container policy on OVH console, only options using the three dots, are assigned a user, display objects or delete?
I've screen grabbed again, the exact setup I've done to make sure the relative data is used in the correct fields.
I've cracked it, and this might help others who face the same issue.
The config as I had it was all good, and even though the servers were located in the same country, the locale that was initially setup by Plesk was US, so I just had to amend the location to de & uk respectively. I used the Panel.ini editor for this and just added the lines below to the 'Editor' window
Try a public bucket: Create a public bucket in the same region as the container and try to access it from Plesk. This will help rule out issues with Plesk credentials or settings.
If the problem persists, I would recommend that you open a ticket to support.
Unable to check bucket and directory existence. Make sure you are using correct IAM policy (403 Forbidden (Request-ID: tx6e9316f997af45509c27e-00693fec66)).