GitHub Community
-
|
Hi, I just switched my workflow to use Github Actions to deploy my website: wumbo.net, however when renaming the Github pages branch the settings > pages page shows that the TLS certificate is stuck showing an error. It looks like the old certificate is still valid when using HTTPS, but I really would like to enforce HTTPS only traffic. Is there anything that I can do other than waiting? Edit: Since my DNS was working right before changing my workflow and HTTPS was enforced, I am assuming that DNS is still configured correctly. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 7 replies
-
|
I used the pages health check tool today to see if I could get any more information on the TLS Certificate Error. Here is the output: Currently, in my DNS (Google Domains) configuration I am forwarding the subdomain |
Beta Was this translation helpful? Give feedback.
-
|
Update for those in a similar situation. Adding a You can trigger the TLS certificate process by temporarily removing your custom domain and adding it again. A couple minutes later I was able to check the “Enforce HTTPS” check box again. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @kurtbruns |
Beta Was this translation helpful? Give feedback.
-
|
So, I had a working portfolio site with a TLS cert before. However, I decided to create a new site using React/Next.js. I got everything up and running with my main and gh-pages branches merged. However, now I cannot seem to reuse my domain. The DNS check passes, but it errors when I am awaiting the TLS certificate. It has been well over 24 hours now and still nothing. Everything was setup correctly previously, so I don't know what's up this time around. |
Beta Was this translation helpful? Give feedback.
-
|
@travisengh @notsag-dev Any update regarding this? Im on the same boat :/ |
Beta Was this translation helpful? Give feedback.
-
|
So, what I ended up doing was deleting that repository, waiting about two days, and then creating a completely new repository to store my website on. It still took awhile, but it worked. I would also suggest self hosting your site through a cloudflare tunnel if you can. I recently containerized my website and did this on a raspberry pi docker swarm and will never look back. :) |
Beta Was this translation helpful? Give feedback.
-
|
@tronch0 it eventually worked for me. I believe I had to wait for more than an entire day, but I didn't recreate the repo. For the record, did it work for you already? |
Beta Was this translation helpful? Give feedback.
-
|
@travisengh @notsag-dev thanks for your inputs. I waiting for about 48h but still got the cert error, so I ended up changing the address I deployed to, instead of the regular address I used a subdomain to have a new address for the ssl certificate. *my project is a personal website so I was more lean with my address constraints. Thanks again! :) |
Beta Was this translation helpful? Give feedback.
-
|
I had waited over a week before I deleted and recreated the repository. It just wasn't working for me until I redid it all. Mine was for a portfolio website, so I wasn't in much of a rush. |
Beta Was this translation helpful? Give feedback.
-
|
What should i do to solver this problem in my windows 7 32bit laptop "The request was aborted: Could not create SSL/TLS secure channal" |
Beta Was this translation helpful? Give feedback.
Update for those in a similar situation. Adding a
wwwCNAME record fixed the error following the advice from this post. My DNS custom resource records section now looks like this:You can trigger the TLS certificate process by temporarily removing your custom domain and adding it again. A couple minutes later I was able to check the “Enforce HTTPS” check box again.