Public Folder in Heroku Not Working with Images and Routes

0
votes

I am at a loss... I have tried so many different things but can not get this to work right.

Regardless if I run the Build or if Heroku runs the build, something weird is happening with the Public folder in my react app.

Everything works really well in the local server. But things are not working the right way when I launch it to Heroku -

First, I was storing my background Image for the home page in the public folder - It worked in the local server but not when I launched it to Heroku.

The Favicon also will not work in the heroku launch.

Lastly, it also wont register my routes. Locally I can go to /admin, but when launched to Heroku, it gives me a 503 error.

Not quite sure what code to include here - I am thinking maybe it has something to do with git? Not sure!

Thanks for your help!

Here is the Heroku Log ---

2020-07-03T23:26:06.755835+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/aaaa" host=www.brianpruzzo.com request_id=1d6e5d13-5464-4ca5-8965-8e70aa5fa915 fwd="77.255.15.191" dyno=web.1 connect=1ms service=30000ms status=503 bytes=0 protocol=https

2020-07-03T23:26:13.767848+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/manifest.json" host=www.brianpruzzo.com request_id=f218a673-5a9a-484c-9fe9-002689f69f9f fwd="77.255.15.191" dyno=web.1 connect=1ms service=30000ms status=503 bytes=0 protocol=https

1
reactjsexpressherokupublic
Can you access the files directly from heroku, such as myApp.heroku.com/favicon.ico? – Adam Jeliński
No I can not - Though I am trying with a custom domain name. www.brianpruzzo.com/favicon.ico - Hold up for a sec I am messing with this... – Nick McLean
brianpruzzo.com – Nick McLean
Okej, so for some reason all of the unprocessed files and custom routes throw errors. Does the heroku logs --tail command provide any useful information about the errors, that you could post? – Adam Jeliński
Posting above ! – Nick McLean

1 Answers

1
votes

Alright! After a while I finally figured out the issue... be sure to check that the static route in your express server comes before your other routes. Better yet... use a router.... Agh! It got me.