I can confirm that the S3 Location is us-east-1.linodeobjects.com
My previous post is explaining that is not a location, that is an endpoint.
and S3 endpoint is “mybucketname”
Entering this as the endpoint is wrong because that is not an endpoint, that is a location.
As mentioned, I have double checked the credentials many times
On each occasion above that you explicitly state what details you have entered in the “endpoint” and “location” fields, these details are the wrong way round. This is what my previous post is trying to explain.
Even the fact that I enter the information that should be the correct way (ie, endpoint is ONLY the bucket name and S3 location is only the linode address – us-east-1.linodeobjects.com)
That is entering the information the incorrect way.
To be clear:
us-east-1.linodeobjects.com is an endpoint. This is as per step 1 of the instructions, “The end-point. This depends upon which Linode region you want to use for the storage. The end-point is (region).linodeobjects.com – e.g. us-east-1.linodeobjects.com.”
mybucketname can be entered as your location (or things like mybucketname/subdirectory to put them in a pseudo-subfolder).
Did you ever have your developer look into this and try themselves with the S3 Compatible settings and Linode Objects storage, and your free version of this plugin?
Yes, we have a test site that backs up daily to Linode, and it is working as expected. But on that site, we entered the credentials as described in my previous post, not the way that you have described entering them.
errors about being able to access the bucket but not able to write a file
If you see such an error after entering the details the correct way round, the most likely cause of this is what is mentioned at the end of the documentation, “you used a bucket name that another Linode user had already taken. (The name-space is shared globally). So, pick another one.” Linode’s error reporting won’t explicitly tell you that another user already has the bucket name, but it’s the error you’ll see. (But if you can write to the bucket in another tool, then that’s not the problem).