-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable HTTPS on community website #4
Comments
I think now is done. Please @chris001 , could you test it? Thanks a lot, |
Yes this URL is working now @thekix thanks! https://imapfw.offlineimap.org/ |
Hi, the website is https://imapfwdoc.offlineimap.org/? Probably is https://github.com/OfflineIMAP/imapfw-documentation , but there are not info configured in the Pages section: GitHub Pages is currently disabled. How can I help? |
@nicolas33 is hosting this imapfw-documentation on https://gitbook.com It's different format from github pages, and a separate company from github. Someone with access, I guess Nicolas, has to login to gitbook and get the unique public URL of the docs, for the custom https://imapfwdoc.offlineimap.org to alias to. |
Enable HTTPS on the
imapfw
community web site is free. Someone with access to "Settings ⚙️" on this repo, @nicolas33 , could you do this:DNS
check begins. This check determines if ourDNS
settings are configured to allow GitHub to obtain a certificate automatically. If the check is successful, GitHub queues a job to request aTLS
certificate fromLet's Encrypt
. On receiving a valid certificate, GitHub automatically uploads it to the GitHub servers that handleTLS
termination for Pages. When this process completes successfully, a check mark is displayed beside your custom domain name.The process may take some time. If the process has not completed several minutes after you clicked Save for your custom domain name, try clicking Remove next to your custom domain name. Retype the domain name and click Save again. This will cancel and restart the
TLS
certificate provisioning process. WhenTLS
certificate provisioning is complete, theEnforce HTTPS
checkbox is accessible.5. Click to enable the checkbox
Enforce HTTPS
.The text was updated successfully, but these errors were encountered: