Warehouse name must be uername.github.io
, the user name is your GitHub user name, so that 404 will not appear
but I didn’t use my user name at first, and later found that it was the same, so I went to modify my user name to keep it consistent with the warehouse name, so the final result of this operation is still 404
solution: Delete the warehouse you just built, create another warehouse with the new user name, and repeat the steps
Read More:
- Solve GitHub push error 403 Forbidden while accessing
- django.db.utils .IntegrityError: NOT NULL constraint failed: blog_ blog.author_ ID error resolution
- GitHub push ErrorThe requested URL returned error: 403 Forbidden while accessing
- Solving GitHub push error: the requested URL returned error:403 Forbidden while accessing
- [details] jar conflict resolution in Maven (personal test)
- A little bug of CSDN blog
- Possible causes and solutions of 404 problems in accessing servlet pages
- About maven Pom.xml Personal solutions to reporting errors!!!
- Parse error: syntax error, unexpected T_OBJECT_OPERATOR in E:\WWW\blog\hyii2\frontend\web\index.php
- 404 error in browser accessing Servlet
- Push failed Unable to access ‘https://github.com/‘: Failed to connect to github.com port 443: Timed
- Using GitHub in vs2017
- Halo blog system reports log error when idea is running
- In the laravel project of GitHub clone, whoops, looks like something went wrong
- A Chrome extension to protect the privacy of personal favorites
- SSL_ERROR_SYSCALL in connection to github.com:443
- Exception of browser accessing servlet404
- NPM installØin sprintf- [email protected] Wealth: not available https://github.com/nhn/raphael.git/ “
- macos LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443
- Nginx reports 502 error, log connect() failed (111: Connection refused) while connecting to upstream. A personal effective solution