#SJ057
1 messages · Page 1 of 1 (latest)
Um that seems like smth not related to Stripe API?
Yes ..It is not related to stripe API
It looks like a TCP connection is closed by the connected remote host. (as the error says)
and you are connecting from 2 different hosts in same local computer which sound strange to me
I am trying to run single app only
Can you please suggest any work or solution around on this issue
I would depends on what you are doing, which technology stack, which language, which command?
it is just stripe app..i am not calling any api....just trying to run stripe app with respect to stripe app documentation
Oh okie, which Doc are you following?
In which step you have that error?
when I hit stripe apps start>>>it is not showing account on which app need to test...it still showing that need to start development server
the correct command is with the plural (apps)
stripe apps start
and make sure you call it inside the directory of the app
I am using same stripe apps start...but still getting same error
yes...i am calling from same directory
can you screenshot?
hmm okie, are you logging in with stripe login and have node installed with node -v?
Can you just ignore this app and recreate a new app?
Would you repeatedly see this error?
Yes ...i have created new app but getting same error
Hi @halcyon quarry I'm Jack and I'm also an engineer from Stripe.
Do you have another service also running in 4242 port?
no
Is there any way we can try to run app locally with another port...so i can try out that
No you can't run Stripe apps locally, you can only run it in Dashboard as an extension.
Can you run a netstat and see if there are any other services using 4242?
ok
Do you have a firewall configuration that could block certain kinds of traffic?
Pardon me...one of the service is running under 4242 port
Can you stop this service and try stripe apps start again?
Yes , I have tried with that as well
still no luck
it is working now
Thanks 🙂
Welcome. How did you fix it eventually?
Due to cache it is not working....i have clear all temp data and cache again..
I see. Glad to know that your problem is fixed