The backup is failing again and again. Here’s the log: SSL_connect returned=1 errno=0 state=error: certificate verify failed (ok) /usr/local/lib/ruby/2.5.0/net/protocol.rb:44:in `connect_nonblock' /usr/local/lib/ruby/2.5.0/net/protocol.rb:44:in `ssl_socket_connect' /usr/local/lib/ruby/2.5.0/net/ht…

@pfaffman That commit basically broke my minio discourse s3 backup today after upgrading to the latest (2.3.0-beta6). The following resolved it after spending 2 hours fixing it: Add a DNS entry for your backup-bucket-name.backup.example.com. Add a MINIO_DOMAIN environment variable to your /etc/def…

[图片] hosna: SSL_connect returned=1 errno=0 state=error: certificate verify failed (ok) Something is wrong with your HTTPS.

I’m using lets encrypt for https and it seems its working fine. btw my backups is integrated with a minio server. The minio server is also https and seems to be fine too. Maybe a recent change to backup to minio script is breaking it? :thinking: Cause I have two instances and the one that is not y…

The certificate presented by the Minio server isn’t trusted by the Discourse server. This is usually a missing intermediate certificate or something like that. I suggest testing the certificate of the Minio server in a service like SSL Server Test: meta.discourse.org (Powered by Qualys SSL Labs)

I cant find anything wrong with the backup server. https://www.ssllabs.com/ssltest/analyze.html?d=m2.res.zabanshenas.com As I told my second instance is correctly uploading the backup to the same minio server. Any idea?

Are both Discourses running the same version?

[图片] hosna: SSL_connect returned=1 errno=0 state=error: certificate verify failed (ok) /usr/local/lib/ruby/2.5.0/net/protocol.rb:44:in `connect_nonblock' /usr/local/lib/ruby/2.5.0/net/protocol.rb:44:in `ssl_socket_connect' /usr/local/lib/ruby/2.5.0/net/http.rb:981:in `connect' /usr/local/lib/…

[图片] supermathie: If you run awscli commands from inside the container against Minio, do they work or fail with a cert error? can you tell me how can I do this?

Try rebuilding your Discourse container. It seems to be quite old. git pull ./launcher rebuild app You can also check if the connection to the server works by running the following in the container: openssl s_client -connect m2.res.zabanshenas.com:443 But please note that we do not test Discours…

It seems to me the output is ok cd /var/discourse [root@test discourse]# ./launcher enter app which: no docker.io in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) root@test-app:/var/www/discourse# openssl s_client -connect m2.res.zabanshenas.com:443 CONNECTED(00000003) depth=2 O = D…

The error that you’re seeing doesn’t look like it but DEV: Remove SiteSetting.s3_force_path_style (#7210) committed 01:58PM - 20 Mar 19 UTC (UTC) [图片] rishabhnambiar …

备份因 HTTPS 错误而失败

支持

hosna (hosna) 2019 年4 月 1 日 18:43 21

Thank you very much for your help. So I suppose after update, I should be able to use minio for my upload files too and fix my problem

3 个赞

Has anyone succeed in use minio for upload files?

话题		回复	浏览量
Unable to backup to custom s3 endpoint due to https certificate error Self-hosting backups , s3	7	1185	2020 年7 月 30 日
Has anyone succeed in use minio for upload files? Support	7	1273	2019 年11 月 12 日
Forum rendered unusable Self-hosting s3	10	885	2023 年9 月 4 日
Error in rebuilding using minio as object store Support	9	3635	2022 年10 月 4 日
Help restoring - system hung at midnight Self-hosting	26	2438	2022 年6 月 13 日

备份因 HTTPS 错误而失败

相关话题