New to the community? Start here

AWS PHP SDK failure when attempting to admin Shipper

Would like to know if Shipper is accessing AWS as if it is from the website or is it accessing AWS from wpmudev servers? I have an error when I try to start the admin of Shipper. See attachement.

[attachments are only viewable by logged-in members]

I have a lockdown on AWS. I set the security for the bucket that only the website, in this case oceans2u.com can directly access the bucket. If your AWS SDK for Shipper does not access AWS from the website but from one of your servers, it will not work.

So how would I identify your servers, if that is the case, otherwise what is the issue?

The identity can be an FQD ie. oceans2u.com

Support access is enabled.

Wed, 27 Mar 2019 20:36:24
More Shipper Pro discussions
Shipper Pro
  • Nithin Ramdas
    • Support Wizard

    Hi Lee,

    This error usually occurs in the pre-flight check, when there is a plugin that also comes with the AWS SDK and most probably an older version, and hence causing such error. Shipper is using v3.

    Disabling the plugin which makes use of AWS temporarily, should solve this error and allow you to proceed with the migration.

    I have a lockdown on AWS. I set the security for the bucket that only the website, in this case oceans2u.com can directly access the bucket. If your AWS SDK for Shipper does not access AWS from the website but from one of your servers, it will not work.

    So how would I identify your servers, if that is the case, otherwise what is the issue?

    I’ll have to double check regarding this with the developer. Could I know which exact plugin is making use of AWS, and in the meanwhile please check whether the error occurs even after disabling it too?

    Will keep you posted once I get further feedback regarding the status of the query asap. Have a nice day ahead. :slight_smile:

    Regards,

    Nithin

  • Nithin Ramdas
    • Support Wizard

    Hi Lee,

    Got an update regarding this from the developer. We aren’t working on your website AWS bucket, and using our own, and it shouldn’t get locked down in such use case.

    As mentioned in the previous reply, the issue is more related due to legacy AWS SDK either used in your custom code or via a plugin. Which should be fixed once the related plugin is deactivated. Please let us know how that goes. :slight_smile:

    Kind Regards,

    Nithin

  • Lee
    • Syntax Hero

    AWS plugin: https://wordpress.org/plugins/amazon-s3-and-cloudfront/

    1. Can’t disable all my images are on AWS for 200 products or more in ecom store.

    2. Shipper takes to long to migrate etc.

    3. AWS lockdown means you can not access images for copy unless that copy comes from oceans2u.com or if I add another FQD to the list.

    So guess can’t use shipper. Shipper should never be blocked by other plugins. Please ask development to fix issue.

  • Nithin Ramdas
    • Support Wizard

    Hi Lee,

    Our developer was able to notice what you meant, we are going to implement changes on how AWS is included in the upcoming release most probably on version 1.0.3 so that such conflicts would be covered.

    As for the lockdown, there shouldn’t be a problem, most probably you might have to reconfigure the WP offload plugin on your destination site and grant the access to your AWS for destination domain as well. This would bring much clarity once the initial conflict is resolved.

    However, at the moment, I’m afraid, there isn’t any workaround regarding this in the current version, other than disabling the Offload plugin.

    Regards,

    Nithin