-
Notifications
You must be signed in to change notification settings - Fork 930
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
GitHub Pages shows 404 error when navigating to other routes #63
Comments
Looks like it's problem with In your condition I can see, that route is |
Having the same issue for a while, found any solution yet? :)) |
Likewise, I have encountered the same issue. I'll post back if I figure it out. |
Found the problem: capital letters in the repo name. I change the repo name to the same name, but with all lowercase letters (including the Homepage url in the package.json) and re-deployed. No 404 now. I get a white screen, which is a different problem, but the 404 is gone. |
I have everything in lowercase, however it doesn't help |
Use some other hosting site like firebase
…On Wed, 20 Apr 2022, 15:40 Ekaterine (Catherine) Mitagvaria, < ***@***.***> wrote:
Found the problem: capital letters in the repo name. I change the repo
name to the same name, but with all lowercase letters (including the
Homepage url in the package.json) and re-deployed. No 404 now. I get a
white screen, which is a different problem, but the 404 is gone.
I have everything in lowercase, however it doesn't help
—
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJVVIWS43WP4QTOPIRMQM2DVF7JZ7ANCNFSM5AVCM6ZQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I had the same issue, and found it was the way I was Handling my Routing. I was using
|
Hi everyone, sorry about the long wait. In case you are still getting an HTTP 404 error page when you navigate to other URLs within your app, you may be running into a limitation of GitHub Pages, which is described here, in the official CRA deployment guide: https://create-react-app.dev/docs/deployment/#notes-on-client-side-routing Also described in that guide are two available workarounds, one of which @israelmrios described above. I recently paraphrased the same two workarounds in the following issue comment: #104 (comment) |
I created my portfolio website but when I click on home or about me or skills or contact ...every time I found the error like
How I solve this problem
The text was updated successfully, but these errors were encountered: