BackWPup conflict with Composer AWS PHP SDK

  • Hi,

    I’ve been using BackWPup on a website for a year without any problems. This week I installed the AWS PHP SDK through Composer, for use in a custom theme, and using a .env file for the AWS credentials. Since then, BackWPup can no longer do backups to AWS S3 as before. Please see log file output below. It seems BackWPup is looking for AWS credentials in the .env file, is it? Can I tell it not to look there or can I simply add the AWS version to my .env file?

    
[INFO] BackWPup 3.4.1; A project of Inpsyde GmbH
[INFO] WordPress 4.8.2 on [URL hidden]
[INFO] Log Level: Normal 
[INFO] BackWPup job: Hourly database backup to S3
[INFO] Logfile is: backwpup_log_[hidden]_2017-09-27_12-00-03.html
[INFO] Backup file is: backwpup_[hidden]01_database_2017-09-27_12-00-03.tar.gz
[27-Sep-2017 12:00:03] 1. Try to backup database …
[27-Sep-2017 12:00:03] Connected to database [name_hidden] on localhost
[27-Sep-2017 12:00:04] Added database dump "[name_hidden].sql.gz" with 1,61 MB to backup file list
[27-Sep-2017 12:00:04] Database backup done!
[27-Sep-2017 12:00:04] 1. Trying to generate a manifest file …
[27-Sep-2017 12:00:04] Added manifest.json file with 4,08 KB to backup file list.
[27-Sep-2017 12:00:04] 1. Trying to create backup archive …
[27-Sep-2017 12:00:04] Compressing files as TarGz. Please be patient, this may take a moment.
[27-Sep-2017 12:00:04] Backup archive created.
[27-Sep-2017 12:00:04] Archive size is 1,60 MB.
[27-Sep-2017 12:00:04] 3 Files with 1,61 MB in Archive.
[27-Sep-2017 12:00:04] 1. Trying to send backup file to S3 Service …
[27-Sep-2017 12:00:04] ERROR: S3 Service API: Missing required client configuration options: version: (string) A "version" configuration value is required. Specifying a version constraint ensures that your code will not be affected by a breaking change made to the service. For example, when using Amazon S3, you can lock your API version to "2006-03-01". Your build of the SDK has the following version(s) of "s3": * "2006-03-01" You may provide "latest" to the "version" configuration value to utilize the most recent available API version that your client's API provider can find. Note: Using 'latest' in a production application is not recommended. A list of available API versions can be found on each client's API documentation page: https://docs.aws.amazon.com/aws-sdk-php/v3/api/index.html. If you are unable to load a specific API version, then you may need to update your copy of the SDK.
[27-Sep-2017 12:00:04] 2. Trying to send backup file to S3 Service …
[27-Sep-2017 12:00:04] ERROR: S3 Service API: Missing required client configuration options: version: (string) A "version" configuration value is required. Specifying a version constraint ensures that your code will not be affected by a breaking change made to the service. For example, when using Amazon S3, you can lock your API version to "2006-03-01". Your build of the SDK has the following version(s) of "s3": * "2006-03-01" You may provide "latest" to the "version" configuration value to utilize the most recent available API version that your client's API provider can find. Note: Using 'latest' in a production application is not recommended. A list of available API versions can be found on each client's API documentation page: https://docs.aws.amazon.com/aws-sdk-php/v3/api/index.html. If you are unable to load a specific API version, then you may need to update your copy of the SDK.
[27-Sep-2017 12:00:04] 3. Trying to send backup file to S3 Service …
[27-Sep-2017 12:00:04] ERROR: S3 Service API: Missing required client configuration options: version: (string) A "version" configuration value is required. Specifying a version constraint ensures that your code will not be affected by a breaking change made to the service. For example, when using Amazon S3, you can lock your API version to "2006-03-01". Your build of the SDK has the following version(s) of "s3": * "2006-03-01" You may provide "latest" to the "version" configuration value to utilize the most recent available API version that your client's API provider can find. Note: Using 'latest' in a production application is not recommended. A list of available API versions can be found on each client's API documentation page: https://docs.aws.amazon.com/aws-sdk-php/v3/api/index.html. If you are unable to load a specific API version, then you may need to update your copy of the SDK.
[27-Sep-2017 12:00:04] ERROR: Step aborted: too many attempts!
[27-Sep-2017 12:00:04] One old log deleted
[27-Sep-2017 12:00:04] ERROR: Job has ended with errors in 1 seconds. You must resolve the errors for correct execution.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Bet Hannon

    (@bethannon1)

    Hi Gesen!

    I’m getting this error too, although I have made no changes to Amazon or SDK. Did you get this worked out?

    I’m getting this even though we have 100+ other sites on the same server, using the same S3 account that are not getting this error. It’s a real puzzle!

    Thread Starter Emil Gustafsson

    (@gesen)

    I still have this problem on sites running BackWPup and the AWS SDK through Composer. Sites using the AWS SDK not through Composer are not having this problem.

    Since I have found no solution on this, I have had to give up on BackWPup on some sites. Can’t have unreliable backup solutions, right?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘BackWPup conflict with Composer AWS PHP SDK’ is closed to new replies.