Urbit: Digital Ocean Spaces S3 integration in the chat app doesn't work

Created on 9 Sep 2020  Â·  11Comments  Â·  Source: urbit/urbit

I have created a Space on Digital Ocean (their S3 compatible service) and filled in the correct details under the settings tab on Urbit. When I try to post an image, I get the following error in the console:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://fonnyx-nopmer.ams3.cdn.digitaloceanspaces.com/fonnyx-nopmer/2020.9.09..15.20.05-bee.png. (Reason: CORS header 'Access-Control-Allow-Origin' missing).

It looks to me as if I have set up things correctly on the DO side:

image

If I run :s3-store +dbug the output looks correct.

I am using Firefox.

I believe @custom-jonathan also has this problem.

undocumented

Most helpful comment

Yep, worked like a charm.

All 11 comments

Yep, I've added * in the origin & header field, and I still get the same errors.

Check out the guide:

https://github.com/urbit/support/wiki/How-to-set-up-S3-integration

You need to loosen CORS further. @tacryt-socryp wrote the integration with DO so maybe he can opine.

On Sep 9, 2020, at 11:29 AM, fonnyx notifications@github.com wrote:


I have created a Space on Digital Ocean (their S3 compatible service) and filled in the correct details under the settings tab on Urbit. When I try to post an image, I get the following error in the console:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://fonnyx-nopmer.ams3.cdn.digitaloceanspaces.com/fonnyx-nopmer/2020.9.09..15.20.05-bee.png. (Reason: CORS header 'Access-Control-Allow-Origin' missing).
It looks to me as if I have set up things correctly on the DO side:

If I run :s3-store +dbug the output looks correct.

I am using Firefox.

I believe @custom-jonathan also has this problem.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I'm afraid I don't know what to put in the "Allowed Headers" field, so I will have to wait for someone who knows how to get it working on DO.

Allowed Headers should be *

Having tried that, I am afraid I still get the same error in the console.

Having tried that, I am afraid I still get the same error in the console.

I have to ask, in your screenshot, did you put * and press "Save Options" or did you put * and press "Add Header"? It's not clear how you'd add a header example.

I have the same experience. I press save. Hard refresh the DO page to make sure it really saved. Then hard refresh landscape, and it doesn't work.

Yep, worked like a charm.

I have it working now. The problem was not having these two things match:

Was this page helpful?
0 / 5 - 0 ratings

Related issues

custom-jonathan picture custom-jonathan  Â·  5Comments

hrharder picture hrharder  Â·  14Comments

rabsef-bicrym picture rabsef-bicrym  Â·  7Comments

custom-jonathan picture custom-jonathan  Â·  10Comments

JohnELester picture JohnELester  Â·  4Comments