K11 Testing Subdomain Error

Bonny Parker-Davies asked on June 6, 2019 11:32

We are preparing to launch our new K11 site but want to test it working with CloudFlare using a test subdomain. We have added the testing subdomain URL to the domain aliases and added the licence for the testing subdomain.

We have then updated the settings within CloudFlare but when we attempt to access the URL we encounter the following error message:

Either the website is stopped or the requested domain name is not configured for any website: https://wwwtest.basware.com:443/If you're an administrator of this site, you need to go to Sites and make sure the following domain name is configured either in the site properties or a domain alias of a running web site: wwwtest.basware.com:443

What do we need to do to correct this? I have checked and the testing subdomain is set up in exactly the same way as other domain aliases.

kentico 11 sub domain domain alias

Correct Answer

Bonny Parker-Davies answered on July 9, 2019 11:36

Just to close this off in case anyone else was having the same problem. I have now been able to correct this by logging into admin of the wwwtest domain rather than try to make these changes from the original. Once in there, all I need to do was then begin to 'run' the wwwtest site in the Sites app.

0 votesVote for this answer Unmark Correct answer

Recent Answers

Zach Perry answered on June 6, 2019 17:01

Did you verify the site is actually running in the Sites app?

0 votesVote for this answer Mark as a Correct answer

Bonny Parker-Davies answered on June 6, 2019 17:12

I've checked in Sites and the main domain is showing as 'Running'.

0 votesVote for this answer Mark as a Correct answer

David te Kloese answered on June 6, 2019 20:19

check the culture for the domain alias. It should match the main culture you use

check if it's not cloud flare cache (you could clear it in the CF admin)

If all seems fine I'd say try bypassing CF using your local hosts-file to see if the issue is Kentico side or CF.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on June 6, 2019 20:49

Kentico sees any domain with a port after it as a specific domain. So add the alias of wwwtest.basware.com:443 to your domain's aliases.

0 votesVote for this answer Mark as a Correct answer

Bonny Parker-Davies answered on June 7, 2019 13:18

Thanks for the responses so far. Here is what we have tried:

Adding port name to the end of the domain alias
Checking CF settings
Purging CF cache
Setting visitor culture to the same as the main domain (it was previously set to automatic)
Checked proxy, internal network and firewall settings

None of the above has resolved the issue. I am now just waiting on a response from my hosting team to see if the bindings set in the same way on the IIS for all the domain names.

If we wanted to narrow down whether this is a CF or Kentico issue, how do we bypass CF? Sorry, this must seem v basic to some but I am completely outside of my comfort zone on this one!!

0 votesVote for this answer Mark as a Correct answer