Skip to main content

S3 backup compatibility - OVH

Comments

14 comments

  • cPanelLauren
    Can you please open a ticket using the link in my signature? Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved. Thanks!
    0
  • PeppaPigKilla
    Did this get resolved ?
    0
  • Gort33
    Not yet. Our license wasn't purchased directly from cpanel so I haven't been able to open a ticket via Lauren's sig link.
    0
  • cPanelLauren
    Not yet. Our license wasn't purchased directly from cpanel so I haven't been able to open a ticket via Lauren's sig link.

    If your provider is unable or will not provide you the assistance you can always open a ticket with us - keep in mind though we do just prefer you do reach out to them first.
    0
  • HostXNow_Chris

    I was just about to create a new topic about this.

    I have OVH S3 Object Storage working fine with JetBackup to backup cPanel accounts on servers and even SolusVM 2.0 to back up the VPSs, but it does not work on the cPanel/WHM S3 Compatible backup destination.

    I tried Custom and S3 Compatible destations in WHM and it doesn't work.

    How is it S3 compatible if it isn't? So that means JetBackup and SolusVM backup sections are truly S3 Compatible, and the cPanel/WHM backup section is not?

    cPanel/WHM to OVH S3 Object Storage returns error "Error: Validation for transport “<snipped>” failed: Could not upload test file: Timeout".

    I would like to get this working on the cPanel/WHM side because I find OVH S3 Object Storage is far better compared to others like Wasabi, Amazon S3, BackBlaze, and StorJ. I tried lots of them, and the speeds are terrible. I find OVH S3 Object Storage is the best/fastest of them all!

    I highly recommend cPanel/WHM add official OVH S3 Object Storage asap.

    0
  • cPRex Jurassic Moderator

    HostXNow_Chris - it's possible that we didn't specifically test with OVH's S3 system.  However, a timeout usually indicates a more basic failure, such as a network problem.  Can you reach the destination IP and port from your cPanel server on the command line, outside of the backup interface?  If so, it would likely be best to create a ticket with our team so we can see the backup failure in action.

    0
  • HostXNow_Chris

    Ok cPRex I've created a support ticket,

    0
  • cPRex Jurassic Moderator

    Can you post that number here so I can follow along?

    0
  • HostXNow_Chris

    #95191212

    I said in the ticket

    "

    Hello,

    Please check this

    https://support.cpanel.net/hc/en-us/community/posts/19141371871639-S3-backup-compatibility-OVH?page=1#community_comment_20966949626263

    I tested OVH S3 Object Storage on many different panels, and it works fine, but not cPanel/WHM. Oddly, even newer control panels support OVH S3 Object Storage, but cPanel/WHM does not.

    Kind regards,

    Chris"

    0
  • cPRex Jurassic Moderator

    Thanks - I'm following along now!

    0
  • cPRex Jurassic Moderator

    I see our team was able to confirm the validation failures and we created this support article to help:

    https://support.cpanel.net/hc/en-us/articles/360048582713-Some-S3-Compatible-services-use-a-custom-region-not-on-the-AWS-regions-list-causing-backup-validation-failures

    I did leave a note on that case with some additional details about the problem to help out our developers.

    0
  • HostXNow_Chris

    Yes, support figured out the problem and provided a workaround, which I will confirm worked in my support ticket with them, and they'll add their workaround to the page

    https://support.cpanel.net/hc/en-us/articles/360048582713-Some-S3-Compatible-services-use-a-custom-region-not-on-the-AWS-regions-list-causing-backup-validation-failures

    Thank you.

     

     

    1
  • Russ Friesen

    Is anyone able to post the workaround?  I have been pulling out my hair trying to use OVH S3 storage, and it appears to be the same problem listed above.  (region is bhs, not a default aws region)

    0
  • Vicen

    A workaround reported by cPanel support is to edit the following file: 

    /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Amazon/S3.pm

    You would need to locate the following part of the file:

      # The "default" region for Amazon is us-east-1
      # This is the region to set it to for listing buckets
      # We don't actually list buckets in our transport, but
      # it is sometimes useful to list buckets in a test script
      # For a specific bucket, it is necessary to call adjust_region
      # to set the region that is appropriate for that bucket   

    $self->{'signer'} = Net::Amazon::Signature::V4->new(
         $self->aws_access_key_id,
         $self->aws_secret_access_key,
         'us-east-1', 's3'
       );

    Then you would replace the 'us-east-1' portion with the region of your S3 bucket. But be careful, because the file can be updated automatically and will replace it.

    Regards.

     

    0

Please sign in to leave a comment.