ドキュメントには頻繁に更新が加えられ、その都度公開されています。本ページの翻訳はまだ未完成な部分があることをご了承ください。最新の情報については、英語のドキュメンテーションをご参照ください。本ページの翻訳に問題がある場合はこちらまでご連絡ください。

Troubleshooting custom domains and GitHub Pages

You can check for common errors to resolve issues with custom domains or HTTPS for your GitHub Pages site.

GitHub Pages is available in public repositories with GitHub Free, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see "GitHub's products."

ここには以下の内容があります:

CNAME errors

Custom domains are stored in a CNAME file in the root of your publishing source. You can add or update this file through your repository settings or manually. 詳しい情報については、「GitHub Pages サイト用のカスタムドメインを管理する」を参照してください。

For your site to render at the correct domain, make sure your CNAME file still exists in the repository. For example, many static site generators force push to your repository, which can overwrite the CNAME file that was added to your repository when you configured your custom domain. If you build your site locally and push generated files to GitHub, make sure to pull the commit that added the CNAME file to your local repository first, so the file will be included in the build.

Then, make sure the CNAME file is formatted correctly.

  • The CNAME filename must be all uppercase.
  • The CNAME file can contain only one domain. To point multiple domains to your site, you must set up a redirect through your DNS provider.
  • The CNAME entry must be the bare domain. For example, www.example.com,blog.example.com, or example.com.
  • The CNAME entry can only be used once on GitHub. For example, if another repository's CNAME file contains example.com, you cannot use example.com in the CNAME file for your repository.

DNS misconfiguration

If you have trouble pointing the default domain for your site to your custom domain, contact your DNS provider.

You can also test whether your custom domain's DNS records are configured correctly. 詳しい情報については、「GitHub Pages サイト用のカスタムドメインを管理する」を参照してください。

Custom domain names that are unsupported

If your custom domain is unsupported, you may need to change your domain to a supported domain. You can also contact your DNS provider to see if they offer forwarding services for domain names.

Make sure your site does not:

  • Use more than one apex domain. For example, both example.com and anotherexample.com.
  • Use more than one www subdomain. For example, both www.example.com and www.anotherexample.com.
  • Use both an apex domain and custom subdomain. For example, both example.com and docs.example.com.

Warning: We strongly recommend not using wildcard DNS records, such as *.example.com. ワイルドカード DNS レコードにより、あなたのサブドメインの 1 つで GitHub Pagesサイトを誰でもホストできるようになります。

For a list of supported custom domains, see "About custom domains and GitHub Pages."

HTTPS エラー

CNAMEALIASANAMEA DNS レコードで適切に設定されたカスタムドメインを使っている GitHub Pages サイトは、HTTPS でアクセスできます。 詳しい情報についてはHTTPSでGitHub Pagesサイトをセキュアにするを参照してください。

It can take up to an hour for your site to become available over HTTPS after you configure your custom domain. After you update existing DNS settings, you may need to remove and re-add your custom domain to your site's repository to trigger the process of enabling HTTPS. 詳しい情報については、「GitHub Pages サイト用のカスタムドメインを管理する」を参照してください。

If you're using Certification Authority Authorization (CAA) records, at least one CAA record must exist with the value letsencrypt.org for your site to be accessible over HTTPS. 詳しい情報については、Let's Encrypt ドキュメンテーションの「Certificate Authority Authorization (CAA)」を参照してください。

URL formatting on Linux

If the URL for your site contains a username or organization name that begins or ends with a dash, or contains consecutive dashes, people browsing with Linux will receive a server error when they attempt to visit your site. これを修正するには、GitHubのユーザ名から非英数字を取り除くよう変更してください。 詳細は「GitHub ユーザ名を変更する」を参照してください。

Browser cache

If you've recently changed or removed your custom domain and can't access the new URL in your browser, you may need to clear your browser's cache to reach the new URL. For more information on clearing your cache, see your browser's documentation.

担当者にお尋ねください

探しているものが見つからなかったでしょうか?

弊社にお問い合わせください