a month ago
my https render is not working.
I have a www. DNS entry setup for my domain psalmoftheday.org and then have AWS S3 Bucket redirecting the root domain to the www.
The http://psalmoftheday.org is working just fine, but the https://psalmoftheday.org is not and I think it might be something on the backend of railway causign this to break.
The reason I am doing it this way is I cannot get a cname setup with a blank root within Route 53. so this is the work around.
Any help or guidance you can give me there?
1 Replies
a month ago
The issue with the https:// version of your domain is likely related to how Amazon S3 handles redirects and SSL/TLS certificates, not the backend of Railway. S3 static website endpoints do not natively support HTTPS with a custom domain unless you use another service like Amazon CloudFront or an Application Load Balancer (ALB)
I recommend AWS Amazon CloudFront in front of your S3 Bucket or pointing directly to your railway service.
Here are some steps to set one up:
Create a new CloudFront distribution.
Request a free SSL certificate for both psalmoftheday.org and www.psalmoftheday.org using AWS Certificate Manager (ACM) in the us-east-1 region (required for CloudFront).
Configure CloudFront: Set your S3 bucket or the Railway app's domain as the origin. Add your domain names (psalmoftheday.org and www.psalmoftheday.org) as Alternate Domain Names (CNAMEs) in the distribution settings. Configure the "Viewer Protocol Policy" to "Redirect HTTP to HTTPS" or "HTTPS Only".
Update Route 53: In your Route 53 hosted zone, change the DNS record for your root domain (psalmoftheday.org) to an Alias A record that points to the new CloudFront distribution's domain name.
This setup allows CloudFront to handle the SSL negotiation and the redirect, ensuring that HTTPS works correctly for both the root and www domains.
Status changed to Open brody • about 1 month ago