У нас вы можете посмотреть бесплатно How to Enforce HTTPS for Your GitHub Pages Using a GoDaddy Domain или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
Learn how to enable HTTPS on your GitHub Pages site connected to a GoDaddy domain by following these simple steps. --- This video is based on the question https://stackoverflow.com/q/69260922/ asked by the user 'lachnroll' ( https://stackoverflow.com/u/13187747/ ) and on the answer https://stackoverflow.com/a/69261496/ provided by the user 'lachnroll' ( https://stackoverflow.com/u/13187747/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions. Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Unable to enforce https for github pages with Godaddy domain Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l... The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license. If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com. --- Enforcing HTTPS for GitHub Pages with a GoDaddy Domain If you've set up a website using GitHub Pages and linked it to a domain purchased from GoDaddy, you might be facing an issue with enabling HTTPS. A common message you may encounter is that "the domain is not eligible for HTTPS at this time." This can be frustrating, especially when you want to ensure your site is secure and trustworthy. Fortunately, the solution is relatively simple once you understand the necessary steps. Understanding the Problem The inability to enforce HTTPS on your GitHub Pages site primarily arises from misconfigured DNS settings on the GoDaddy platform. When you set up your domain, GoDaddy configures certain DNS records automatically, which can interfere with GitHub's ability to issue an SSL certificate for your custom domain. Common Symptoms You receive a warning that your domain is not eligible for HTTPS. Your site may function properly but still lacks a secured connection. You’ve already checked for mixed asset types in your HTML files, but still can't enable HTTPS. Solutions for Enforcing HTTPS To fix the HTTPS issue, you need to make adjustments to your DNS records on GoDaddy. Here’s how to do it: Step 1: Access Your DNS Settings Log in to your GoDaddy account. Navigate to the Domains section and select the domain you are using for your GitHub Pages site. Look for the option that allows you to modify the DNS settings. Step 2: Remove the A Record for "park" Once in the DNS management section, locate the A Record that has a value of park. This record can often cause conflicts with HTTPS configuration. Delete this specific A Record. Removing it will help clear up any issues with GitHub's SSL certificate issuance. Step 3: Verify Your DNS Settings After removing the A Record, double-check your other DNS settings to ensure that they are pointing correctly to GitHub Pages’ IP addresses. Typically, you should have CNAME records set for www pointing to <username>.github.io and proper A records pointing to GitHub's IP addresses. Step 4: Enable HTTPS on GitHub Once you’ve made the changes to your DNS settings, head back to your GitHub repository settings. Look for the GitHub Pages section. Check the box to enforce HTTPS. Conclusion By following these steps to adjust your DNS records on GoDaddy, you should be able to enable HTTPS for your GitHub Pages site successfully. Enforcing HTTPS is essential for securing your website and improving user trust, so it’s worth taking the time to ensure everything is correctly configured. If you continue experiencing issues after making these changes, it could be helpful to wait for a few minutes to several hours, as DNS changes can take time to propagate. Now, enjoy the peace of mind that comes with a secure, HTTPS-enabled site on your custom GoDaddy domain!