Custom Subdomain Not working (Configuration CNAMe and TXT shows green in glide)

Hi Guys,

I have a domain cultosglobal.io which is in name cheap

I am trying to create subdomain app.cultosglobal.io and host my app in it.

Here are screenshots of my configuration on glide

Here is my config on Namecheap

This is the error I am getting


Has anyone else faced this? Can you please guide me as to how can I resolve this?

Regards,
Dilip

Give it some time. DNS changes can take a while to propagate.
I can see that it is already resolving from here, although there is an SSL error. That is normal, SSL takes a little longer.

1 Like

Hi @Darren_Murphy

Thank you for replying. Is it because it is from Namecheap it takes time?

I used clod flare before and it was pretty quick

I will wait for sometime as suggested.

Thank you for replying.

Regards,
Dilip

Hi @Darren_Murphy ,

I dont see it working. It’s still showing the same error message.

I tried changing it from app to product. i.e. product.cultosglobal.io

But its still giving same error message.

Any ideas on how I can move around this issue? It shouldn’t take more than 12 hours right?

Thank you for your help.
Regards,
Dilip

If you change it, then the whole DNS propagation process starts again.

But yes, I noticed last night that something isn’t right. The error suggests something wrong on the hosting provider side. I would suggest reaching out to their support.

Everything is correctly configured in Glide, based on the screen shots you shared.

Hi @Darren_Murphy ,

Thank you for replying. I did reach out to Namecheap support this morning.

They said that its propagated from thier end properly and its some issue to do with Glide side.

I was planning on launching this tomorrow, so kind of stuck right now.

Wondering what can be my next step to get it resolved fast?

Regards,
Dilip

You can try reaching out to Glide Support. Maybe they’ll see something that I missed.

Hi @Darren_Murphy ,

Thank you for suggesting. I wrote to them, They suggested trying it by changing app → to something else.

But its the same.

They asked me for this

" Add https:// or http:// in front of the subdomain URL and reconfigure the custom domain settings in Glide"

I am not quite sure I understand what they mean by this.

As I didnt get any replies after this.

Thank you for replying to me.

Regards,
Dilip

That just means you should use https://product.cultosglobal.io/

Right now, it is resolving correctly:

$ host product.cultosglobal.io
product.cultosglobal.io is an alias for custom.glideapps.com.
custom.glideapps.com is an alias for edge-proxy.glideapp.io.cdn.cloudflare.net.
edge-proxy.glideapp.io.cdn.cloudflare.net has address 104.16.218.83
edge-proxy.glideapp.io.cdn.cloudflare.net has address 104.16.219.83
edge-proxy.glideapp.io.cdn.cloudflare.net has IPv6 address 2606:4700::6810:da53
edge-proxy.glideapp.io.cdn.cloudflare.net has IPv6 address 2606:4700::6810:db53

But it is giving an SSL error, which again is normal if it was recently changed.

Normally you would see the above error for a short while and then it would start working.
If it doesn’t in this case, I really have nothing more to suggest, sorry.

Hi @Darren_Murphy ,

Had a long chat with Namecheap team.

They are saying

I have checked it with my team as well, the destination “custom.glideapps.com” itself is showing the error, so the error is on the service provider’s end.

Could you please ask them why custom.glideapps.com is showing the error?

Have you are anyone else done custom subdomain config before ?

And faced similar issue?

Regards,
Dilip

Hi @Darren_Murphy ,

Got reply from head of glide support.

He just said issue is escalated and its an issue from Glide end and they are looking into it.

Regards,
Dilip

Hi Guys,

Just an Update. @Marcel_at_Glide from glide support escalated it to Glide support team and got it resolved for me.

I followed the same step as mentioned in the glide documentation and it worked.

Thank you for helping out @Darren_Murphy
Regards,
Dilip

1 Like

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