Describe the problem/error/question
Installed earlier today and all was working well. Ran into an error, thought it was a local issue and moved to the cloud. Went to load locally tonight and it will not go.
What is the error message (if any)?
This site can’t be reached
Check if there is a typo in local.
- If spelling is correct, [try running Windows Network Diagnostics](javascript:diagnoseErrors()).
DNS_PROBE_FINISHED_NXDOMAIN
and when I do run diagnostics
I’ve pinged local, I’ve pinged 127.0.0.1 and there are no issues at the CMD. I’ve even added 5678 to pass any proxies.
Information on your n8n setup
- n8n version: Version 1.102.4 (assumed)
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main): own
- Running n8n via (Docker, npm, n8n cloud, desktop app): npm
- Operating system: Win11 23H2
Hey @CandiAnne hope all is well.
From the error on the screenshot it looks like you are trying to access “local”?
Can you please provide more details:
- what have you installed?
- what error you ran into?
- when you say “it will not go” what do you mean?
Could you please provide steps to reproduce this issue? Screenshots, outputs, anything you think could help.
Evenin @jabbson, apologies for not being clear enough. Have been workin on this stuff all day and brain is mush plus it’s late here. I installed the whole node.js and such today as per the directions for a local install. npm install n8n -g and everything was running smooth as can be. Then something went wonky, not thoroughly understanding what I’m doing I moved to the cloud version thinkin it was a local issue and not a me issue. Figured out where I erred so wanted to go back to my computer. When I type in http://local:5678 I get the error about site can’t be reached, make sure local is spelled right yadda yadda that I have in my original question.
I’ve tried both –
but yet when I go to CMD line it’s no issue
C:\windows\System32>ping localhost
Pinging Envy [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Ping statistics for ::1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\windows\System32>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
I’ve also made sure that all is well with my firewall, everything has permission. I even added 5678 special just in case
Are you certain n8n in running?
I don’t see why it wouldn’t be, I didn’t uninstall it or anything. Will check in the morning when I get up. Thank you for the help @jabbson 
Seems like the n8n is not running, if you installed n8n using npm, then you can start by running ‘n8n’ or ‘n8n start’ command in the terminal and let the terminal open. Then try to ping / curl ‘localhost:5678’ in a different terminal
@jabbson I got up and went to my computer, no it wasn’t running I had to completely reinstall, neither n8n nor n8n start would work at the cmd – no clue how or why that happened but I’m back in.
@Sultan_Naufal_Abdill thank you for the reply as well.
Which command did you use to install n8n? was it npx n8n?
