EDIT: Well, it took me 18 hours, but it seems that defining DISCOURSE_CDN_URL keeps (at least) this site from rebuilding and/or functioning after a restore. I guess the next thing to test is doing a build without DISCOURSE_CDN_URL and then cranking up the container with the ENV var set. What I knew…

@pfaffman I’ve just stumbled across this exact same issue after battling through my other problems when trying to set up S3. Did you ever find out what was causing this?

Fixed it. Make sure you prepend your CDN url with http:// :facepalm: So instead of DISCOURSE_CDN_URL=your-cdn-url.com it should be DISCOURSE_CDN_URL=http://your-cdn-url.com. Only 2 hours wasted debugging it :smiley:

Hmm can we add some kind of warning here @eviltrout so people don’t run into this in the future?

This will pop up a warning if you don’t add a protocol: https://github.com/discourse/discourse/commit/9ab2a15691de4c280e234be8d50b0526b657db83

But bozos (like me) who do this with ENV variables will still have trouble. Is there a downside to printing the warning and prepending https://?

GlobalSetting is the object that takes your ENV variables into Discourse, so if you do it that way the warning should also appear.

[图片] pfaffman: But bozos (like me) who do this with ENV variables I too feel pretty silly for falling into this trap! :laughing:

If I’m remembering correctly, I lost 18 hours on it during what was supposed to be a Christmas break. :frowning_face:

DISCOURSE_CDN_URL 导致重建/恢复失败

产品支持

eviltrout (Robin Ward) 2020 年3 月 5 日 20:38 5

如果您未添加协议，将弹出警告：

话题		回复	浏览量
Aborting! CDN must have a protocol specified Product Support	6	1085	2019 年5 月 20 日
Assets not serving from CDN in latest update Product Support	16	2047	2020 年2 月 7 日
Remove DISCOURSE_CDN_URL Self-hosting cdn	2	545	2020 年4 月 15 日
Cannot rebake after setting up CDN Self-hosting unsupported-install	17	1713	2021 年3 月 19 日
Rebaking old posts won't pull new S3 CDN URL after S3 bucket rename Self-hosting	13	2167	2021 年1 月 12 日

DISCOURSE_CDN_URL 导致重建/恢复失败

相关话题