I’m trying to setup S3 CDN, but when entering the app and rebaking, I get a large block of output following rake aborted! I am running discourse from the Digital Ocean Marketplace App (docker). Here is what outputs: ActiveRecord::NoDatabaseError: FATAL: Peer authentication failed for user "discou…

I ended up installing a new instance of the Digital Ocean provided docker environment to test and it still throws the same error. I would have to assume it’s something within the Digital Ocean droplet setup. Could someone help me figure this out?

We recommend installing following our Discourse official Standard Installation . Third party packages that are not maintained by us may break at any point, and as we don’t have any idea of how they are made we can’t offer any support for those.

I’m pretty sure Digital Ocean’s distribution pulls directly from the current source. They don’t customize anything afaik. They are even referenced in the GitHub official setup. Can you help me troubleshoot this issue? [image]

If you read that page further you will see that what we recommend is using Digital Ocean VPS running the current supported LTS release of Ubuntu Server and not their [afbeelding] alanman: Digital Ocean Marketplace App (docker). That said, if you want to debug further are you running it l…

The marketplace app is just a shortcut for spinning up a new droplet VPS with the discourse docker setup script running on login. It is running Ubuntu 20.04. It’s no different than a supported install afaik, just faster if you don’t already have a droplet setup. And, yes the commands and directorie…

You can try sharing the app.yml. My best guess is that the postgres template is missing?

Here is the app.yml file. I have hidden my hostnames and email addresses. ## this is the all-in-one, standalone Discourse Docker container template ## ## After making changes to this file, you MUST rebuild ## /var/discourse/launcher rebuild app ## ## BE *VERY* CAREFUL WHEN EDITING! ## YAML FILES AR…

[afbeelding] alanman: #DISCOURSE_CDN_URL: https://discour Uncomment that line and set the CDN url.

I am using the s3 CDN url set via the GUI. I found that enabling the CDN via app.yml setting would prevent the forum form loading.

I can’t imagine why setting the CDN in the ux could cause the error you show in the OP. I can’t imagine why setting the CDN in the yml file wouldn’t work. My best guess is that you have something wrong with the CDN and something wrong with your configuration. But I don’t know.

Kan niet opnieuw bakken na het instellen van CDN

Ondersteuning Installatie

pfaffman (Jay Pfaffman) 18 maart 2021 om 20:08 15

And make sure to see Configure an S3 compatible object storage provider for uploads and the after_assets_precompile stanza.

Topic		Antwoorden	Weergaven
Digital Ocean Spaces (S3) "unable to sign request without credentials set" Support uploads , backups , s3	19	383	7 januari 2026
Enable a CDN for your Discourse Self-Hosting cdn , configuring , how-to	72	294484	4 oktober 2025
Problems with Patreon Login, Force HTTPS, and S3 CDN (three) Issues Self-hosting unsupported-install	12	2119	6 januari 2023
Rebaking old posts won't pull new S3 CDN URL after S3 bucket rename Self-hosting	13	1909	12 januari 2021
Disable CDN causes old images with CDN URL can not be shown Support	4	2716	4 juni 2015

Kan niet opnieuw bakken na het instellen van CDN

Gerelateerde topics