-
Notifications
You must be signed in to change notification settings - Fork 22
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
Bug: 404 Page Not Found on refreshing a page on gh-pages #48
Comments
This happens to /register also .. Please include that too ..!! @Rahulm2310 |
@chinmaym07 It is a generic issue and happens with all routes. |
I want to give it a try, Could you assign this to me? @Rahulm2310 |
Yours @Aryamanz29 . Happy Researching 🎉 |
@Rahulm2310 Hii,👋 |
Hi @Aryamanz29, you need to submit link to a google doc explaining the solution. So that others can give their feedback on it. |
@Rahulm2310 Done 👍 , Could you please review my PR 😄 |
Is there a solution for this? Thanks! |
Is there a solution for this? I am facing same issue with repo that has a react project. |
No solutions yet for this problem. unfortunately |
Joining the thread to find out whether someone found any solution to this. I have been researching this for almost a month and had no luck so far, unfortunately! |
Hello, I found a workaround to solve this, I was facing the same problem on my angular app I hope it works as well for you.
If you are not using custom domain on Github Pages set Copy this script and add to you index.html.
On you build folder need to have this file 404.html, and thats is it. |
…irectly using any routes anitab-org/stem-diverse-tv-cms#48
this video hepls me: |
Thank you for This |
Hi there, if you use Angular
if you use react. index.js
I hope will be helpfull. |
I'm deploying a VueJS app to To get around this issue:
In this example, all directory pages need to be added to the
|
Describe the bug
We get a
404 Page Not Found
error when refreshing a page. Actually, this happens because github pages doesn't supports single page apps. It doesn't have access to front-end routes.To Reproduce
Steps to reproduce the behavior:
Expected behavior
We should not get a 404 error and should be redirected to the same page.
A solution I saw was to add a 404.html file to add under the public folder which redirects back to index.html. Although not sure if it will work for us or not.
Feel free to
research
on this find the best possible solution.Screenshots
Desktop (please complete the following information):
Additional context
For reference, you can see the implementation here.
The text was updated successfully, but these errors were encountered: