# Routing SSH traffic with Traefik v2

**URL:** <https://community.traefik.io/t/routing-ssh-traffic-with-traefik-v2/717>\
**Category:** Traefik v2\
**Tags:** tcp\
**Created:** [July 1, 2019, 3:51pm UTC](https://community.traefik.io/t/routing-ssh-traffic-with-traefik-v2/717 "2019-07-01T15:51:02Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![csarn](https://avatars.discourse-cdn.com/v4/letter/c/919ad9/32.png) [@csarn](https://community.traefik.io/u/csarn)\
**Post date:** [December 19, 2019, 2:21pm UTC](https://community.traefik.io/t/routing-ssh-traffic-with-traefik-v2/717/12 "2019-12-19T14:21:14Z")

</div>

Hi! I'm a bit late to the party, but found this via google, trying to do the same thing.  
For those who have not found a suitable solution, maybe you could use sslh, which is an ssh/tls multiplexer. I have it working and just wanted to see whether I can skip sslh from now on, now that I found traefik. So the answer is no, I'll be using sslh together with traefik.

sslh can distinguish several protocols and forward connection attempts to the configured handler:  
ssh, openvpn, tinc, xmpp, http, tls, ssl, adb, socks5, other.

You can find it at [https://github.com/yrutschle/sslh](https://github.com/yrutschle/sslh) or in the repo of the linux distribution of your choice.

---

_[View the full topic](https://community.traefik.io/t/routing-ssh-traffic-with-traefik-v2/717)._
