643b4069-cb2f-48ee-ba57-2b6401361d71

Please share the domain name.

Please attach screenshots of the domains in Railway and your dns setup in namecheap.

Please share the domain name.Please attach screenshots of the domains in Railway and your dns setup in namecheap.

Here are the screenshots, thanks for taking the ticket.

Looks like DNS has been setup correctly, this is looking like a route propagation delay that should resolve itself in ~20 minutes.

Railway is actively working on speeding up this progress.

Looks like DNS has been setup correctly, this is looking like a route propagation delay that should resolve itself in ~20 minutes.

Railway is actively working on speeding up this progress.

Hey, its been around a hour and the issue still persists. A heads up is I've had this issue for around 12+ hours now, I just decided to make a ticket this morning. The railway url is secure but the namecheap url isn't.

Have you tried removing and re-addiing the domain?

Have you tried removing and re-addiing the domain?

Yes I did that about a hour before I made the thread.

Approaching 24 hours of this issue still persisting. I tried re-adding twice in total. It is on setup complete but the domain is not secure while the railway given url/domain is secure.

Do you have the edge proxy enabled? if not, try enabling it and report back in another 20 minutes.

Do you have the edge proxy enabled? if not, try enabling it and report back in another 20 minutes.

Its been around 20 minutes, the same issue persists even with this feature enabled.

Can confirm the issue persists, will bring in a team member.

https://revelation-roadmap.org/

Request ID: qBxlQ0rLSMazlsE3D95DQg_1654200396

Just one extra thought, have you tried to redeploy the service?

Just one extra thought, have you tried to redeploy the service?

No I did not prior to you mentioning it. Now that I removed the service and added a new one, I get a different issue while still having the insecure issue. I actually get a error message now on top of the insecure site

Okay, I have asked the applicable team member, they will join in when available.

Just to be clear, did you redeploy via the most recent deployment's 3-dot menu?

Just to be clear, did you redeploy via the most recent deployment's 3-dot menu?

I did not, I also can't seem to find what you are talking about. When you said redeploy I thought you was referring to deleting the service and reinstating it, similar to how I removed the DNS and the domain and re-added it.

Open your service, you will see a list of deployments, they will all have 3-dot menus, click the 3-dot menu and then click redeploy.

Open your service, you will see a list of deployments, they will all have 3-dot menus, click the 3-dot menu and then click redeploy.

Sorry for the late reply but I did redeploy. Is the issue of me not getting my SSL with failed deployments? I am getting a: "TypeError: fetch failed" ... "cause: Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: Host: revelation-roadmap.org. is not in the cert's altnames: DNS:*.up.railway.app" - This is a completely separate issue than the one I made, I was trying to fix it myself without having to make another thread but if the failed deployments is what makes the SSL not apply then should I make a separate thread for this issue to get fixed?

Your failed deployment does not have anything to do with the domain's SSL.

If you want to open a new thread that only focuses on the failed deployment you are more than welcome to!

Your failed deployment does not have anything to do with the domain's SSL.

Ah, then I have no idea. I did redeploy and re-add the domain many times.

I'm thinking that dash in the domain is causing issues, even though that's a valid character.

I'm thinking that dash in the domain is causing issues, even though that's a valid character.

I got it resolved, it wasn't railways fault at all. Apparently the domain got flagged and just today they suspended it. I got it unsuspended and now when you visit revelation-roadmap.org it is secure. Thanks for the help, have a nice day!

Ah, that would do it, glad you solved it!