3 ms·
THANK YOU! I still miss Serveo because this was easiest tunnel solution that "just works!"
by mobilio 6y ago
THANK YOU!
I still miss Serveo because this was easiest tunnel solution that "just works!"
- anderspitman 6y agoIf you want a self-hosted alternative to serveo, I recommend sish (comprehensive) or my own SirTunnel (simple and minimal). If you just need ad-hoc tunnels on someone else's servers for free, I'm not sure what the leading options are. localhost.run is one. [0]: https://github.com/antoniomika/sish https://github.com/antoniomika/sish [1]: https://github.com/anderspitman/SirTunnel https://github.com/anderspitman/SirTunnel
- tommyvan 6y agoI've seen a few servo refugees recently land on my service, https://localhost.run/ https://localhost.run/ I didn't get to try serveo before it ended but I _think_ I do something similar, "ssh -R 80:localhost:8080 ssh.localhost.run" will give you an internet accessible address tunneled to localhost:8080.
- tommyvan 6y agodoes anyone know what happened to serveo BTW? As happy as i am to welcome peeps onto localhost.run it's sad to see peeps in this space disappear, especially peeps that like SSH as much as I do. I read a medium article about serveo after it disappeared that suggested you could choose your own stable subdomain. localhost.run used to work like this but I got hammered by phishing sites, almost got shut down by my registrar and my hosting provider. I wonder if that was it? Stopping phishing is, by far, the thing I've had to do the most work on.
- mobilio 6y agoServeo author is Google employee and I THINK that there was some issues that service caused to him and his job. As i said - I THINK!