Netlify deployed with no errors, but page blank .HTTP2 error

My github repo deployed to Netlify with no problems, but I’m getting an HTTP2 error in my console. Not sure what it means-- how am I supposed to resolve this?


@westher0870 If you check the errors you’ll see that the files are trying to load from an odd location, where a token value looks like it hasn’t been replaced (%PUBLIC_URL%):

What would this error be due to? I’m having the same issue, its making requests to that url, how to i get the public_url value to be replaced?

It’s a little hard to say, since you’ve not provided any details on what you’re working with.

Taking the guess that it’s probably create-react-app, then it’s likely you just haven’t set a value for it and thus it can’t interpolate it.

I don’t work with it myself, but from a quick check it appears that you can set the value via a homepage property in the package.json, e.g.

  "homepage": "",

or alternatively via an environment variable of PUBLIC_URL.

Yeah, sorry i didn’t really add any extra info. I did use create-react-app. I keep getting manifest.json not found and check the request and its going to "netlifyurl/%PUBLIC_URL%/manifest.json.
I was looking at other answers on othe sites and they said to set the homepage to “/”, but that wasn’t working, so i’ll try changing it to the netilfy url

Hi @mbaccari :wave:t6: Welcome to the forums! Sorry to hear you are having issues with your site! Give that suggestion a go and let us know if it works? If that doesn’t work can you share your build log and the site you are referring to? We may be able to assist further. Good luck and happy building! :netliconfetti:

I tried changing the homepage to the deployed url, but that didnt work. I think I’m having the same issue as the original poster of this thread. She said it ended up being a react-router-dom issue and linked to a doc, but she doc she posted isn’t up anymore so I can’t figure out what she did to fix it

In most cases, the problem is because:

  1. You did not run CI= npm run build
  2. OR you set the publish path to public instead of build.