@David and @Angus recently created this post that helped solve an issue we had exporting my site’s admin-created theme . After updating, we have another substantial problem, now no one can access posts or PMs at https://forum.ackerlygreen.com . You can see the number of posts, but you’re automaticall…

Yes, just add https: to the beginning

Have you specified DISCOURSE_CDN_URL in your app.yml file? If so, make sure it has a protocol at the beginning (e.g. https://)

The visible error on your forum is caused by the retort plugin. Once you manage to successfully rebuild, it should be fixed [image] Retort - a reaction-style plugin for Discourse plugin I’ve just pushed a fix which removes _.contains from the repo, so this should start wo…

Thank you @David . Much appreciated.

@david , I’m so out of my depth here, but this is what the CDN url looks like in my app.yml: Should it be an absolute url as mentioned in your above response?

Thanks so much, the forum’s up and running again.

Aborting! CDN must have a protocol specified

Support

david (David Taylor) May 20, 2019, 12:35pm 3

The visible error on your forum is caused by the retort plugin. Once you manage to successfully rebuild, it should be fixed

4 Likes

Topic		Replies	Views
DISCOURSE_CDN_URL breaks rebuild/restore Support	10	1093	February 19, 2024
Remove DISCOURSE_CDN_URL Self-hosting cdn	3	461	April 15, 2020
Enable a CDN for your Discourse Self-Hosting cdn , configuring , how-to	72	294002	October 4, 2025
Aborting! Domain is not configured! Self-hosting	3	649	June 19, 2022
Forum not working after configuring CDN (ERR_CERT_COMMON_NAME_INVALID) Support cdn	7	1664	October 23, 2020

Aborting! CDN must have a protocol specified

Related topics