Github Pages on 1&1 domain has weird behavior
I have a 1and1 domain and web server (kyleplo.com), and I want to link it with my Github Pages site (kyleplo.github.io). I followed the instructions on the Github Help website, and now it works on HTTP on Edge and Firefox, has security errors on HTTPS, and doesn't work at all on Chrome.
github web-hosting
asked Dec 28 '18 at 13:37
kyleplokyleplo
34
add a comment |
I have a 1and1 domain and web server (kyleplo.com), and I want to link it with my Github Pages site (kyleplo.github.io). I followed the instructions on the Github Help website, and now it works on HTTP on Edge and Firefox, has security errors on HTTPS, and doesn't work at all on Chrome.
github web-hosting
asked Dec 28 '18 at 13:37
kyleplokyleplo
34
3
What have you tried and what doesn't work?
– Sathyajith Bhat♦
Dec 28 '18 at 13:41
Never mind, I got it to work.
– kyleplo
Dec 28 '18 at 13:58
1
It'd be helpful if you could explain what you did in order to make it work. You can answer your own question using the button below your post. Please be as specific as possible. This way, others can benefit from your answer.
– slhck
Dec 28 '18 at 14:00
@SathyajithBhat Actually, I'm not sure if it's working. It loads fine on http in Firefox and Edge, but it gives security errors on https, and doesn't work on Chrome at all.
– kyleplo
Dec 28 '18 at 14:17
add a comment |
I have a 1and1 domain and web server (kyleplo.com), and I want to link it with my Github Pages site (kyleplo.github.io). I followed the instructions on the Github Help website, and now it works on HTTP on Edge and Firefox, has security errors on HTTPS, and doesn't work at all on Chrome.
github web-hosting
asked Dec 28 '18 at 13:37
kyleplokyleplo
34
I have a 1and1 domain and web server (kyleplo.com), and I want to link it with my Github Pages site (kyleplo.github.io). I followed the instructions on the Github Help website, and now it works on HTTP on Edge and Firefox, has security errors on HTTPS, and doesn't work at all on Chrome.
github web-hosting
github web-hosting
asked Dec 28 '18 at 13:37
kyleplokyleplo
34
asked Dec 28 '18 at 13:37
kyleplokyleplo
34
edited Dec 28 '18 at 14:20
kyleplo
asked Dec 28 '18 at 13:37
kyleplokyleplo
34
asked Dec 28 '18 at 13:37
kyleplokyleplo
34
asked Dec 28 '18 at 13:37
kyleplokyleplo
34
34
3
What have you tried and what doesn't work?
– Sathyajith Bhat♦
Dec 28 '18 at 13:41
Never mind, I got it to work.
– kyleplo
Dec 28 '18 at 13:58
1
It'd be helpful if you could explain what you did in order to make it work. You can answer your own question using the button below your post. Please be as specific as possible. This way, others can benefit from your answer.
– slhck
Dec 28 '18 at 14:00
@SathyajithBhat Actually, I'm not sure if it's working. It loads fine on http in Firefox and Edge, but it gives security errors on https, and doesn't work on Chrome at all.
– kyleplo
Dec 28 '18 at 14:17
add a comment |
3
What have you tried and what doesn't work?
– Sathyajith Bhat♦
Dec 28 '18 at 13:41
Never mind, I got it to work.
– kyleplo
Dec 28 '18 at 13:58
1
It'd be helpful if you could explain what you did in order to make it work. You can answer your own question using the button below your post. Please be as specific as possible. This way, others can benefit from your answer.
– slhck
Dec 28 '18 at 14:00
@SathyajithBhat Actually, I'm not sure if it's working. It loads fine on http in Firefox and Edge, but it gives security errors on https, and doesn't work on Chrome at all.
– kyleplo
Dec 28 '18 at 14:17
3
3
What have you tried and what doesn't work?
– Sathyajith Bhat♦
Dec 28 '18 at 13:41
What have you tried and what doesn't work?
– Sathyajith Bhat♦
Dec 28 '18 at 13:41
Never mind, I got it to work.
– kyleplo
Dec 28 '18 at 13:58
Never mind, I got it to work.
– kyleplo
Dec 28 '18 at 13:58
1
1
It'd be helpful if you could explain what you did in order to make it work. You can answer your own question using the button below your post. Please be as specific as possible. This way, others can benefit from your answer.
– slhck
Dec 28 '18 at 14:00
It'd be helpful if you could explain what you did in order to make it work. You can answer your own question using the button below your post. Please be as specific as possible. This way, others can benefit from your answer.
– slhck
Dec 28 '18 at 14:00
@SathyajithBhat Actually, I'm not sure if it's working. It loads fine on http in Firefox and Edge, but it gives security errors on https, and doesn't work on Chrome at all.
– kyleplo
Dec 28 '18 at 14:17
@SathyajithBhat Actually, I'm not sure if it's working. It loads fine on http in Firefox and Edge, but it gives security errors on https, and doesn't work on Chrome at all.
– kyleplo
Dec 28 '18 at 14:17
add a comment |
1 Answer
1
active
oldest
votes
A quick look at the HTTP troubleshooting steps from Github suggests that you need to remove and re-add the domain in order to trigger HTTPS:
It can take up to an hour for your GitHub Pages site to become available over HTTPS after you add and correctly configure your custom domain. After updating existing DNS settings, you may need to remove and re-add your custom domain to your GitHub account to trigger the process of enabling HTTPS.
By the looks of things, you've forwarded the A record correctly, but haven't taken this additional step, so the SAN entries on the certificate are just for the generic pages www.github.com, *.github.io, *.githubusercontent.com, *.github.com, github.com, github.io, githubusercontent.com hence the SSL error.
I would go back and double check you have followed this process.
answered Dec 28 '18 at 14:57
v25v25
1562
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388451%2fgithub-pages-on-11-domain-has-weird-behavior%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
A quick look at the HTTP troubleshooting steps from Github suggests that you need to remove and re-add the domain in order to trigger HTTPS:
It can take up to an hour for your GitHub Pages site to become available over HTTPS after you add and correctly configure your custom domain. After updating existing DNS settings, you may need to remove and re-add your custom domain to your GitHub account to trigger the process of enabling HTTPS.
By the looks of things, you've forwarded the A record correctly, but haven't taken this additional step, so the SAN entries on the certificate are just for the generic pages www.github.com, *.github.io, *.githubusercontent.com, *.github.com, github.com, github.io, githubusercontent.com hence the SSL error.
I would go back and double check you have followed this process.
answered Dec 28 '18 at 14:57
v25v25
1562
add a comment |
A quick look at the HTTP troubleshooting steps from Github suggests that you need to remove and re-add the domain in order to trigger HTTPS:
It can take up to an hour for your GitHub Pages site to become available over HTTPS after you add and correctly configure your custom domain. After updating existing DNS settings, you may need to remove and re-add your custom domain to your GitHub account to trigger the process of enabling HTTPS.
By the looks of things, you've forwarded the A record correctly, but haven't taken this additional step, so the SAN entries on the certificate are just for the generic pages www.github.com, *.github.io, *.githubusercontent.com, *.github.com, github.com, github.io, githubusercontent.com hence the SSL error.
I would go back and double check you have followed this process.
answered Dec 28 '18 at 14:57
v25v25
1562
add a comment |
A quick look at the HTTP troubleshooting steps from Github suggests that you need to remove and re-add the domain in order to trigger HTTPS:
It can take up to an hour for your GitHub Pages site to become available over HTTPS after you add and correctly configure your custom domain. After updating existing DNS settings, you may need to remove and re-add your custom domain to your GitHub account to trigger the process of enabling HTTPS.
By the looks of things, you've forwarded the A record correctly, but haven't taken this additional step, so the SAN entries on the certificate are just for the generic pages www.github.com, *.github.io, *.githubusercontent.com, *.github.com, github.com, github.io, githubusercontent.com hence the SSL error.
I would go back and double check you have followed this process.
answered Dec 28 '18 at 14:57
v25v25
1562
A quick look at the HTTP troubleshooting steps from Github suggests that you need to remove and re-add the domain in order to trigger HTTPS:
It can take up to an hour for your GitHub Pages site to become available over HTTPS after you add and correctly configure your custom domain. After updating existing DNS settings, you may need to remove and re-add your custom domain to your GitHub account to trigger the process of enabling HTTPS.
By the looks of things, you've forwarded the A record correctly, but haven't taken this additional step, so the SAN entries on the certificate are just for the generic pages www.github.com, *.github.io, *.githubusercontent.com, *.github.com, github.com, github.io, githubusercontent.com hence the SSL error.
I would go back and double check you have followed this process.
answered Dec 28 '18 at 14:57
v25v25
1562
answered Dec 28 '18 at 14:57
v25v25
1562
answered Dec 28 '18 at 14:57
v25v25
1562
answered Dec 28 '18 at 14:57
v25v25
1562
1562
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388451%2fgithub-pages-on-11-domain-has-weird-behavior%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
What have you tried and what doesn't work?
– Sathyajith Bhat♦
Dec 28 '18 at 13:41
Never mind, I got it to work.
– kyleplo
Dec 28 '18 at 13:58
1
It'd be helpful if you could explain what you did in order to make it work. You can answer your own question using the button below your post. Please be as specific as possible. This way, others can benefit from your answer.
– slhck
Dec 28 '18 at 14:00
@SathyajithBhat Actually, I'm not sure if it's working. It loads fine on http in Firefox and Edge, but it gives security errors on https, and doesn't work on Chrome at all.
– kyleplo
Dec 28 '18 at 14:17