SSL_connect returned=1 errno=0 peeraddr=162.243.189.2:443 state=error: certificate verify failed (Hostname mismatch)

DavidO · June 29, 2023, 2:48am

OK. I got the after_assets_precompile added…

I rebuilt it and I still don’t see a section of S3.

Do I just make one?
Does it matter where I put the settings?

Configure an S3 compatible object storage provider for uploads

Example configuration:

  DISCOURSE_USE_S3: true
  DISCOURSE_S3_REGION: whatever
  DISCOURSE_S3_ENDPOINT: https://nyc3.digitaloceanspaces.com
  DISCOURSE_S3_ACCESS_KEY_ID: myaccesskey
  DISCOURSE_S3_SECRET_ACCESS_KEY: mysecretkey
  DISCOURSE_S3_CDN_URL: https://falcoland-files-cdn.falco.dev
  DISCOURSE_S3_BUCKET: falcoland-files
  DISCOURSE_S3_BACKUP_BUCKET: falcoland-files/backups
  DISCOURSE_BACKUP_LOCATION: s3
  DISCOURSE_S3_INSTALL_CORS_RULE: false

Topic		Replies	Views
Configure an S3 compatible object storage provider for uploads Self-Hosting cdn , configuring , how-to , reference	230	38775	October 24, 2024
Set up file and image uploads to S3 Self-Hosting configuring , how-to	23	116874	November 4, 2024
Defining DISCOURSE_S3_CDN_URL links to assets in S3 CDN URL Support	43	5869	April 22, 2020
Digital Ocean Spaces don’t implement the AWS S3 API for the CORS rule Installation cdn , s3	17	3405	April 30, 2020
Can't enable Uploads in Digital Ocean Spaces Support	4	1512	July 6, 2019

SSL_connect returned=1 errno=0 peeraddr=162.243.189.2:443 state=error: certificate verify failed (Hostname mismatch)

Related topics