cname problem


#1

hi

I am opening cdn.domain.com while opening cname, but does it say forbid?


#2

What is saying Forbid? If it is the DNS settings page here, it might forbid you to :orange: your CNAME. Try :grey:.


#3

Or is it a 403 - forbidden when he tries to access cdn.domain.com? :thinking:


#4

hi

http://prntscr.com/jqrzf7


#5

You wrote “forbid” which is 403 :wink:

this 404 is delivered by your server which doesn’t know how to handle access to cdn.foo.bar or there’s no contenr or wrong redirect to a non-existing folder or…


#6

I dont understand?


#7

Wow, that is a lot of nested CNAMEs.

The server you’re using 1) Does not support HTTPS for your URL, and 2) Doesn’t know where your content is.

KeyCDN shouldn’t be this tough to set up. I’ve used it before and it’s pretty straightforward. First of all, it’s not normal to use a CDN with no file or path. There should be some sort of file in your URL. It also seems like KeyCDN doesn’t have HTTPS set up for your CNAME:


#8

hi

http://prntscr.com/jr0g4a

hi to get this cdn.finanspara.com url file?


#9

You don’t need to buy an SSL certificate. The one you already have at Cloudflare is ok.

Did you have cdn.finanspara.com set to :orange: on your DNS page?


#10

yes there is cdn.finanspara.com but it is not active due to ssl


#11

This topic was automatically closed after 14 days. New replies are no longer allowed.