As I’m constantly frustrated by breakage of the Azure Blob Storage plugin, I’ve run a Flexify.IO server to translate the Azure into S3 protocol. However, after setting into Discourse, it doesn’t work. The error is: Failed to open TCP connection to support.xxx.xxx.xxx.xxx:443 (getaddrinfo: Name or…

I have a feeling that my setting for the s3_bucket is wrong, since it is appending the bucket name to the endpoint URL itself. app/models/site_setting.rb 9b7c17b92 bucket = SiteSetting.enable_s3_uploads ? Discourse.store.s3_bucket_name : GlobalSetting.s3_bu…

Given this: [afbeelding] schungx: xx.xx.xx.xx is the IP address of the S3 gateway Then this is definitely wrong: [afbeelding] schungx: support.xxx.xxx.xxx.xxx:443 The error message says as much. getaddrinfo: Name or service not known is a DNS lookup failure; There will never be a hos…

[afbeelding] schleifer: Where did you get the “support” part from? Oh, sorry. support is the bucket name. I can see that S3 simply prepends the bucket name to the domain name, and this is assumed by Discourse. [afbeelding] schleifer: So you can’t use the admin console to change it, ins…

@Falco @schleifer Alright, I’ve tried it, but unfortunately it is still giving me the exact same error. Therefore, I don’t think it works even when hard-coded into app.yaml. They seem to go into the same code stream. This is my app.yaml setting: DISCOURSE_USE_S3: true DISCOURSE_S3_REGION: e…

[afbeelding] schungx: Is there a way to get the exact error message? Have you tried checking the /logs page?

Yes, but there is nothing there…

What is the exact value you are using for the endpoint env var?

OK, I found a setting in Flexify.IO to set sub-domain mode. It is now working. :champagne: I’ll update the wiki!

Fouten bij het gebruik van aangepaste S3-opslag

Ondersteuning

Falco (Falco) 16 augustus 2021 om 15:04 3

You should try to follow the documentation on Using Object Storage for Uploads (S3 & Clones) for your use case. It’s a lot more flexible. When you get it working you can add it to the wiki too!

Topic		Antwoorden	Weergaven
Using Scaleway s3-compatible object storage Support	27	4074	6 april 2021
SSL_connect returned=1 errno=0 peeraddr=162.243.189.2:443 state=error: certificate verify failed (Hostname mismatch) Self-hosting s3	19	4490	9 januari 2024
What are the right settings to use S3 bucket (with non-Amazon URL)? Self-hosting	19	4970	25 augustus 2020
Setting DISCOURSE_S3_REGION: whatever no longer works Bug	2	80	7 november 2024
Failed to open TCP connection to <my-site>.s3.amazonaws.com:443 Support	7	5784	22 november 2019

Fouten bij het gebruik van aangepaste S3-opslag

Gerelateerde topics