Custom domains not working for some projects


This is what I see at the console:

curl -IL

HTTP/1.1 302 Found
Server: nginx
Date: Tue, 06 Nov 2018 20:22:40 GMT
Content-Type: text/plain; charset=utf-8
Connection: keep-alive
X-Served-By: Namecheap URL Forward

HTTP/2 200
date: Tue, 06 Nov 2018 20:22:40 GMT
content-type: text/html; charset=UTF-8
content-length: 4482
x-powered-by: Express
accept-ranges: bytes
cache-control: public, max-age=0
last-modified: Tue, 24 Jul 2018 00:00:21 GMT
etag: W/"1182-164c9963208"

In chrome I end up at


Yes, sorry, that’s an existing redirect I have. Sounds like I’ve muddied things here. Many of my custom domains redirect to Glitch apps like that, which is not the same as this new feature where I can make my custom domain the canonical URL, right?

But, first things first, what about my question about the URLs saying “Not Found”?


Ah yes, I see where I was confused. Yes, there is work underway to fix a bug that cropped up a few days ago. Some portions of the solution are in place but there’s more work yet to be done, so things aren’t quite where they need to be yet.

Thanks for your patience - hopefully the full fix will be in place soon!


Note that visiting the URL itself in the browser will display ‘Not Found’ - that’s to be expected. It’s not intended to be used directly, only as part of a CNAME.


I forget which one that is but I have a different one.



Hey my custom domains seem to be working now but if I try to access it says “no mount found”, but and work.


The full set of changes we expected to resolve the custom domain issues have been deployed and it looks like custom domains are coming back - not everyone’s is working yet but some definitely are.

@advaith1 are you seeing any errors in the logs when you access your custom domain’s /api/servers endpoint? Can you tell if the request is making it to your project at all? We’re taking a look to see what might be going on, but any information you can provide will be helpful.


Actually it looks like our partners over at have already issued a fix for that problem; @advaith1 your endpoint seems to be working correctly now.


Everything is working for me now! With one exception that’s probably not Glitch’s or’s fault but I’d be grateful to understand what it would take to fix this. For my MoleCall project I have the CNAME set up for to be the canonical name for, which is great, and I also have a redirect set up for the root domain so redirects to Also great. But there must be something else I need to do for SSL on the root domain because even though works and both and work, doesn’t work. It times out. (And similarly for other projects with analogous setups.)

Would using A records instead of CNAMEs solve that?


Hey @dreeves sorry you’re site is still having some trouble.

Here’s what I think is happening. resolves (eventually) to the / servers, which are serving up an appropriate SSL certificate for, so that all works as expected. However itself, where the redirect to takes place, is being served by a Namecheap server (based both on the results of a WHOIS lookup at and on the X-Served-By: Namecheap URL Forward header returned in a curl -IL request) which doesn’t have an SSL cert for (or at least isn’t responding on port 443). Therefore requests for time out.

Swapping the CNAME record at for an A record wouldn’t help; A records need to point to an IP address, and presumably if you pointed to (the ip where resides) then wouldn’t be able to resolve your custom domain to the right project (I expect that they use the host header of the incoming request to determine which application to serve, but that’s largely a guess).

My suspicion is that you need to make some changes in your Namecheap forwarder configuration to have them serve a valid SSL cert for if you want SSL to work at that address.

Hope that helps!