Skip to content
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

front end not running - cannot get on screen #9

Open
nosizejosh opened this issue Oct 21, 2018 · 7 comments
Open

front end not running - cannot get on screen #9

nosizejosh opened this issue Oct 21, 2018 · 7 comments

Comments

@nosizejosh
Copy link

the fron end code will not run, error in browser console as follows;

favicon.ico:1 GET http://localhost:3000/favicon.ico 404 (Not Found)
A bad HTTP response code (404) was received when fetching the script.
Failed to load resource: net::ERR_INVALID_RESPONSE
localhost/:1 Refused to load the image 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAACXBIWXMAAAsTAAALEwEAmpwYAAAKwWlDQ1BQaG90b3Nob3AgSUNDIHByb2ZpbGUAAHjarZZ3UJPZGsbf7/vSSKElhCIl9CZIJ4D0GkBBOtgICZBACCEFAbuyqOBaUBEBdUVXRBRcCyBrQUSxItj7giwqyrqoiw2V+wdLuHfuvX/cmfvOnJnfPHPOc973nH8eAOpjrkQiQtUBcsRyaUxoACspOYVFfAoI6AMZqMDm8mQS/+joSPjPhQB8uAsIAMAtO65EIoL/rTT46TIeABINAGl8GS8HADkOgHTwJFI5AFYAAKaL5BI5AFYDAAxpUnIKAHYEABiZE9wJAIy0Cb4PAAxpXEwgADYMQKJyudJMAMonAGDl8zLlAFQdAHAQ84ViAGoYAPjwBFw+AHUtAEzPycnlA1CPA4BV2j/5ZP6LZ5rSk8vNVPLELAAAQ...5eiVOB/6fEQwCTMFJltVplpVIJS+LLmh1nYcC3Wi0KISiEYKPRCEuiiQOTcCn4drtNIcSf80IINpvNMASuAOD2UMdOpyMNvylRLBaDFrgFgJtDHS3L4nK5lIYnydlsxmQyGbTADQBcuulcKpW4WCyk4VOpVBiv0CUAvAJw5+aCbDbLer3OWq3GWCwWNfwdgJdOKj2TvVFE8ATwdvdjdn5C8B/2/U54kpjP50rBe5bYHdgqwEtJ2LZNkpxOp1vwpmkynU4fHV56TGy2QqFA27Zp2zbz+fzR4X1JOPBO+JSQhpeSyGQyW/CbEqZpBg5/sMhH8jOA925tV6sVNO3v0pumadB1TzXFjwA+BbkyJ52dbNv2+iPn+7XZtzbqWiKXy7Hf73MwGNCyrGjg96xOnyO8qWKw8GGl2KjhNyVEAOACwLuoykxv1isEfqaEr1XYavAMwHMAD1z2/wXgx7qC72+vxP/dKhHH7wEASvaA8SqpSrsAAAAASUVORK5CYII=' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

@JKHeadley
Copy link
Owner

@nosizejosh I'm not able to replicate this currently. It looks like this is due to security updates in the browser. Please see this SO issue and let me know if it helps at all:
https://stackoverflow.com/questions/32166870/img-src-was-not-explicitly-set-so-default-src-is-used-as-a-fallback

@nosizejosh
Copy link
Author

tried on three different browsers, same results. Looked for a similar meta tag to update as described in the SO article but couldn't find in the index.html file.

@nosizejosh
Copy link
Author

still not working. tried a couple of browsers but same results. Tried to find the meta to update as described in SO article but cant find culprit meta tag either. not sure if that really is the challenge though.

@nosizejosh
Copy link
Author

still unable to get this working. can you please have a look so I can move ahead with my project?

@JKHeadley
Copy link
Owner

@nosizejosh I'll look into this but it will be hard to debug if I can't reproduce. I'll let you know if I make any progress. In the meantime any details (such as exact browser versions) you can provide will help.

@nosizejosh
Copy link
Author

@JKHeadley thank you so much. My default browser is Google chrome and with current Version 70.0.3538.67 (Official Build) (64-bit). I am running on windows and for other browser eg explorer, I dont get the "Refused to load the image " error in browser console, just "cannot Get/" on a blank screen.
Is there a way to run just the back-end and proceed with development until issue is resolved? also are there any write-ups on deployment etc? im trying to get an mvp api out asap. Thanks

@JKHeadley
Copy link
Owner

@nosizejosh Thanks for the info. Yes you can run the backend alone either by using node directly or by commenting out the web/frontend portion of docker-compose.yml.

Unfortunately most of the docs (including deployment) are still in progress as of now. However I'm happy to try to answer any deployment questions here if you like.

For frontend deployment I highly recommend Netlify. The app already has some support for this via the netlify.toml file and the deploy npm script.

Backend deployment is usually more involved and can vary in complexity. In the past I have used a free tier AWS EC2 server with mongo and nginx installed for personal projects. I've also been wanting to try captain duck duck. It's probably worth looking into.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants