Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/inf800/chro.in
Landing Page
https://github.com/inf800/chro.in
Last synced: 24 days ago
JSON representation
Landing Page
- Host: GitHub
- URL: https://github.com/inf800/chro.in
- Owner: INF800
- Created: 2024-01-20T14:06:08.000Z (11 months ago)
- Default Branch: main
- Last Pushed: 2024-02-15T21:09:06.000Z (10 months ago)
- Last Synced: 2024-02-15T22:27:11.776Z (10 months ago)
- Language: HTML
- Size: 40 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# chro.in
Page to test hostinger service without SSL and check if adding 3rd party SLL certificate is possible.
#### Steps to direct chro.in to github pages (HTTP)
- Host gh page @ https://inf800.github.io/chro.in
- Create `CNAME` file with `www.chro.in`. (This will redirect all browsers to www.chro.in when https://inf800.github.io/chro.in is given in URL field)
- Add the following in DNS: (Same can be done for other providers like Godaddy etc.)
| Type | Name | Content | TTL |
| --- | --- | --- | --- |
|A|@|185.199.108.153|14400|
|A|@|185.199.109.153|14400|
|A|@|185.199.110.153|14400|
|A|@|185.199.111.153|14400|Now, chro.in will contain the contents deployed at https://inf800.github.io/chro.in.
#### Steps to add SSL (HTTPS)
- Signup @ https://www.cloudflare.com/
- Click on "Add website or application"
- Enter domain name "chro.in" and press continue.
- Select the free tier
- Verify DNS records are set correctly. You should see previously added information automatically. Press continue.
> Note: Sometimes the CNAME record may not appear as in below image, in that case, add it manually!
- The next page that tells you to do 1. Log in to your domain registrar, 2. Avoid DNS resolution issues caused by DNSSEC and 3. Update your nameservers (follow them and). Press continue.
1. Log in to your domain registrar
> "Domain registrar" is the same as your domain provider like Hostinger, GoDaddy, etc.
2. Avoid DNS resolution issues caused by DNSSEC
> Basically delete all DNSSEC fields
3. Update your nameservers
> Replace your provider's nameservers with cloudfare's nameserver
- Go to the "SSL/TLS" section.
- Choose the SSL/TLS encryption mode to ~"Full"~ "Flexible" (Do not select the "Full (strict)" which will cause [526](https://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-526-invalid-ssl-certificate) with cloud fare).
- **Wait for about 1 - 48 Hrs, you should be able to see a secure HTTPS connection @ https://www.chro.in/**
- ~~To always use HTTPS, go to "SSL/TLS" -> "Edge Certificates" -> "Always Use HTTPS" -> Click on toggle button.~~> #### References
> - https://dev.to/vjnvisakh/hosting-a-custom-domain-on-github-2d1a
> - https://dev.to/pratik_kale/github-pages-custom-domains-and-ssl-mc4
> - https://stackoverflow.com/questions/54059217/how-to-fix-domain-does-not-resolve-to-the-github-pages-server-error-in-github
> - https://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-526-invalid-ssl-certificate