Fatal Errors while connecting to S3

  • Resolved helikazeta

    (@helikazeta)


    3 years, 7 months ago

    Hello,

    Can you explain this error to me, and possible resolution?
    Thank you

    [19-Apr-2021 14:24:20 UTC] PHP Fatal error: Uncaught Aws\Exception\InvalidRegionException: Region must be a valid RFC host label. in /home/customer/www/******.com/public_html/wp-content/plugins/wp-media-storage-to-cloud/vendor/aws/aws-sdk-php/src/ClientResolver.php:543
    Stack trace:
    #0 /home/customer/www/*****.com/public_html/wp-content/plugins/wp-media-storage-to-cloud/vendor/aws/aws-sdk-php/src/ClientResolver.php(323): Aws\ClientResolver::_apply_endpoint_provider(Object(Aws\Endpoint\Partition), Array, Object(Aws\HandlerList))
    #1 /home/customer/www/*******.com/public_html/wp-content/plugins/wp-media-storage-to-cloud/vendor/aws/aws-sdk-php/src/AwsClient.php(199): Aws\ClientResolver->resolve(Array, Object(Aws\HandlerList))
    #2 /home/customer/www/*******.com/public_html/wp-content/plugins/wp-media-storage-to-cloud/vendor/aws/aws-sdk-php/src/S3/S3Client.php(346): Aws\AwsClient->__construct(Array)
    #3 /home/customer/www/*******.com/public_html/wp-content/plugins/wp-media-storage-to-cloud/admin/channels/class-w2cloud-aws-process.php(206): Aws\S3\S3Client->__cons in /home/customer/www/*******.com/public_html/wp-content/plugins/wp-media-storage-to-cloud/vendor/aws/aws-sdk-php/src/ClientResolver.php on line 543

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support Rafi Alam

    (@raficode)

    Hello @helikazeta ,

    Can you please cross-check whether you are entering the correct Region?

    Also, can you please give me a screenshot of the error from the plugin dashboard?

    Thank you.

    • This reply was modified 3 years, 7 months ago by Rafi Alam.
    Thread Starter helikazeta

    (@helikazeta)

    Screenshot => https://snipboard.io/PA5EUp.jpg

    What is the actual syntax for entering the bucket and region?

    We currently have it as:
    hhttps://s3.us-east-1.amazonaws.com for region &
    https://****.s3.us-east-1.amazonaws.com for bucket name

    Is that correct?

    • This reply was modified 3 years, 7 months ago by helikazeta.
    Plugin Support Rafi Alam

    (@raficode)

    Hello @helikazeta ,

    Yes, the links you’ve sent seem correct.

    However, can you please send me a screenshot of the plugin dashboard with the error you are getting after entering all the details and click on Save button?

    Also, can you tell me exactly what Region did you enter in the Region field?

    Let me know.

    Thank you.

    Thread Starter helikazeta

    (@helikazeta)

    It just reports “Error Occurred. Please Check Again all information”
    See snapshot here -> https://snipboard.io/k35lwi.jpg

    I input the access key ***
    the secret key ***
    s3 bucket name = https://xxx.s3.us-east-1.amazonaws.com
    Bucket Region = hhttps://s3.us-east-1.amazonaws.com

    I’ve changed the access key and secret key multiple times for IAM account but no joy

    Plugin Support Rafi Alam

    (@raficode)

    Hello @helikazeta ,

    Did you enter “us-east-1” as your bucket region? or Did you enter something else?

    Can you please give us the exact Bucket name and Region you entered here:

    Such as,
    Bucket name: testbucket
    Region: us-east-1

    Let me know.

    Thank you.

    Thread Starter helikazeta

    (@helikazeta)

    I was using the bucket and bucket region as below.
    s3 bucket name = https://xxx.s3.us-east-1.amazonaws.com
    Bucket Region = hhttps://s3.us-east-1.amazonaws.com

    I assumed that was the syntax Amazon recommended.

    Anyway, I’ve modified it to
    Bucket name: dz1
    Region us-east-1

    Same error.
    See it here =>https://snipboard.io/wBuSUE.jpg

    Hope that helps

    Plugin Support Rafi Alam

    (@raficode)

    Hello @helikazeta ,

    Well, we tried to recreate this issue on our server but it seems to be working fine.

    At this point, we believe, it depends on certain settings on your site for which this is happening.

    In this case, can you create a Sandbox environment or a Staging server with the same situation and give it us to use? Then we could observe directly and find a quick solution.

    Thanks.

    Plugin Support Rafi Alam

    (@raficode)

    Hello @helikazeta ,

    I was following up to see if the issue was resolved.

    If not, then can you please reply with the inquired data.

    Thanks.

    Thread Starter helikazeta

    (@helikazeta)

    okay. Give me 24hrs to setup sandbox.
    I’ll come back to you

    Plugin Support Rafi Alam

    (@raficode)

    Hello @helikazeta ,

    I was following up to see if the issue was resolved.

    If not, then can you please reply with the inquired data.

    Thanks.

    Plugin Support Rafi Alam

    (@raficode)

    Hello @helikazeta ,

    Since we haven’t heard anything from you in a while, we’re now closing this thread.

    You’re always welcome to open another thread if you face any more issues with our plugin.

    Thanks.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Fatal Errors while connecting to S3’ is closed to new replies.