https://serverless-stack.com/ logo
Join Slack
Powered by
is this stuck for anyone else? I have the latest v...
# help
s
is this stuck for anyone else? I have the latest version of SST
f
which browser r u using?
s
Firefox, latest
f
do u have 
sst start
or 
sst console
running?
s
doesn’t work in Chrome either
sst start
f
and u r going to the url that 
sst start
prints out after it starts up?
t
can you open the network inspector, find the ws connection and send a screenshot of the messages in it
s
oh woops. I had https://console.serverless-stack.com/ bookmarked. but the link that 
sst start
prints gets stuck on “syncing metadata”
one sec
t
if it gets stuck on syncing metadata do you see a bunch of reqs going out to cfn?
s
websocket activity
I see activity in the websocket connection when I navigate in my app
but the SST console page still says “syncing metadata”
t
are you seeing normal http reqs go out to cfn?
any any errors in console?
s
no errors in console, just that one in the browser
t
can you click that error
what's the error?
s
nothing.. it’s kinda not useful 😕 just NS_BINDING_ABORTED. here’s a HAR file, if that helps
lemme know once you have that so I can delete it. just in case it has my AWS account info or any credentials in there
t
can delete
do you have sst start running on a different port?
s
no, no changes to the ports or anything
t
what happens if you go to localhost:12557
s
it hangs. curl request also hangs
whoa. I quit the SST process and port 12557 is still there
that.. doesn’t seem right?
t
is maybe a previous sst start deployed and stuck there?
s
don’t think so. I just did 
pkill node
the port is still open
t
I only know how to figure out what's running on a port in linux
s
sudo lsof -i -P | grep LISTEN | grep 12557
t
might need to try 
pkill -9 node
s
you’re right, 
-9
was needed
ok, restarting sst
ahhhhhh, there we go
thanks! that was strange
12 Views
Open in Slack
PreviousNext
Powered by