Replies: 5 comments
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
I want draw your attention towards an excellent opportunity which will diffidently help to improve in the sections like Licenses, SSL Certificate, IPv4/IPv6 addresses, Unlim shared hosting, SSD VPS, Windows VDS SSD/NVMe (KVM) and Servers across the World. Further details may be sought from https://prohoster.info |
Beta Was this translation helpful? Give feedback.
-
|
I want draw your attention towards an excellent opportunity which will diffidently help to improve in the sections like Licenses, SSL Certificate, IPv4/IPv6 addresses, Unlim shared hosting, SSD VPS, Windows VDS SSD/NVMe (KVM) and Servers across the World. Further details may be sought from https://prohoster.info/ |
Beta Was this translation helpful? Give feedback.
-
|
Hey, sounds like you’ve already done most of the right steps — this issue is usually related to how GitHub Pages handles SSL certificates for both the root and www domains. A couple of things you can check: In your GitHub Pages settings, make sure the custom domain is set to www.marleamartens.com (not the root) and HTTPS is enforced. Then, in your DNS, set a CNAME record for www → username.github.io and an ALIAS/A record for the root (@ → username.github.io). Remove any conflicting AAAA or old CNAME records. Finally, clear GitHub Pages’ cache by re-saving the custom domain, wait 10–15 minutes, and recheck via whatsmydns.net This mismatch often happens because GitHub auto-generates SSL only for the domain explicitly set in your Pages config. Once both records and the enforced HTTPS setting align, the certificate error should disappear. |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Hello!
I am experiencing issues with deploying my React app (using Vite) to GitHub Pages using a custom domain. My setup involves the domain marleamartens.com (with a www subdomain) but I'm facing multiple issues, including SSL errors (?) and connectivity problems.
I’ve done the DNS Configuration, and also ensured that there is no redirect domain record:
I also configured my custom domain to www.marleamartens.com and enabled Enforce HTTPS:
For https://www.marleamartens.com, I get an SSL warning (ERR_CERT_COMMON_NAME_INVALID), though SSL Checker shows valid certificates for both the root and www domain.
For https://marleamartens.com, I get ERR_CONNECTION_RESET.
I’ve verified DNS propagation using various tools (shows correct IPs and SSL certificates) and have also waited ~12 hours for DNS propagation (still seeing errors).
I was thinking maybe it has something to do with my Vite config, but as far as I can tell, I think everything is fine:
<Router> <Routes> <Route path="/" element={ <div> …Any guidance or suggestions to fix the issues would be greatly appreciated! This is my first time using a custom domain, I’ve been stuck for days :,)
Beta Was this translation helpful? Give feedback.
All reactions