I want to connect to my webserver, but the ssh is disabled, so decided to try using the webdisk service the server-provider suggested. My Nautilus though can't seem to be able to connect the davs server.
When I run it and ask to join it recognizes the davs address but when I press the "connect" button, it shows me an error saying: "unhandled error: cannot connect to destination (...)".
Whenever I try doing this as superuser though it doesn't even let me click on the connect button saying: "This file server type is not recognized."
I thought it might be due to some packages missing to handle davs connections. Can it be the problem? I'm using Nautilus 3.10.1 on Deepin Linux (which uses the ubuntu repositories). Can anyone tell me what packages do I need to install, or how do I get this working?
I'm quite sure you've found the answer yourself since Jan 2016, but for the sake of others who may search for the answer, I'll say it:
Make sure you have davfs2 package installed.
Related
I have a problem since yesterday, I made the error of uninstalling Nodejs to put the latest version (14.17.2 LTS OR 16.4.1 Current) and since I have this error ... I do not understand, this is my personal pc and I am the admin (normally) I do not understand either how to solve this problem and in the meantime I can no longer work ...
I've been looking for solutions since yesterday but can't find what I need to do to fix it ..
(PS: excuse my English, I'm French)
I attach you the capture of my administrator account
Windows 10
Error Nodejs
administrator account
MAJ 06/july/2021:
I finally managed to cheat the thing, downloaded the Nodejs ZIP folder, and put it straight to my hard drive and it worked.
Open Command Prompt (cmd.exe) as administrator and type or copy/paste:
net localgroup /add "Authenticated Users"
Then click the "Retry" button or run the installation file again.
I am using the Remote-ssh extension with VS Code (Insiders) to connect to an AWS Linux server. This connection is authenticated with a SSH key stored on my local machine. After I connect, a terminal titled "install" is opened and the following is the output:
685ad2d6d150: running
Acquiring lock on /home/ubuntu/.vscode-server-insiders/bin/45aafeb326d0d3d56cbc9e2932f87e368dbf652d/vscode-remote-lock.ubuntu.45aafeb326d0d3d56cbc9e2932f87e368dbf652d
Found existing installation at /home/ubuntu/.vscode-server-insiders/bin/45aafeb326d0d3d56cbc9e2932f87e368dbf652d...
Checking /home/ubuntu/.vscode-server-insiders/.45aafeb326d0d3d56cbc9e2932f87e368dbf652d.log and /home/ubuntu/.vscode-server-insiders/.45aafeb326d0d3d56cbc9e2932f87e368dbf652d.pid for a running server
Looking for server with pid: 79962
Found running server...
*
* Reminder: You may only use this software with Visual Studio family products,
* as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057)
*
Checking server status on port 45093 with wget
685ad2d6d150: start
SSH_AUTH_SOCK====
DISPLAY====
webUiAccessToken====
listeningOn==45093==
osReleaseId==ubuntu==
arch==x86_64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
extInstallTime====
serverStartTime====
connectionToken==86be68cd-ee77-49dc-ae26-5c1521022c2c==
685ad2d6d150: end
(this print is after the initial install and reconnecting to the server, but the output is about the same)
Afterwards the "install" terminal remains open. If I close it, then it seems my connection is interrupted and trying to open a file, or another Bash terminal reopens the install terminal.
If I open a direct connection to the user directory, I get the following warning:
If I open a connection from within a git repository directory I don't get that warning.
My question is, is the vscode-server-insiders "install" finished? Is the "install" terminal supposed to remain open the entire time? If I close the "install" terminal, is it supposed to break the connection and reopen? Is the warning that shows up because I am not in a git repository directory? Should I be getting that warning? Or is this all the normal process of remotely connecting via ssh with VS Code?
Sorry, I have Googled, but have not seen anything referencing that this is the regular behavior of using the Remote-ssh extension. I feel like if the vscode-server-insiders installation was completed that the "install" output in the terminal should go away. But it seems to hang after the connectionToken==86be68cd-ee77-49dc-ae26-5c1521022c2c==4134564d6c5d: end output. Just trying to figure out if this is indeed what is supposed to happen.
UPDATE 1: As mentioned by #VonC, it appears that the install process is indeed hanging. I had already looked at the Troubleshooting hanging or failing connections documentation and added "remote.SSH.showLoginTerminal": true, "remote.SSH.useLocalServer": false to my settings file, but it doesn't seem to make a difference. Nothing shows up in the output log for the Remote-ssh extension. There are a lot of pty errors in the developer's console, but nothing else that looks like it could be making the install process hang. So, does anyone have any clues as to why the install process is hanging?
UPDATE 2: Setting remote.SSH.showLoginTerminal to false doesn't show the "install" terminal at all. But is this hiding the terminal and the issue, or is this actually solving the issue? It appears that the "Checking server status..." step was what was hanging in the process, but I could still use a bash terminal and open files. I can also still do all that with remote.SSH.showLoginTerminal set to false. I am using a ssh key and I am not using a password to login. I guess now I am more curious as to what is really going on here and making sure that there are no problems that are just being hidden by this setting.
I set remote.SSH.showLoginTerminal: false in the VS Code settings and it either hides these warnings or it gets rid of them. I am not sure. So, while I don't know why these warnings occurred, or if this setting really "fixed" it, I am going to say this is solved because nothing is blocking my use of the SSH Remote features of VS Code, and I am no longer getting annoying warnings.
The "Extensions want to make changes" part does not seem linked to microsoft/vscode-remote-release, but is more a VSCode warning, as shown in microsoft/vscode issue 108940, still opened in issue 96699.
Closing the install terminal does not terminate the session, but check settings, as seen in the "Troubleshooting hanging or failing connections": something like "remote.SSH.showLoginTerminal" could have bearing on what you see.
The OP Charles Williams confirms having set "remote.SSH.showLoginTerminal" to false, which seems to resolve (or hide?) the issue.
I met the same problem as yours. At last, I found this problem happened because I used both MobaXterm and vscode to connect the remote host at the same time. When I closed MobaXterm ssh connection, the problem in vscode was solved.
Allowing the editor to install random undocumented code onto every remote server you access is very odd.
I've spent a fair amount of time going through the current (Aug 2022) VS Code 3rd-party extensions to find a less-invasive alternative, and the most straightforward seems to be "ftp-simple" which uses the common technique of using (s)ftp as the file-io method to the remote server allowing you to browse the file system, open file, edit, save pretty much as you would do on the local file system.
Some other VS Code 3rd-party (s)ftp extensions use the heavyweight 'synchronize workspace' model where your client copies the entire directory tree below your 'remote folder' assuming it's a 'project', and then keeps that local copy in sync with the server. This works ok for developers working on small projects (although frankly Git would be better) but doesn't fit the sysadmin ad-hoc file edits I might need to do. Another hiccup is some extensions allow you to edit a remote FILE, but don't integrate browsing the remote file system, so you have to specify the complete filename for the file you want to edit.
SFTP is a good fit for remote file editting because the editor file i/o is basically 'browse filesystem', 'read entire file', 'save entire file' which maps to sftp fine, and the clear delineation between the editting and the file read/write makes the remote access less vulnerable to connection issues.
I am working my way through 'The linux command line' (http://linuxcommand.org/tlcl.php) . Since I don't have a local linux environment and I have to work in windows , I am telnetting into an Ubuntu 14.4 LTS instance on EC2 , with putty. On page 114 , when I run the xlogo command I get:
ubuntu#ip-172-31-22-65:~$ xlogo
Error: Can't open display:
How can I get this working?
xlogo will try to access the current Xserver to display a logo. If you're telneting to a box, you will not have an X server available, which is what that "can't open display" message is saying. It's trying to look at your DISPLAY environment variable to use that to show the logo on, but you don't have a display to use, and thus have nothing in your DISPLAY variable.
You will need access to an X server somewhere to do that step. One option would be to install cygwin on your Windows machine. Then you wouldn't need the remote linux box for most steps I imagine, because you could just use your local cygwin environment. Even if you want to use the remote box still, if you use cygwin and launch an xterm with it, you could ssh -X <host> and that will export your DISPLAY to that remote machine so it can display back on your windows machine.
As I mentioned in the comment under Eric Renouf answer, I am working thru the same book. That part of the book have some testing of creating users, groups, shifting users, group permissions etc. I found that I needed to log the same user out quite some times. The last time logging that user out, I got a message saying xlogo is terminatet, like it was hanging on that user?
After everyone was logged out, I logged in as sudo and everything worked again.
I have recently spun up a new Ubuntu 12.04 instance in AWS. I had no issues connecting to and opening an SSH terminal to the server. Having connected to the instance, I was able to install the Ubuntu desktop and FreeNX without any problem, as well as enabling password authentication on the server instance.
I downloaded and installed the NX Client for Windows on a PC running Windows 8. After entering the user credentials I can connect to and authenticate into the server. I'm brand new to the Linux world, but at this point everything was going so smoothly I was about ready to throw my Windows licenses to the dogs - good thing I held off on that.
"Problem: At the client, the !M logo window appears, but after a few seconds that window just closes, even without showing any error message."
That problem statement is in quotes because it's precisely the issue described in FreeNX Ubuntu Community support documentation https://help.ubuntu.com/community/FreeNX#Troubleshooting.
So naturally I follow the solution in the guide:
"Solution: The issue is due custom VNC configuration. In the server, access your home directory and run these commands,"
sudo rm .Xauthority*
touch .Xauthority
chmod 600 .Xauthority
Unfortunately, this did absolutely nothing to resolve the issue. The problem would be easier to diagnose if I had an error message, but reference the Problem statement, there is no error message to be had. Several hours of googling yielded nothing, so wondering if anyone here has encountered this problem in the past, and if so, they would be willing to help.
Thanks!
I am trying to install Cygwin on someone's computer. During the setup, when
the window with the websites to get cygwin from shows up, it's empty. I tried
typing some links, that I know work (tried it on another machine) and they don't work - getting an error message. (something about not being to get the .ini ... )
Any ideas?
If the list of websites isn't being populated, Setup.exe is unable to get to the internet. Make sure you are connected (including checking your Proxy settings) and try again.