Netlify dev port unknown

Support
1

Nowhere in the docs or the CLI output does it say which port I should open my browser at to see the proxy.

I have the folowed this

Thus the default Gatsby template and added a function (not actually called yet ) and I see gatsby startup with ‘netlify dev’ and its messages but then I just see a series of … evergrowing and no idea what port the proxy is serving on.

The diagram in the docs shows 8888 but that does not work.

I can get to gatsby on 8000 as usual.

Also As the . keeps getting added to I am unable to scroll up the bcli buffer to see previous output to check for errors etc

Thanks

2

So I just tried to invoke my function manually via the cli and got this (sorry dont know how to get code formatting here). I get the same error whatever option I choose for the prompt.

? Pick a function to trigger
? Pick a function to trigger token-hider
? Invoke with emulated Netlify Identity authentication headers? (pass --identity/–no-identity to override) (Y/n)
? Invoke with emulated Netlify Identity authentication headers? (pass --identity/–no-identity to override) Yes
ran into an error invoking your function
FetchError: request to http://localhost:8888/.netlify/functions/token-hider failed, reason: connect ECONNREFUSED 127.0.0.1:8888
at ClientRequest. (C:\Users\steve\AppData\Roaming\npm\node_modules\netlify-cli\node_modules\node-fetch\lib\index.js:1455:11)
at ClientRequest.emit (events.js:210:5)
at Socket.socketErrorListener (_http_client.js:406:9)
at Socket.emit (events.js:210:5)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
message: ‘request to http://localhost:8888/.netlify/functions/token-hider failed, reason: connect ECONNREFUSED 127.0.0.1:8888’,
type: ‘system’,
errno: ‘ECONNREFUSED’,
code: ‘ECONNREFUSED’

3

I also tried appending / to the functions entry in the toml but it makes no difference.

4

Looks like others havre some problems and is a known bug

Rolling back netlify-cli fixed it for me too

5

Hi @slim glad you found that issue. We always recommend checking the repo for the cli when you have problems since that’s the source of truth for bugs/issues and requests. Sorry about that!

6

Got it and that makes sense. I just followed the general help path which pointed me to the forum. I much prefer to use issues :slight_smile: Happy new year.

1 Like