We need to investigate and check in n8n sources.
We need to investigate and check in n8n sources.
KIs it worth updating https://developers.cloudflare.com/r2/data-access/s3-api/api/#bucket-region to nudge people towards the location hints beta?
SCan you force N8N to use
Also I don't understand what you meant by
autoAlso I don't understand what you meant by
N8N node uses the region from the R2 response as value for next request
SAh good idea, let me ask @denisep
KI guess the CreateBucket part further down on the table could also be updated to show that LocationConstraint is now implemented at experimental
KListMultipartUploads is still down as experimental from when it was first added, not sure if it’s moved towards stable for the rest of the query params yet
SHuh, pretty sure these are implemented now. Let me double-check and we can probably remove the 
from there as well
from there as wellKI don’t think it’s been changed since it was released haha
Khttps://developers.cloudflare.com/r2/learning/consistency/#operations-and-consistency this table only shows one column on mobile - not sure what’s up with it 
K
CWe are investigating this now, it is a standard n8n node. From n8n frontend we provide region 'auto'. But according to the error somewhere behind the scenes the value WEUR is send. But now we know we are looking in the correct place in sources and that R2 had changed region behaviour today
K
SFrederik also changed the UI to reflect the public-ness of custom domains based on feedback here!
Ewoah
Epretty
SAlso the buckets page should feel considerably faster. Let me know if y'all find bugs in there
KCORS also has a delete confirmation now
K
SHaha big release day
KDoes GetBucketLocation return the hint?
SGetBucketLocation returns where the bucket actually is
KI think n8n does that and then signs with that region, which it sounds like is being rejected since it only wants auto/us-east-1/empty string
Synology is similar and makes a location call when you setup a job
Synology is similar and makes a location call when you setup a job
Kunless you now allow those hints as a region in that case ignore me
KI haven’t tested any of it - just a thought
SLocations will make their way to the dash once they're out of beta!
CBut then R2 for now van perhaps better accepts also weur and treat it as auto?
Kthat’s what I’d expect it to do, yes
Kotherwise lots of tooling will explode
Ekaboom
Kthe location returned by GetBucketLocation is then used in SigV4 signing by <non-trivial amount of things>
K
Ewhen i tell sharex to use
enam
Eit gets back
EEwhere enam is one of the ones listed 
E"sorry enam isnt valid, please use enam"
K
HZero-Width Space Time!
CExactly what we have with weur....
E@sdnts this is the error thats happening, providing a region doesnt seem to work and despite the error msg it doesnt accept the new values
Eit only works if i supply
autous-east-1wnam, enam, weur, apacOh, thanks for checking, let me look
Ealso thank you whoever let me have tokens that live forever now, it was annoying when this got removed and i had to remember or risk my apps exploding in a year
Eah i see
E
Eone i just made doesnt, only Active
Edid you make those tokens just now? Forever wasnt available until recently
Eor did you edit an existing one?