Connection is not private for half of my sites in different environments
bitcoindevelopment
PROOP

14 days ago

Your connection is not private

Attackers might be trying to steal your information from X (for example, passwords, messages or credit cards). Learn more about this warning

net::ERR_CERT_COMMON_NAME_INVALID

Turn on enhanced protection to get Chrome's highest level of security.

Some of my sites are fine, some look like they are being attacked? What is going on. My sites are entirely knocked offline. I've tried setting up the domain again but same issue.

Solved$20 Bounty

2 Replies

Railway
BOT

14 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 14 days ago


bitcoindevelopment
PROOP

13 days ago

NET::ERR_CERT_COMMON_NAME_INVALID

I investigated the SSL configuration and confirmed that the server is presenting a valid Let's Encrypt certificate. However, the certificate currently appears to be issued only for the wildcard domain (*.X.com) and not for the root domain (X.com).

As a result, connections to the root domain are being rejected by browsers even though the certificate itself is valid.

This issue did not exist previously and appears to have been introduced following recent platform changes or modifications to the certificate provisioning process. I have attempted to recreate domains and certificates, but the problem persists.

Given that multiple sites have been affected simultaneously, this appears to be a platform-level issue rather than an isolated configuration problem.

Status.railway is saying no issues, i've tried everything to get multiple sites working again with no progress.


bitcoindevelopment

NET::ERR_CERT_COMMON_NAME_INVALID I investigated the SSL configuration and confirmed that the server is presenting a valid Let's Encrypt certificate. However, the certificate currently appears to be issued only for the wildcard domain (*.X.com) and not for the root domain (X.com). As a result, connections to the root domain are being rejected by browsers even though the certificate itself is valid. This issue did not exist previously and appears to have been introduced following recent platform changes or modifications to the certificate provisioning process. I have attempted to recreate domains and certificates, but the problem persists. Given that multiple sites have been affected simultaneously, this appears to be a platform-level issue rather than an isolated configuration problem. Status.railway is saying no issues, i've tried everything to get multiple sites working again with no progress.

13 days ago

Hey, do you have Cloudflare set up on your domain? We’ve seen reports of Cloudflare blocking certificates from being generated or renewed.

And lastly, would you mind sharing your domain here so I can do some basic checks to see if everything is set up correctly?


Status changed to Solved bitcoindevelopment 13 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...