a year ago
I'm trying to take memory dumps of my nodejs application in production deployed on railway, I've added --inspect=0.0.0.0:9229 to the NODE_OPTIONS and added a TCP proxy to my service in railway
But I'm unable to get it to work inside chrome://inspect/#devices, I suspect the proxying is working correctly
Has anyone successfully done this inside railway?
23 Replies
a year ago
on render
?
a year ago
haha fair enough
a year ago
what service?
I notice when I curl the tcp proxied domain and port I get a response back from my nodejs app
My nodejs app is served on 3000
If this isin't possible I guess I will dump some heapdumps to a remote location like this person did: https://discord.com/channels/713503345364697088/1178691418919813160/1178691418919813160
a year ago
looks like you also need the uuid?
a year ago
isnt frontend a node.js app?
a year ago
on railway the debugger is now at 50647
Yep but:
It doesn't appear in chrome://inspect/#devices
When I try to curl the proxied domain and port
50647I get a response back from the nodejs app
a year ago
hmmm yeah, i do get html back from the tcp proxy
a year ago
but the debugger is on port 9229 -
# curl http://127.0.0.1:9229/
WebSockets request was expected(from inside the container)
a year ago
no there isnt
a year ago
well not natively
a year ago
sounds good
a year ago
!s
Status changed to Solved brody • about 1 year ago