Skip to content
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

msemoji.js.org #8403

Closed
wants to merge 1 commit into from
Closed

msemoji.js.org #8403

wants to merge 1 commit into from

Conversation

DellZHackintosh
Copy link
Contributor

@DellZHackintosh DellZHackintosh changed the title Update cnames_active.js msemoji.js.org Jul 25, 2023
Copy link
Member

@MattIPv4 MattIPv4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi there!

❌ Before we can accept your domain request, you need to create a file named CNAME in the root of your github pages site (this may not be the root of your repository). 📝
This file should contain a single line with the full js.org domain you are requesting, in this instance msemoji.js.org.

@MattIPv4 MattIPv4 added the awaiting CNAME This PR is waiting for the target to add a CNAME file label Jul 25, 2023
@DellZHackintosh
Copy link
Contributor Author

Oops, is that means I should put CNAME into my site root instead of the project page root?
That seems strange.

@MattIPv4
Copy link
Member

Yeah, it should be at the root of wherever GitHub Pages is operating from. It looks like you've got that in place now, and GitHub isn't detecting it. You might want to check your repository settings and check the custom subdomain setting under the GitHub Pages settings.

@DellZHackintosh
Copy link
Contributor Author

I had already put CNAME into https://github.com/DellZHackintosh/msemoji/blob/gh-pages/CNAME, and also tried to update the custom subdomain setting (in my repository), but I got an error:

The custom domain `msemoji.js.org` is already taken. If you are the owner of this domain, check out https://docs.github.com/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages for information about how to verify and release this domain.

I had also looked through the GitHub Pages settings to verify domain, but I can't continue.
So...I don't know what to do next...


BTW, I visited msemoji.js.org before, but there is no doubt about it, http 302 error.

@MattIPv4
Copy link
Member

Ah, it is likely the case that another repository exists on GitHub that has that subdomain configured as it's custom domain for one reason or another. You can reach out to GitHub Support and they should be able to help you get it freed up so you can use it, as I agree we're not expecting it to be in use by anyone.

@DellZHackintosh
Copy link
Contributor Author

Alright...See you later.

@DellZHackintosh
Copy link
Contributor Author

I can't get anything useful help from Github Support now. I don't know how to negotiate with them. 😮‍💨

@MattIPv4
Copy link
Member

Unfortunately, we're not really able to help here. You, as the person wanting to use the subdomain, need to ask GitHub to allow you to do so. They normally provide a way to verify that the domain is yours, which we can assist with once you have that from them.

@DellZHackintosh
Copy link
Contributor Author

DellZHackintosh commented Jul 30, 2023

I'm sorry to hear that. This subdomain is truly not mine, it's belongs to js.org, isn't it?
I'm not able to verify that the subdomain is mine.

@DellZHackintosh
Copy link
Contributor Author

DellZHackintosh commented Jul 31, 2023

The result is I must verify the subdomain is mine by using the official way. I know it's impossible, but is that possible if I provide the DNS Record to you? And then maybe you can help to verify the subdomain, I mean maybe...


We're not in a position to stray from our standard domain verification and domain release procedure, and the process that js.org have set up is a special case on their end.

I can see you've reached out to the js.org team, if they can add the TXT DNS record that is provided to you during the domain verification process then I will be able to release the domain for you.

Let me know how you go with js.org adding the TXT record for you!

Roy
GitHub Support

@MattIPv4
Copy link
Member

Yup, once you have the verification steps from GitHub, we can assist with putting the record in place to confirm for them that we're expecting you to be able to use the subdomain.

@DellZHackintosh
Copy link
Contributor Author

DellZHackintosh commented Aug 3, 2023

Ok, here is:

  1. Create a TXT record in your DNS configuration for the following hostname:
    _github-pages-challenge-DellZHackintosh.msemoji.js.org
  2. Use this code for the value of the TXT record:
    8ca626f101f17ad48a6eabe0370278
  3. Wait until your DNS configuration changes. This could take up to 24 hours to propagate.

@MattIPv4
Copy link
Member

MattIPv4 commented Aug 3, 2023

@indus would you be able to get that added? ^

@indus
Copy link
Member

indus commented Aug 3, 2023

@MattIPv4 @DellZHackintosh I've just added the TXT record with the given key value pair

@DellZHackintosh
Copy link
Contributor Author

@MattIPv4 @indus Thanks! All things are solved! I'll open a new PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting CNAME This PR is waiting for the target to add a CNAME file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants