jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Remove the url prefix from links in website (#5013)

Browse source
This commit is contained in:
Paulus Schoutsen 2018-03-24 21:21:09 -07:00 • committed by GitHub
parent c29501ddbd
commit d3fc349b50
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
64 changed files with 2506 additions and 2506 deletions
Download patch file Download diff file Expand all files Collapse all files

12
source/_posts/2017-11-02-secure-shell-tunnel.markdown
View file

@ -13,7 +13,7 @@ og_image: /images/blog/2017-11-ssh/social.png
Most system engineers are very familiar with [SSH (Secure shell)](https://en.wikipedia.org/wiki/Secure_Shell). This tool which contains a server part and a client part is used to access a remote system in a secure way. It can also help you if your are running Home Assistant but don't want to expose it to the public. On a Linux system SSH is often available by default. If you are using a Windows installation additional steps are required which are not covered here.
In this blog post we are going to use the tunneling option of SSH to create a secure connection and forward the Home Assistant frontend to a local system.
In this blog post we are going to use the tunneling option of SSH to create a secure connection and forward the Home Assistant frontend to a local system.
<!--more-->
@ -22,7 +22,7 @@ The involved parties are:
- **Remote system**: Where Home Assistant is running, usually in your home network.
- **Local system**: Where you want to see the frontend.
The prerequirements are that you need to allow the forwarding of port 22 from your router to the system where Home Assistant is running in your network. It might also be needed that you enable the SSH daemon by `$ sudo systemctl start sshd` on the remote system and to adjust the host firewall. If you are running [Hass.io](https://home-assistant.io/hassio/) then enable the [SSH Server add-on](https://home-assistant.io/addons/ssh/). You must also have a public IP address or hostname which can be provided by dynamic DNS (e.g., [NO-IP](https://www.noip.com/) or [DuckDNS](https://www.duckdns.org/)).
The prerequirements are that you need to allow the forwarding of port 22 from your router to the system where Home Assistant is running in your network. It might also be needed that you enable the SSH daemon by `$ sudo systemctl start sshd` on the remote system and to adjust the host firewall. If you are running [Hass.io](/hassio/) then enable the [SSH Server add-on](/addons/ssh/). You must also have a public IP address or hostname which can be provided by dynamic DNS (e.g., [NO-IP](https://www.noip.com/) or [DuckDNS](https://www.duckdns.org/)).
On your local system you need only a SSH client and you need to be in a network where SSH is allowed.
First let's have a look at the command we are going to use. Use `man ssh` to get more information.
@ -38,7 +38,7 @@ $ ssh -L 8000:localhost:8123 user@[IP_ADDRESS_REMOTE]
|_ We want to do local port forwarding.
```
A possible example could look like the command below.
A possible example could look like the command below.
```bash
$ ssh -L 8000:localhost:8123 ha@192.168.0.11
@ -50,11 +50,11 @@ The first time you establish the connection you need to accept the fingerprint.
The authenticity of host '192.168.0.11 (192.168.0.11)' can't be established.
ECDSA key fingerprint is SHA256:asdf2faasd4gk45454fadr78wfadfasdfeg4vvvsae33.
ECDSA key fingerprint is MD5:44:d4:f7:44:d4:aa:b8:de:ef:09:3e:0d:4e:12:11:09.
Are you sure you want to continue connecting (yes/no)?
Are you sure you want to continue connecting (yes/no)?
Warning: Permanently added '192.168.0.162' (ECDSA) to the list of known hosts.
ha@192.168.0.11's password:
ha@192.168.0.11's password:
Last login: Fri Oct 27 17:50:09 2017
[ha@home-assistant ~]$
[ha@home-assistant ~]$
```
Now you are able to use your frontend on your local system: [http://localhost:8000](http://localhost:8000)