samples-js-react icon indicating copy to clipboard operation
samples-js-react copied to clipboard

at=error code=H10 desc="App crashed" method=GET path="/favicon.ico"

Open poddb opened this issue 2 years ago • 23 comments

Getting the following error when I npm start:

at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=my-app.herokuapp.com request_id=ID a fwd=".,*," dyno= connect= service= status=503 bytes= protocol=https

I can see that this in fileserver.js held in samples-js-react/node_modules/selenium-webdriver/lib/test/:

var app = express();

app.get('/', sendIndex) .get('/favicon.ico', function(req, res) { res.writeHead(204); res.end();

I've tried looking around the past day to see if I can find out what is causing it but nothing I try has resolved it.

Would appreciate some assistance as I am quite new to this and it might be a very simple fix but I can't see the wood for the trees

poddb avatar May 24 '22 16:05 poddb

@poddb which sample are you trying? okta-hosted or custom-login?

jaredperreault-okta avatar May 24 '22 17:05 jaredperreault-okta

@jaredperreault-okta okta-hosted

poddb avatar May 25 '22 08:05 poddb

@jaredperreault-okta have you got any idea of what I can try?

poddb avatar Jun 06 '22 08:06 poddb

@poddb are you attempting to run this locally? Or on heroku?

I just did a fresh install and the sample worked for me (locally)

git clone https://github.com/okta/samples-js-react.git
cd samples-js-react
npm install
cd okta-hosted
npm start
# browser to localhost:8080

jaredperreault-okta avatar Jun 06 '22 13:06 jaredperreault-okta

@jaredperreault-okta I'm doing it via heroku. I can get the app running ` $ npm start

@okta/[email protected] start node ./heroku/server.js

App is live on port 8080! ` But when I try and sign into the app in heroku I get Application error

and in the logs I see

2022-06-06T08:53:08.444061+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=*******.herokuapp.com request_id=a440e52c-2c51-4fd2-b751-2f938597684c fwd="**.*.***.***" dyno= connect= service= status=503 bytes= protocol=https 2022-06-06T08:53:19.201453+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=*******.herokuapp.com request_id=0b5898ff-474c-4ef6-8654-473e3276fcb7 fwd="**.*.***.***" dyno= connect= service= status=503 bytes= protocol=https

poddb avatar Jun 06 '22 14:06 poddb

Does it crash if you go to https://*******.herokuapp.com/okta-hosted-login?

jaredperreault-okta avatar Jun 06 '22 14:06 jaredperreault-okta

@jaredperreault-okta

Screenshot 2022-06-06 at 16 58 05

I get this

poddb avatar Jun 06 '22 15:06 poddb

@jaredperreault-okta I have been looking through the logs and have spotted this, though I am not sure how I would go about fixing it:

2022-06-14T08:13:45.533806+00:00 app[web.1]: at Function.Module._load (node:internal/modules/cjs/loader:778:27) 2022-06-14T08:13:45.533806+00:00 app[web.1]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) 2022-06-14T08:13:45.533807+00:00 app[web.1]: at node:internal/main/run_main_module:17:47 { 2022-06-14T08:13:45.533807+00:00 app[web.1]: code: 'MODULE_NOT_FOUND', 2022-06-14T08:13:45.533808+00:00 app[web.1]: requireStack: [] 2022-06-14T08:13:45.533808+00:00 app[web.1]: }

poddb avatar Jun 14 '22 10:06 poddb

@poddb I created an internal ticket to look into this. The sample works fine locally, so it might have something to do with deploying to Heroku

Internal Ref: OKTA-506911

jaredperreault-okta avatar Jun 14 '22 13:06 jaredperreault-okta

Hi @jaredperreault-okta was there any update on the ticket?

poddb avatar Jul 04 '22 08:07 poddb

@poddb This ticket is in our current sprint. Updates to follow

jaredperreault-okta avatar Jul 13 '22 16:07 jaredperreault-okta

any updates on the ticket?

Zuker-nie avatar Dec 17 '22 00:12 Zuker-nie

@Zuker-nie I believe this issue was fixed in https://github.com/okta/samples-js-react/pull/267. Are you still experiencing this issue?

jaredperreault-okta avatar Dec 19 '22 13:12 jaredperreault-okta

Hello,

This project was put on hold for the time being so I haven't been able to test anything. I will be sure to comment when we pick up the project again in the new year.

On Mon, 19 Dec 2022 at 13:37, Jared Perreault @.***> wrote:

@Zuker-nie https://github.com/Zuker-nie I believe this issue was fixed in #267 https://github.com/okta/samples-js-react/pull/267. Are you still experiencing this issue?

— Reply to this email directly, view it on GitHub https://github.com/okta/samples-js-react/issues/262#issuecomment-1357686653, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANQZEX37VVAL5GW2PGIULODWOBQJXANCNFSM5W2E2SPA . You are receiving this because you were mentioned.Message ID: @.***>

-- Kind Regards,

Padraigh Basquille (he/him they/them) Engineer, IT & Security 8am - 6pm (M, T, W, F)

Learn more about Shout https://giveusashout.org/ - Click here to volunteer with us https://crisistextlineuk.tfaforms.net/24 Mental Health Innovations (legal name of Shout) is a registered charity, number: 1175670

poddb avatar Dec 19 '22 16:12 poddb

I am facing the same issue. When the app is hosted locally it runs But when deployed to Heroku it shows the below error. at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=apitestrisk12.herokuapp.com request_id=5e73a635-20a4-4922-b280-477b140a596a fwd="144.167.230.11" dyno= connect= service= status=503 bytes= protocol=https

trobinuk avatar Feb 21 '23 03:02 trobinuk

I've got the exactly same error message as trobinuk described. The python code was running well on the Heroku until some time last week when I tried to deploy an updated code with minor changes. Even when I now use the code that was previously deployed with success, the same error message appeared. It appears that something has changed on the Heroku server.

testruncoder avatar Mar 28 '23 04:03 testruncoder

Same - I am currently trying to figure it out. I believe it has to do with how the directories are organized.

lalithadsuresh avatar Sep 04 '23 03:09 lalithadsuresh

got the same issue for my deployment

iphaminh avatar Oct 20 '23 18:10 iphaminh

same problem for my deployment

ricpar123 avatar Feb 10 '24 21:02 ricpar123

has anyone solved the problem?

oondels avatar May 11 '24 15:05 oondels

same problem

ccorreia-rhaeos avatar May 24 '24 16:05 ccorreia-rhaeos

same problem here

eayand avatar May 29 '24 17:05 eayand

I had the same issue but I resolved mine by changing this in my package.json file "scripts": { "start": "nodemon index.js" },

to

"scripts": { "start": "node index.js" },

mimi-tech avatar Jul 29 '24 16:07 mimi-tech