Could not get region from server? DO Spaces

  • Resolved Tanner

    (@tannerchung)


    6 years, 4 months ago

    [Tue Oct 30 01:53:29.739242 2018] [proxy_fcgi:error] [pid 18368:tid 140078210873088] [client 10.136.137.10:0] AH01071: Got error ‘PHP message: [2018-10-30 01:53:29] ilab-media-tool.INFO: Could not get region from server. [] []\nPHP message: [2018-10-30 01:53:29] ilab-media-tool.INFO: Could not create regular client, creating multi-region client instead. [] []\n’, referer: https://example.com/wp-admin/media-new.php

    I’m using the plugin to connect to DO Spaces and whenever I upload an image it shows a 404 error. If I don’t use the plugin, the image is able to be uploaded successfully.

    I should note that I’m on a load balanced server Cloudflare->DO Load Balancer->2xWP App (with a mounted gluster fs)

    Is there anyway to debug this further?

    • This topic was modified 6 years, 4 months ago by Tanner.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Tanner

    (@tannerchung)

    Got this from the apache error log

    [Tue Oct 30 01:51:41.508344 2018] [proxy_fcgi:error] [pid 18368:tid 140078202480384] [client 10.136.137.10:0] AH01071: Got error 'PHP message: [2018-10-30 01:51:40] ilab-media-tool.INFO: Could not get region from server. [] []\nPHP message: [2018-10-30 01:51:40] ilab-media-tool.INFO: Could not create regular client, creating multi-region client instead. [] []\nPHP message: [2018-10-30 01:51:41] ilab-media-tool.INFO: Start Upload {"file":"2018/10/Screenshot_102918_040749_PM.jpg"} []\nPHP message: [2018-10-30 01:51:41] ilab-media-tool.ERROR: S3 Upload Error {"exception":"Error executing \\"PutObject\\" on \\"https://nyc3.digitaloceanspaces.com/example/2018/10/Screenshot_102918_040749_PM.jpg\\"; AWS HTTP error: Client error:PUT https://nyc3.digitaloceanspaces.com/example/2018/10/Screenshot_102918_040749_PM.jpgresulted in a400 Bad Requestresponse:\\n<?xml version=\\"1.0\\" encoding=\\"UTF-8\\"?><Error><Code>InvalidArgument</Code><RequestId>tx000000000000004187878-005bd7b92d-1 (truncated...)\\n1InvalidArgument (client): - <?xml version=\\"1.0\\" encoding=\\"UTF-8\\"?><Error><Code>InvalidArgument</Code><RequestId>tx000000000000004187878-005bd7b92d-1433241-nyc3a</RequestId><HostId>1433241-nyc3a-nyc</HostId></Error>","bucket":"example","key":"2018/10/Screenshot_102918_040749_PM.jpg","privacy":"public-read","options":[]} []\nPHP message: [2018-10-30 01:51:41] ilab-media-tool.ERROR: Upload Error {"exception":"Error executing \\"PutObject\\" on \\"https://nyc3.digitaloceanspaces.com/example/2018/10/Screenshot_102918_040749_PM.jpg\\"; AWS HTTP error: Client error:PUT https://nyc3.digitaloceanspaces.com/example/2018/10/Screenshot_102918_040749_PM.jpgresulted in a400 Bad Requestresponse:\\n<?xml version=\\"1.0\\" encoding=\\"UTF-8\\"?><Error><Code>InvalidArgument</Code><RequestId>tx000000000000004187878-005bd7b92d-1 (truncated...)\\n InvalidArgument (client): - <?xml version=\\"1.0\\" encoding=\\"UTF-8\\"?><Error><Code>InvalidArgument</Code><RequestId>tx000000000000004187878-005bd7b92d-1433241-nyc3a</RequestId><HostId>1433241-nyc3a-nyc</HostId></Error>","prefix":"2018/10/","bucketFilename":"Screenshot_102918_040749_PM.jpg","privacy":"public-read"} []\n

    • This reply was modified 6 years, 4 months ago by Tanner.
    Plugin Author interfacelab

    (@interfacelab)

    Yes, that’s how DO works but I tried to make the backend as generic as possible, so it will attempt to create a normal client first, but if no region was specified then it creates a multi region client.

    I tested DO a lot today and didn’t run into any issues.

    I’ve not tested DO with Cloudflare or a load balancer, so I have to think one or the other is causing the issue.

    Your bucket must explicitly be set to public with DO though, unlike S3, which is maybe why you are getting the 404 or 400 errors. Spaces doesn’t have ACLs like S3 yet.

    Thread Starter Tanner

    (@tannerchung)

    Ah okay I’ll take a look at the settings. The errors like these keep disappearing after I report them so it’s been really difficult to reproduce. So far I haven’t ran into any issues but the staging server is just 2017 theme so it’s hard to predict what other errors may show up.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Could not get region from server? DO Spaces’ is closed to new replies.