Uncaught Error: Not connected

philippotto commented 7 years ago

[Enter steps to reproduce:]

Temporarily disconnect remote connection and try to let it automatically reconnect

Atom: 1.16.0 ia32 Electron: 1.3.13 OS: Windows 10 (local) and Ubuntu 16.04 (remote) Thrown From: nuclide package 0.218.0

Stack Trace

Uncaught Error: Not connected

At C:\Users\Philipp\.atom\packages\nuclide\pkg\nuclide-remote-connection\lib\SshHandshake.js:0

Error: Not connected
  at Client.forwardOut (/packages/nuclide/node_modules/ssh2/lib/client.js:983:11)
  at SshHandshake._forwardSocket (/packages/nuclide/pkg/nuclide-remote-connection/lib/SshHandshake.js:264:22)
  at /packages/nuclide/pkg/nuclide-remote-connection/lib/SshHandshake.js:474:18)
  at emitOne (events.js:96:13)
  at Server.emit (events.js:188:7)
  at TCP.onconnection (net.js:1459:8)

Commands

     -2:35.4.0 editor:toggle-line-comments (input.hidden-input)
     -2:35.1.0 core:save (input.hidden-input)
  4x -2:34.5.0 core:move-up (input.hidden-input)
     -2:32.5.0 editor:select-to-end-of-word (input.hidden-input)
     -2:32.3.0 core:copy (input.hidden-input)
     -1:27.9.0 editor:move-to-end-of-screen-line (input.hidden-input)
  6x -1:27.4.0 editor:move-to-beginning-of-word (input.hidden-input)
     -1:25.5.0 editor:select-to-beginning-of-word (input.hidden-input)
  2x -1:17.6.0 editor:move-to-beginning-of-word (input.hidden-input)
     -1:17.1.0 editor:select-to-end-of-word (input.hidden-input)
     -1:15.9.0 core:save (input.hidden-input)
     -0:54.6.0 editor:select-to-beginning-of-word (input.hidden-input)
     -0:53.5.0 core:save (input.hidden-input)
     -0:52.8.0 editor:move-to-end-of-word (input.hidden-input)
     -0:52.6.0 core:move-right (input.hidden-input)
     -0:51.9.0 editor:select-to-end-of-word (input.hidden-input)

Non-Core Packages

git-history 3.3.0 
haskell-grammar 0.4.0 
highlight-selected 0.13.1 
language-babel 2.57.7 
language-graphql 0.8.0 
language-ini 1.19.0 
language-lua 0.9.11 
language-ocaml 1.8.0 
language-swift 0.5.0 
language-thrift 1.0.2 
linter 2.1.2 
linter-eslint 8.1.6 
MagicPython 1.0.9 
merge-conflicts 1.4.4 
nuclide 0.218.0 
nuclide-format-js 0.0.36 
rulerz 0.4.3 
set-syntax 0.3.2 
sort-lines 0.14.0 
tool-bar 1.1.0

hansonw commented 7 years ago

This seems like you're using the insecure code path "nuclide-start-server -k". Is that the case / if so, does this work without that extra flag?

philippotto commented 7 years ago

@hansonw Yes, this is true. I'm using the -k flag since I can't establish the connection otherwise. If I omit the flag I get:

The server successfully started, but we were unable to connect.
Original error message:
 connect ECONNREFUSED 192.168.1.116:9091

However, SSHing into the machine works just fine.

Ale-cc commented 7 years ago

Firstly ,check the information you login in. After I reinstalling the Atom ,I find it hard to connect the server. I fund it that update my .npmrc file for installing package(In China), registry=https://registry.npm.taobao.org/ Finally I can connect the server.

abhijits1234 commented 7 years ago

I am facing the same issue

JananiKSekar commented 6 years ago

I am facing the same issue, but i am getting this error: The server successfully started, but we were unable to connect. Original error message: Timeout after 60000 for id: 4182, Calling function FileSystemService/resolveRealPath.

I have to close atom again and reopen all the files I was working on, every time. Please prioritize and fix this.

francip commented 6 years ago

Remote connection with insecure server (nuclide-start-server -k) used to work in v0.280, and stopped working again in v0.282.

[Enter steps to reproduce:]

Install nuclide server v0.282 on remote remote machine (in my case: Raspberry Pi3 / Raspbian Stretch / Node.js v9.5.0)
Run Nuclide and attempt to connect to the remote server using 'nuclide-start-server -k' command

Atom: 1.23.3 x64 Electron: 1.6.15 OS: Mac OS X 10.13.3 Thrown From: nuclide package 0.282.0

Stack Trace

Uncaught Error: Not connected

At /Users/francip/.atompi/packages/nuclide/node_modules/ssh2/lib/client.js:983

Error: Not connected
    at Client.forwardOut (/packages/nuclide/node_modules/ssh2/lib/client.js:983:11)
    at SshHandshake._forwardSocket (/packages/nuclide/pkg/nuclide-remote-connection/lib/SshHandshake.js:275:22)
    at /packages/nuclide/pkg/nuclide-remote-connection/lib/SshHandshake.js:467:18)
    at emitOne (events.js:96:13)
    at Server.emit (events.js:188:7)
    at TCP.onconnection (net.js:1454:8)

Commands

     -1:36.9.0 tree-view:show (atom-workspace.workspace.scrollbars-visible-when-scrolling)
     -1:27.9.0 nuclide-remote-projects:connect (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-one-dark-syntax.theme-one-dark-ui)

Non-Core Packages

atom-beautify 0.30.9 
file-icons 2.1.16 
haskell-grammar 0.4.0 
highlight-selected 0.13.1 
jsonlint 1.1.4 
language-babel 2.83.1 
language-graphql 0.9.0 
language-haskell 1.17.3 
language-ini 1.19.0 
language-lua 0.9.11 
language-ocaml 1.9.5 
language-rust 0.4.12 
language-scala 1.1.9 
language-swift 0.5.0 
language-thrift 1.0.2 
linter-jsonlint 1.3.0 
MagicPython 1.0.12 
merge-conflicts 1.4.5 
nuclide 0.282.0 
nuclide-format-js 0.0.44 
pretty-json 1.6.4 
set-syntax 0.4.0 
sort-lines 0.18.0 
tool-bar 1.1.5

Lawris commented 6 years ago

Same issue on v0.284 (Client and Server).

p-t-u commented 6 years ago

Same issue. Nuclide is broken on Ubuntu 18.04 Beta, presumably due to changes in the Python packages.

"nuclide-start-server -k" causes the bug described here.

"nuclide-start-server" causes this other bug: https://github.com/facebook/nuclide/issues/1341

paulchill commented 6 years ago

This is driving me nuts, i've been trying to connect every day for the last 3 weeks.

I'm on windows with latest atom / nuclide and latest nuclide server on Ubuntu 16 i get the same

Error: Not connected at Client.forwardOut (C:\Users\Paul.atom\packages\nuclide\node_modules\ssh2\lib\client.js:983:11) at SshHandshake._forwardSocket (C:\Users\Paul.atom\packages\nuclide\pkg\nuclide-remote-connection\lib\SshHandshake.js:275:22) at Server. (C:\Users\Paul.atom\packages\nuclide\pkg\nuclide-remote-connection\lib\SshHandshake.js:467:18) at emitOne (events.js:96:13) at Server.emit (events.js:191:7) at TCP.onconnection (net.js:1486:8)

and ocasionally

Nuclide server cannot be reached at "https://localhost:57568". Nuclide will reconnect when the network is restored.

the folder appears in the remote window but i keep getting the first error

Does any one have any suggestions ??

facebookarchive / nuclide