I have an issue, my website seems to build and deploy fine but when I visit it I received a blank screen. When I inspect element I receive 4 errors stating ‘Failed to load resource: the server responded with a status of 404 ()’. I understand that the page isn’t loading because it can’t be found but I don’t understand why it can’t be found.
I’m not seeing any 404 errors, just a blank page— opening the Dev Tools confirms that the request for the HTML returned with a 200 OK. What does appear to be failing to load are your JS and CSS files, though.
Since I don’t know what your build environment looks like I would double-check that the correct directory is being deployed and that any build artifacts are generated in the directory that will be deployed.
One way to check that things are where they’re supposed to be is visit the build page for your most recently deploy and click the download button next to the timestamp. This will download the directory that Netlify deployed so you can see what was actually pushed live.
@noelforte@Luke You were right, I had stupidly left “homepage” : “https://www.kairoberts.github.io/react_portfolio” inside my package.json because I tried to deploy through gh-pages originally, so that is why it was adding /react_portfolio/ within the build folder. Everything is now working as intended, cheers for the help gents I appreciate it.
good day sirs, please I have a react app hosted on Netlify with the backend hosted on Heroku.it works well locally but on Netlify I get Failed to load resource: the server responded with a status of 404 ()
for my posts and all authentications. Here is the link to my site,
good day sir and happy new year . i have looked at the documentation and i am able to get data, sign in using google auth and delete data . but somehow I still get the error when i try to sign in with my heroku server
the error is coming from netlify…
Failed to load resource: the server responded with a status of 404 () user/login:1
the google auth is working just fine
I can see that you’re forwarding the request from /auth/ to the /user/login on Heroku. Then, you’re applying the same rule to Signup and that won’t work. Plus, I’m not seeing any rule for /user/login URL.
Are you sure you’ve done the setup correctly? Could you share your repo?
The issue here is /auth/* will always go to https://memory-lane2021.herokuapp.com/user/login and never https://memory-lane2021.herokuapp.com/user/signup because you are using a wildcard (* matches anything.) You would need something like