Issue Description:

I have a custom domain configured in Railway (pediahora.com) that works correctly when I access it with www.pediahora.com, showing a secure HTTPS connection.

However, when I access directly to pediahora.com (without www), the browser shows the error "pediahora.com does not support a secure connection" and HTTPS connection is not established.

Error message:

- "pediahora.com does not support a secure connection with https"

What I need:

- Configure the root domain (pediahora.com without www) to also work with HTTPS securely

- Or automatically redirect from pediahora.com to www.pediahora.com

Current configuration:

- www.pediahora.com works correctly with HTTPS

- pediahora.com (root domain) does not establish secure connection

How can I configure Railway so that both versions of the domain (with and without www) work with HTTPS?

Additional Information:

I have already configured all DNS records in GoDaddy exactly as Railway requested when adding the custom domain:

- All DNS settings are properly configured according to Railway's requirements

- DNS records have been set up and verified in GoDaddy

I have also implemented domain forwarding in GoDaddy:

- Set up forwarding from pediahora.com to www.pediahora.com

- Configured the forwarding option in GoDaddy settings

Despite these configurations, the issue persists:

- I have waited for days and even months for DNS propagation

- The forwarding has never worked properly

- www.pediahora.com continues to work with HTTPS, but pediahora.com (root domain) still shows the insecure connection error

Is there something else I need to configure in Railway or GoDaddy to make this work?