SSL_connect retourné=1 errno=0 peeraddr=162.243.189.2:443 état=erreur : vérification du certificat échouée (Incompatibilité de nom d'hôte)

DavidO · Juin 29, 2023, 2:48

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

Sujet		Réponses	Vues
Configure an S3 compatible object storage provider for uploads Self-Hosting cdn , configuring , how-to , reference	259	42227	Juillet 23, 2025
Set up file and image uploads to S3 Self-Hosting configuring , how-to	34	118721	Août 8, 2025
Extend S3 configuration for other S3 API compatible services Feature	57	6292	Avril 22, 2020
What are the right settings to use S3 bucket (with non-Amazon URL)? Installation	19	4746	Août 25, 2020
Migrate_to_s3 for Digital Ocean Spaces woes Installation s3	26	3161	Avril 27, 2019

SSL_connect retourné=1 errno=0 peeraddr=162.243.189.2:443 état=erreur : vérification du certificat échouée (Incompatibilité de nom d'hôte)

Sujets connexes