404 \ Page not found when deploying to Netlify

[zouhir]

I'm not sure if other static site servers / platforms are all like that, but if we deploy this to Netlify we can only navigate from index.html to other pages using Links, once your refresh or type a URL directly in the address bar we'll get 404

In order to get History push state to work we need to add this re-write rule:

/*    /index.html   200

which can be in a file for Netlify in the repo root.

Can we add this directly? as I can see Netlify support is welcome in the Preact repo.

[developit]

Sure! Any chance there's a way to define that in the .toml file? If not then a separate does file is fine.

[zouhir]

Unfortunately no. Netlify does in in 1 way only, which is having a _redirects file in the deployed folder eg dist/ but I'll have to update the docs accordingly

[zouhir]

Ref: (https://www.netlify.com/docs/redirects/)[https://www.netlify.com/docs/redirects/]

Looking more into this...

[developit]

I think we decided to punt on this for now, right?

[zouhir]

I think it's very good to have and won't harm if people won't need it! if ytou think so too, here's a PR #103

[pensebien]

I think people need this. I had to go through a lot of pain to get to understand how to use this. It is really helpful especially for situations where you decide to use routers from you js application

[ianskie1234]

Can anyone help me with this problem "PAGE NOT FOUND. Looks like you've followed a broken link or entered a URL that doesn't exist on this site." I really don't know what to do. My folder came from hithub and when I'm finish deploying it in netlify, when I view my site, It goes like this.

[developit]

You need to configure the fallback HTML page. You can do this by simply copying dist/index.html to dist/200.html and redeploying.

[douchuis]

actually i have the same problem, anybody can say exactly what i should do. Thanks

[constantinpojoga]

in my case, for create-react-app:

• create a _redirects file in public
• add /* /index.html 200 to that file