<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: failed to connect to cloudera EDH on AWS via ssh tunnel in Putty in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/failed-to-connect-to-cloudera-EDH-on-AWS-via-ssh-tunnel-in/m-p/63397#M73146</link>
    <description>&lt;P&gt;&amp;nbsp;found the solution.&lt;/P&gt;&lt;P&gt;1) port forwarding should be defined in the PuTTy interface: ssh -&amp;gt;auth-&amp;gt;tunneling&lt;/P&gt;&lt;P&gt;2) need to enable the inbound rule to include TCP traffic&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 08 Jan 2018 01:45:23 GMT</pubDate>
    <dc:creator>fayyil</dc:creator>
    <dc:date>2018-01-08T01:45:23Z</dc:date>
    <item>
      <title>failed to connect to cloudera EDH on AWS via ssh tunnel in Putty</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/failed-to-connect-to-cloudera-EDH-on-AWS-via-ssh-tunnel-in/m-p/63355#M73145</link>
      <description>&lt;P&gt;Hello there,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am fairly new with&amp;nbsp;unix&amp;nbsp;command. Could someone help me with this?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I was trying to ssh into my cloudera&amp;nbsp;EDH instance,&amp;nbsp;following the&amp;nbsp;instruction&amp;nbsp;&lt;A href="https://docs.aws.amazon.com/quickstart/latest/cloudera/step3.html" target="_self"&gt;here&lt;/A&gt;. I think I got the ssh established to port 7189. However, I still cannot connect to cloudera&amp;nbsp;manager from my local browser, and it gives me 'refuse to connect' error.&lt;/P&gt;
&lt;P&gt;I am running Putty on a windows machine. here is the putty log:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;[ec2-user@ip-172-31-10-233 ~]$ ssh -i /home/ec2-user/cloudera/setup-default/main_key.pem -L 7189:localhost:7189 ec2-user@ec2-35-182-66-141.ca-central-1.compute.amazonaws.com&lt;BR /&gt;Last login: Fri Jan 5 14:21:06 2018 from ip-172-31-10-233.ca-central-1.compute.internal&lt;BR /&gt;[ec2-user@ip-172-31-10-233 ~]$ netstat -lep --tcp&lt;BR /&gt;(Not all processes could be identified, non-owned process info&lt;BR /&gt;will not be shown, you would have to be root to see it all.)&lt;BR /&gt;Active Internet connections (only servers)&lt;BR /&gt;Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name&lt;BR /&gt;tcp 0 0 0.0.0.0:49742 0.0.0.0:* LISTEN cloudera-director 30148 -&lt;BR /&gt;tcp 0 0 0.0.0.0:7189 0.0.0.0:* LISTEN cloudera-director 29664 -&lt;BR /&gt;tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN root 19193 -&lt;BR /&gt;tcp 0 0 localhost:smtp 0.0.0.0:* LISTEN root 16298 -&lt;BR /&gt;tcp6 0 0 localhost:7189 [::]:* LISTEN ec2-user 281332 4203/ssh&lt;BR /&gt;tcp6 0 0 [::]:ssh [::]:* LISTEN root 19195 -&lt;BR /&gt;tcp6 0 0 localhost:smtp [::]:* LISTEN root 16299 -&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;process 4203 is already running, I assume that is the ssh tunnel i just created? but i still cannot access to &lt;SPAN&gt;&lt;A href="http://localhost:7189/" target="_blank"&gt;http://localhost:7189/&lt;/A&gt;&amp;nbsp;on&amp;nbsp;chrome&amp;nbsp;nor&amp;nbsp;firefox&lt;/SPAN&gt;. What is the issue here?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thank you so much for the help.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 12:42:20 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/failed-to-connect-to-cloudera-EDH-on-AWS-via-ssh-tunnel-in/m-p/63355#M73145</guid>
      <dc:creator>fayyil</dc:creator>
      <dc:date>2022-09-16T12:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: failed to connect to cloudera EDH on AWS via ssh tunnel in Putty</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/failed-to-connect-to-cloudera-EDH-on-AWS-via-ssh-tunnel-in/m-p/63397#M73146</link>
      <description>&lt;P&gt;&amp;nbsp;found the solution.&lt;/P&gt;&lt;P&gt;1) port forwarding should be defined in the PuTTy interface: ssh -&amp;gt;auth-&amp;gt;tunneling&lt;/P&gt;&lt;P&gt;2) need to enable the inbound rule to include TCP traffic&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 01:45:23 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/failed-to-connect-to-cloudera-EDH-on-AWS-via-ssh-tunnel-in/m-p/63397#M73146</guid>
      <dc:creator>fayyil</dc:creator>
      <dc:date>2018-01-08T01:45:23Z</dc:date>
    </item>
  </channel>
</rss>

