I am working on a vscode-remote-ssh session. On my server, I launch a jupyter notebook that I then access on vscode through the remote-ssh session but connecting to my compute node.
Everytime I reload a project window, VSCode gives me a warning that I am connecting to an insecure connection (which is fine for me). After clicking yes, I need to enter the password everytime.
Is there a way to make VSCode remember the password for a jupyter connection? My browser seems to do it just fine.
I have tried using an https connection but I do not have a certified ssl certificate so VScode doesn't work on that. That's why I am using an insecure connection with just a password.
Related
I've installed xquartz on my OSX machine, and upon connecting to a remote server with ssh -X user#server.domain I'm able to launch gui windows (let's say Rstudio for example --I see the window show up on my screen even though it's running on the remote server -neato!).
What I'd like to do is create stable, persistent sessions to disconnect/reconnect to (i.e. close and re-open the same window with my environment and variables still there, instead of closing it and opening another one).
Hence, I'm using a tmux session from the terminal so that I can detach from my ssh connection to the server and connect back later. What I'd like to do then is re-launch the gui windows that I started from that session previously. Unfortunately, I don't know how to "store" or "detach" from the GUI windows once they are created --if I close them, then the unsaved data is deleted and the session is lost.
Is there a way to launch a persistent window from within ssh -X, and then "hide" that window, and re-open it after connecting again later?
Not sure if this will still help now but I'll put it here for posterity. For the specific RStudio case you'd be better off installing a server version of RStudio - either the paid RStudio Workbench or the free open-source version. The server versions provide the persistent sessions you're looking for, including for long-running jobs.
The open source version has a login, but all passwords are sent in unencrypted - don't expose it to the internet without other protections. In the open-source version you can only have one session per user.
Even without allowing access to the public internet you could forward port 8787 over ssh ( -L 8787:localhost:8787) & log into the remote RStudio Server instance from your local browser by visiting localhost:8787.
I'm trying to use Google's Colab feature to connect to a remote run-time that is configured with HTTPS. However, I only see an option to inform the port on the UI, not the protocol.
I've checked the Network panel and the website starts a WebSocket connection with http://localhost:8888/http_over_websocket?min_version=0.0.1a3, HTTP-style.
Full details of my setup:
I have a public Jupyter server at https://123.123.123.123:8888 with self-signed certificate and password authentication
I've followed jupyter_http_over_ws' setup on the remote
I started the remote process with jupyter notebook --no-browser --keyfile key.pem --certfile crt.pem --ip 0.0.0.0 --notebook-dir notebook --NotebookApp.allow_origin='https://colab.research.google.com'
I've created a local port forwarding with ssh -L 8888:localhost:8888 dev#123.123.123.123
I've turned on network.websocket.allowInsecureFromHTTPS on Firefox
I've went to https://localhost:8888 and logged in
Naturally, when the UI calls http://localhost:8888/http_over_websocket?min_version=0.0.1a3 it fails. If I manually access https://localhost:8888/http_over_websocket?min_version=0.0.1a3 (note the extra s) it gets through.
I see three options to solve it:
Tell the UI to use secure WS connection
Run a proxy on my local machine to transform the HTTPS into plain HTTP
Turn off HTTPS on my remote
The last two I think will work, but I wouldn't like that way.
How to do #1?
Thanks a lot!
Your option 1 isn't possible in colab today.
Why do you want to use HTTPS over an SSH tunnel that already encrypts forwarded traffic?
I use cyberduck for SFTP my website files to the server. Dreamhost is the server.
In setting up a new bookmark in cyberduck I received this error "Connection failed - EOF while reading packet." [end of file]
The website is up and working fine, http://ce-t.org
Initially I thought this error had to do with the connection opening with cyberduck. So I setup a different bookmark to test and was able to do without a problem.
I have also deleted my first attempt to setup and reset up. This did not alter anything.
Now after doing more reading, may be in one of the website files?
As you can see i am a novice.
Help appreciated.
Usually when I run into this issue, its because my pw has expired.
Try SSHing into the server and change/update your pw. After I change it, I can FTP in.
This is 3 years too late for the OP. But I had this error when trying to make an SFTP connection to hosting on a Plesk server and the solution was to:
Enable the 'Access to the server over SSH' setting for the ftp user via the Plesk Control panel.
Of course you might need to contact your hosting service to get this done if you are not managing your own server.
In my case the same error occurred due to a syntax error in the .bashrc file on the remote server.
Also note that the default account setting for an FTP user at Dreamhost might specify an FTP connection. If so, trying to use Cyberduck to connect via SFTP will generate this error message. You can use the Dreamhost control panel to edit the user's record to specify SFTP.
In my case I have used dropbear ssh server.
I replace this server with openssh server, and now i can open the sftp connection without any issues.
I have a droplet on DigitalOcean with SSH key created.
My SSH and SFTP access work perfectly with Mac OSX Terminal and Transmit.
But for some reason SFTP does not work with PHPSTORM :
Error
Connection to 'ipaddress' failed
SSH_MSG_DISCONNECT: 2 Too many authentication failures for root
I had the same problem, after a while looking for ssh keys and others non working ideas I was just using a root user which just could not access to server
The error message was buggy, it appear for ssh issues and also user issues :-(
I am trying out Eldos's SFTP Net Drive to map a drive to a virtual Ubuntu server. I works great when authenticating with a password. I have tried the normal/typical methods for configuring Key-based access. However, I receive error 10058. I have searched for clear instructions without success.
Anyone using this with Key-based access? Please share how you have it configured.
Thank you :)
If you're connecting via command line (e.g. using "open /profile:server" command line arguments) and you're accessing recently reinstalled server, the connection will silently fail because of changed server ssh fingerprint.
Try to reconnect manually (not using command line), accept new fingerprint and the problem will resolve.
This is because the server doesn't accept the key for whatever reason and closes connection. Usually this is an indicator of buggy server which normally should send the error packet in response.
But your question is offtopic here on StackOverflow.