Getting ERR_SSL_PROTOCOL_ERROR

Website, Application, Performance DNS & Network
1

Hello! My domain was purchased on Google Domains and has been linked through Cloudflare for a couple of years now. It’s never had any issues.

I recently created a subdomain using a CNAME “podcast” in order to connect to Buzzsprout (a podcast site) as the Target. I have it set to DNS Only.

I checked the DNS propogation and it shows that it’s connected to the Buzzsprout Target.

However, I’m still getting ERR_SSL_PROTOCOL_ERROR when I type in “subdomain.rootdomain”

When I ran the site through the Cloudflare Diagnostic Center, it says that “The web server did not respond.” (Screenshot attached.)

I’ve contacted Buzzsprout multiple times and they assured me that everything is ok on their end, unless they are missing something.

Does anyone have any idea what might be missing?

Thank you in advance!

Screen Shot 2022-07-16 at 9.39.02 PM
Screen Shot 2022-07-16 at 9.39.02 PM1830×1418 198 KB

2

The actual domain name so we can offer some specific advice.

1 Like
3

Sure! No need for sass :slight_smile: As I was posting, it said that I couldn’t include links, so I took them all out. And even now, it’s still saying no links allowed.

podcast.kelliyoungmanwellness dot com

4

It’s #1 on this list of things to include (pinned to top of Community):

Makes it much easier to diagnose, so, thanks for figuring out a workaround for posting the hostname. :+1:

Right now, that hostname is not proxied by Cloudflare.

Shockingly, it’s on Caddy, yet does not work with TLS/SSL. “Shock”, because Caddy is so good at issuing certs.

I do see that it’s a CNAME that points to app.buzzsprout.com. If you can get them to fix your site’s TLS/SSL, that should go a long way toward fixing this problem.

5

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.