The user configured StackPath CDN for their Discourse forum, setting up DNS records and updating app.yml with DISCOURSE_CDN_URL: https://www.unicyclist.com. This resulted in SSL errors (ERR_CERT_COMMON_NAME_INVALID) and a 503 error. The community clarified that the CDN URL should be the actual StackPath edge address (f5i4i8k5.stackpathcdn.com), not the site domain. The user also needed to create a custom certificate for the CDN’s delivery domain in StackPath, as the default certificate was for *.ssl.hwcdn.net, not their domain. After adjusting the CDN URL and creating the custom certificate, the issue was resolved. Canapin followed the Discourse CDN guide but misunderstood the CDN URL configuration, which was clarified by Falco, Stephen, and RGJ.
So you have a VPS running on 151.139.128.10, a DNS entry for unicyclist.com of type A pointing to 151.139.128.10 and your app.yml hostname is set to unicyclist.com ?
The CNAME , which is the “friendly” name for your CDN that you’ll set up in your DNS, e.g. discourse-cdn.example.com
The CDN URL , which is the “unfriendly” name for where the cached CDN assets will be coming from via the CDN’s worldwide network of distributed servers. It will look like 637763234.cdn-provider.com
Stackpath told me to add this in my DNS (the screenshot is from my stackpath configuration steps):
So I don’t quite understand why I should set the “unfriendly” name in my app.yml when the howto tell me the opposite.
As for the IP and domains:
My VPS IP is 95.217.21.71.
The A entry that I added following stackpath’s configuration steps is their own IP (as I understand it).
My app.yml hostname is unicyclist.com.