Custom domain and Redirect not working

Hi, how are you? I am having a problem. My custom domain and redirect are not working despite configuring them. My site doesn’t show. Here are the links. https//:owlsectechnologies.netlify.com and https://owlsectechnologies.co.ke.
Kindly help me. The new domain doesn’t work and the netlify.com domain doesn’t redirect to the new domain. I have already set up a redirect file in the root of my website in Github.
I will appreciate.

Hi Stephen,

Seems to work well to me - I can browse the site just fine at owlsectechnologies.co.ke.

The netlify domain won’t redirect to the custom domain unless you configure it to. You can see advice on how to do it in our UI:

https://app.netlify.com/sites/owlsectechnologies/settings/domain#custom-domains

and then click the chevron to expose the configuration you need:

Hi @fool,

I am having similar issue. My custom domain(www.yoursimplify.ng) which is setup as primary,work just fine. However this: yoursimplify.ng doesn’t redirect to www.yoursimplify.com even though both are shown as verified on netfilfy DNS.

Appreciate any help on what to do.

Hi @oliverdejohnson! Welcome to netlify community.

I see you have yoursimplify.ng set up on one site, and yoursimplify.com set up on another site. But I don’t see a redirect set up from one site to the other. Can you point me to where this redirect is set up? Thanks!

Hi

I have somewhat similar problem. My Netifly domain is working fine but my custom domain is not opening.

Thanks.

we would need to know which custom domain and which netlify site you are referring to, @vaibhiarora03!

the custom domain is www.surheal.com
netlify site is vigilant-cori-817fab.netlify.app

the netlify domain is mentioned as default sub-domain
surheal.com is mentioned as primary domain.
www.surheal.com is mentioned as Redirects automatically to primary domain

around 2 weeks back this thing was working perfectly as it was the first time I integrated it. now all of a sudden the name servers were changed in the dns setting of my domain. I don’t know why that happened.

After making those changes again the nelify domain was working but the custom domain was not working.

My custom domain vendor is godaddy.

Hi I am having the same issue. My primary domain is waiyanmyothet.me and my subdomain is https://waiyanmyothet.netlify.app/. It shows NetlifyDNS and HTTPS enabled.
I appreciate any help.
Thank you.

Works for me, @WaiyanMyothet. Can you confirm that all is well?

Remember, y’all: :mage: propagation :woman_mage:!

Thank you, it worked when I tried with VPN. May be I still need to wait to be fully working.

Propagation can take a little while. If it’s still problematic in several hours, we can take a further look :slight_smile:

Is the problem solved? Because I have the same trouble at this time.

Wait I must be missing something very simple but I’ve been troubleshooting for 24 hours with no luck. I am trying to get my redirects (which work for my primary subdomain) to also work for my custom subdomain.

I have a static website on a github repo:


In my website’s github repository I created a _redirects file in my root folder that contains:

#checking if redirects work at all, with dummy-tester redirects 
*/testing_mapbox        https://www.mapbox.com
*/testing_yahoo      https://yahoo.com

#Eventually I want to redirect tucsonpathways.org/map to my 2nd app at frosty-heisenberg
/map/* https://frosty-heisenberg-cf3b94.netlify.app/map/:splat 200!

Redirects do work for default domain https://suspicious-villani-7f8462.netlify.app/testing_yahoo
But do not work for the custom domain https://tucsonpathways.org/testing_yahoo

@fool you say:

*The netlify domain won’t redirect to the custom domain unless you configure it to.

So in addition to setting up the _redirects file, I need to “enable” redirects for custom domains… Where? I cannot find in https://app.netlify.com/sites/suspicious-villani-7f8462/settings/domain#custom-domains where you allow redirects for custom domains…

Sorry I’m sure this is a bonehead error, but I’m kind of a bonehead developer!
Cheers,
Dylan

Hi, @Dylansc22. It appears you found a solution as the redirect above is working when I test now:

$ curl -svo /dev/null https://tucsonpathways.org/testing_yahoo  2>&1 | egrep '< (HTTP|location)'
< HTTP/2 301
< location: https://yahoo.com/

If you have the time (and are so inclined), would mind sharing the solution which worked for you?

Also, if it still doesn’t work for you, please let us know.

If you have the time (and are so inclined), would mind sharing the solution which worked for you?

What I did was I went to sleep, and woke up later… Now it works!.. Hah. I swear custom domain redirects weren’t working when I tested last night:

  • in chrome browser
  • in chrome after clearing cache
  • in chrome private browsing
  • I did not test in curl

Do redirects somehow take time to propagate to custom domains? (for example, similar to how ssl certificates can take time to propagate?)

Hi, @Dylansc22. Thanks for the follow-up and I’m in the same boat. Meaning, without more information about what was happening at the time, all I can do is give a “best guess”.

There isn’t a delay for the redirect rules themselves. However, there are delays in changes to DNS records (universally with DNS, the TTL applies - this isn’t something Netlify specific):

It is possible that the redirects were not working because the DNS itself had not yet updated. This would mean the traffic wasn’t sent to Netlify. If that is the case, our redirects don’t apply because the site isn’t being hosted by us until the DNS propagation is complete.

Again, this is only a guess as I don’t have the information required to say for certain. We do appreciate the follow-up and please feel free to create new topics here anytime. :+1:

Good morning, afternoon or evening!

I am trying to set up a Let’s encrypt ssl certificate to my site: mauriciogs.com, I go to Domain management > HTTPS, I click on Verify DNS configuration, it says that DNS verification was successful, however, when I click the Provision certificate button I get the following error:

We could not provision a Let’s Encrypt certificate for your custom domain.

The strange thing is that I bought the custom domain from Netlify directly, so all the configuration was done automatically, can somebody help me with this?

Thanks!

It is possible that the redirects were not working because the DNS itself had not yet updated. This would mean the traffic wasn’t sent to Netlify. If that is the case, our redirects don’t apply because the site isn’t being hosted by us until the DNS propagation is complete.

Very informative and good to know. This seems like the most reasonable explanation since it did self-solve by just testing the following day - hopefully an edge-case few others will deal with!

2 Likes