Reply To: mt-daapd over HTTPS

#3525
Adar
Guest

I’d also like to point out that the reason my HTTP tunnel and ssh over it failed is because when you forward a port in ssh, it isn’t made available to other machines. So even though port 3689 was properly forwarded to my daapd server, my iTunes client was on a different machine than the one with the forwarded port, and so it couldn’t connect to that forwarded port. The solution is in using “-L *:3689:localhost:3689” when using -L to forward a port. This binds it to all interfaces, not just localhost, so other machines can connect to it.