blocks|key|190054|text|如果你使用的是Mac，重新启动DNS响应器可以帮我解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|190055|sudo+killall+-HUP+mDNSResponder|code-block|syntax|javascript|190056|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If you're on Mac, restarting the DNS responder fixed the issue for me.

<pre><code>sudo killall -HUP mDNSResponder
</code></pre>

blocks|key|189787|text|我在连接到远程机器时也遇到了同样的问题。但我设法登录如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|189788|ssh+-p+22+myName@hostname|code-block|syntax|javascript|189789|或者：|189790|ssh+-l+myName+-p+22+hostname|189791|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had the same issue connecting to a remote machine. but I managed to login as below:

<pre><code>ssh -p 22 myName@hostname
</code></pre>

or:

<pre><code>ssh -l myName -p 22 hostname
</code></pre>

blocks|key|4695952|text|在我的例子中，我是这样尝试ssh的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4695953|ssh+pedro@192.168.2.179:22+|code-block|syntax|javascript|4695954|当正确的格式为：|4695955|ssh+pedro@192.168.2.179+-p+22+|4695956|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

In my case I was trying ssh like this 

<pre><code>ssh pedro@192.168.2.179:22 
</code></pre>

when the correct format is: 

<pre><code>ssh pedro@192.168.2.179 -p 22 
</code></pre>

blocks|key|4695719|text|我也遇到了同样的问题，我可以通过向主机名ala+ssh+user@hostname.local添加一个.local来解决这个问题|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4695720|entityMap^0|O|N|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I had the same issue, which I was able to resolve by adding a .local to the host name, ala <code>ssh user@hostname.local</code>

blocks|key|190074|text|如果您的命令是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|190075|$+ssh+-p+1122++path/to/pemfile+user@[hostip/hostname]|code-block|syntax|javascript|190076|您还将面临同样的错误|190077|ssh:+Could+not+resolve+hostname+[hostname]:+nodename+nor+servname+provided,+or+not+known|190078|当您缺少ssh的选项-i+/path/to/pemfile时|offset|length|style|CODE|190079|因此命令应该是：|190080|$+ssh+-p+1122+-i+path/to/pemfile+user@[hostip/hostname]|190081|entityMap^0|0|0|0|0|A|J|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|10|8|@$M|11|N|12|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|14|8|@]|9|@]|A|$E|F]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

If your command is:

<pre><code>$ ssh -p 1122 path/to/pemfile user@[hostip/hostname]
</code></pre>

You will also face the same error 

<pre><code>ssh: Could not resolve hostname [hostname]: nodename nor servname provided, or not known
</code></pre>

when you miss the option <code>-i /path/to/pemfile</code> of ssh

So Command should be: 

<pre><code>$ ssh -p 1122 -i path/to/pemfile user@[hostip/hostname]
</code></pre>

blocks|key|4695669|text|我也遇到了同样的问题:在Preferences+->+Sharing+->+Remote+Login中显示的地址不起作用，我收到了一个'...nodename和servname都没有提供，或者未知‘。但是，当我手动编辑设置(在Preferences+->+Sharing+->+Remote+Login+->+edit中)并启用“使用动态全局主机名”时，它突然起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4695670|​|4695671|📷|atomic|offset|length|4695672|4695673|4695674|4695675|4695676|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/47ec866d504406e646565d28ed84163d.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/7fe2761190e351dd26751e1fce4cf425.png^0|0|0|0|1|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@$G|10|H|11|1|12]]|A|$]]|$1|I|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|K|3|E|5|F|7|15|8|@]|9|@$G|16|H|17|1|18]]|A|$]]|$1|L|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T|U|-4]]|V|$5|P|Q|R|A|$S|W|U|-4]]]]

I had the same problem: The address shown in Preferences -> Sharing -> Remote Login didn't work and I got a '... nodename nor servname provided, or not known'. However, when I manually edited the settings (in Preferences -> Sharing -> Remote Login -> edit) and enabled "Use dynamic global hostname", it suddenly worked.

<img src="https://i.stack.imgur.com/YEpYu.png" alt="enter image description here">

<img src="https://i.stack.imgur.com/FQYZf.png" alt="enter image description here">

blocks|key|190155|text|对我来说，问题出在我的~/.ssh/config文件上有一个拼写错误。我有：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|190156|Host+host1:
++HostName+10.10.1.1
++User+jlyonsmith|code-block|syntax|javascript|190157|问题出在host1之后的:+-它不应该在那里。对于~/.ssh/config文件中的拼写错误，ssh不会发出警告。当它找不到host1时，它会在本地查找机器，找不到它，并打印出隐秘的错误消息。|190158|entityMap^0|B|D|0|0|4|5|C|1|P|D|1B|3|1Q|5|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|N|$]]

For me, the problem was a typo on my <code>~/.ssh/config</code> file. I had:

<pre><code>Host host1:
 HostName 10.10.1.1
 User jlyonsmith
</code></pre>

The problem was the <code>:</code> after the <code>host1</code> - it should not be there. <code>ssh</code> gives no warnings for typos in the <code>~/.ssh/config</code> file. When it can't find <code>host1</code> it looks for the machine locally, can't find it and prints the cryptic error message.

blocks|key|190118|text|似乎有些应用程序不能读取符号链接的/etc/hosts+(至少在macOS上)，你需要硬链接它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|190119|ln+/path/to/hosts_file+/etc/hosts|190120|entityMap^0|H|A|0|0|X|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

It seems that some apps won't read symlinked <code>/etc/hosts</code> (on macOS at least), you need to hardlink it.

<code>ln /path/to/hosts_file /etc/hosts</code>

blocks|key|4695782|text|这发生在我试图访问Github的时候。问题是我有这样做的习惯：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4695783|git+remote+add+<xyz>+ssh:\\git@github.com......|offset|length|style|CODE|4695784|但是，如果您在问题中遇到此错误，删除ssh:\\可能会解决此问题。它为我解决了这个问题！|4695785|请注意，您必须执行git+remote+remove+<xyz>并在不使用ssh:\\的情况下重新添加远程url。|4695786|entityMap^0|0|0|1B|0|I|6|0|9|N|11|6|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@$D|V|E|W|F|G]|$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|M|$]]

This was happening to me when trying to access Github. The problem is that I was in the habit of doing:

<code>git remote add &lt;xyz&gt; ssh:\\git@github.com......</code>

But, if you are having this error from the question, removing <code>ssh:\\</code> may resolve the issue. It solved it for me!

Note that you will have to do a <code>git remote remove &lt;xyz&gt;</code> and re-add the remote url without <code>ssh:\\</code>.

blocks|key|4695756|text|考虑到您允许的端口，请尝试此操作。例如，将.pem文件存储在Documents文件夹中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4695757|现在要访问它，您所要做的就是使用cd+[directory]，它会将您移动到分配的文件所在的目录。您可以首先键入ls，以列出您当前所在的目录内容：|4695758|ls
cd+/Documents
chmod+400+mycertificate.pem
ssh+-i+"mycertificate.pem"+ec2-user@ec2-1-2-3-4.us-compass-0.compute.amazonaws.com+-p+80|code-block|syntax|javascript|4695759|entityMap^0|L|4|U|9|0|G|E|1K|2|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

Try this, considering your allowed ports. Store your <code>.pem</code> file in your <code>Documents</code> folder for instance.

To gain access to it now all you have to do is <code>cd [directory]</code>, which moves you to the directory of the allotted file. You can first type <code>ls</code>, to list the directory contents you are currently in:

<pre><code>ls
cd /Documents
chmod 400 mycertificate.pem
ssh -i "mycertificate.pem" ec2-user@ec2-1-2-3-4.us-compass-0.compute.amazonaws.com -p 80
</code></pre>

blocks|key|190185|text|我在ansible中使用了一个没有正确格式化的.yml清单文件，得到了这个错误。对于一个组中的多个主机，每个主机名都需要以硬冒号":“结尾。否则，ansible将主机名放在一起运行，并生成此ssh错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|190186|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got this error by using a .yml inventory file in ansible that was not properly formatted. For multiple hosts in a group, each hostname needs to end in a hard colon ":". Otherwise ansible runs the host names together and produces this ssh error.

blocks|key|190188|text|在使用remote-ssh插件测试Visual+Studio代码后，我也遇到了同样的问题。在设置远程主机的过程中，软件确实询问我将配置文件存储在哪里。我认为一个好的地方是'.ssh-folder‘(Linux-system)，因为它是一个ssh-remote配置。事实证明这不是一个好主意。第二天，在重新启动计算机后，我无法在远程服务器上通过ssh登录。错误消息是“无法解析主机名：.......名称或服务未知”。发生的情况是，从VSC卸载并没有删除这个配置文件，当然，它干扰了通常的过程。一个'rm‘之后问题被解决了(我确实删除了这个配置文件)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|190189|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem after testing Visual Studio Code with remote-ssh plugin. During the setup of the remote host the software did ask me where to store the config-file. I thought a good place is the '.ssh-folder' (Linux-system) as it was a ssh-remote configuration.
It turned out to be a bad idea. The next day, after a new start of the computer I couldn't logon via ssh on the remote server. The error message was 'Could not resolve hostname:....... Name or service not known'.
What happen was that the uninstall from VSC did not delete this config-file and of course it was than disturbing the usual process. An 'rm' later the problem was solved (I did delete this config-file).

I am trying to set up a VPN with a Raspberry Pi, and the first step is gaining the ability to <code>ssh</code> into the device from outside my local network. For whatever reason, this is proving to be impossible and I haven't the slightest clue why. When I try to <code>ssh</code> into my server with <code>user@hostname</code>, I get the error:

<pre><code>ssh: Could not resolve hostname [hostname]: nodename nor servname provided, or not known 
</code></pre>

However, I can log into the server with,

<pre><code>ssh user@[local IP]
</code></pre>

The server is a Raspberry Pi Model B running the latest distribution of Raspbian and the machine I am trying to connect to it with is a Macbook Pro running Mavericks. <code>ssh</code> was enabled on the Raspberry Pi when I set up Raspbian.

I have perused Stack Overflow for hours trying to see if anyone else had this problem and I have not found anything. Every <code>ssh</code> tutorial I find says that I should just be able to set it up on the remote machine and log in from anywhere using a hostname, and I have never had success with that.

ssh: Could not resolve hostname [hostname]: nodename nor servname provided, or not known

我正在尝试使用Raspberry Pi设置虚拟专用网，第一步是获得从我的本地网络外部通过ssh连接到设备的能力。不管是什么原因，这被证明是不可能的，我也不知道为什么。当我尝试用user@hostname ssh到我的服务器时，我得到了错误：ssh: Could not resolve hostname [hostname]: nodename nor servname provided, or n

问ssh:无法解析主机名[主机名]：提供的节点名或服务器名，或未知
EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ssh:无法解析主机名[主机名]：提供的节点名或服务器名，或未知EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ssh:无法解析主机名[主机名]：提供的节点名或服务器名，或未知
EN