"Warning: The URL is the only authentication. Anyone with the link has full terminal access."<p>Could you make it so the URL is one-use only, such that once you've scanned it with your phone you can stop worrying because anyone else who uses it won't be able to start a session?
I can recommend tailscale for creating private networks. It has a generous free tier and would reduce the attack surface considerably compared to ngrok<p>Better yet would be setting up your own wireguard instance and not relying on free lunches. But as far as free lunches go tailscale would be my preferred option
Head scale is a good middle option - it uses Tailscale’s DNS system but you are able to control your network as you would with Wireguard
tailscale has a much better chance to work when you need it most. WireGuard is blocked by too much stuff.
Tailscale uses wireguard.<p>What it provides is a opinionated configuration management - which is admittedly great which is why I use it as well, but it's nonsensical to say tailscale works in places where wireguard is blocked.<p>You're likely just noticing the preconfigured nat traversal which tailscale provides and never set one up yourself, as you'd need a static IP for that and it's unconfigured by default.
> it's nonsensical to say tailscale works in places where wireguard is blocked<p>I have two machines on my desk, I configure a wg service on both. I also configure tailscale on both. Everything works.<p>I move one machine to another network, at a friend's place.<p>Wg does not work anymore. Tailscale works. So this is very much sensible to say what GP said.<p>Now, you can have all kinds of explanations about why wg dos not work and ts does, you know STUN, DERP, ts using wg under the hood, and whatnot but the facts are cruel: I cannot wg to my machine, but I can ts.
I was just pointing out that the statement wrt "wireguard being blocked while tailscale works" is nonsensical.<p>It remains nonsensical no matter how uninformed the user may be - even if he's proud of being such, as you seem to be.<p>This was not a discussion about what tool to use if the person doesn't know about networking and is generally ... "less technical".
Right, it’s that specific person’s Wireguard configuration, which is likely a typical one as a result of Wireguard‘s defaults. Tailscale‘s defaults work better, hence the surface-level impression that plain Wireguard does not work in cases in which Tailscale does.
As I said above - how would you set up plain Wireguard in a place without the possibility of exposing a port, or even that does not have a public IP - and initiate the connection from outside that place? I would love to learn something. Without rebuilding tailscale (or whatever other solutions with STUN or whatnot).
i think youre not hearing what - at least <i>i</i> - was saying.<p>I never said that running the same connectivity and NAT traversal via 2 nodes which are both inside of a NAT is possible.
Neither did I ever claim you dont need a static public IP which _isnt_ behind a NAT / has an open port.<p>With Tailscale, these are being provided to you by them.
Without them, you would have to maintain that yourself.
This is a significant maintenance burder, which is why I - as in my very first comment you yourself responded to - pointed out that the service theyre providing is great and that i use it myself for that as well.<p>Nonetheless, _if wireguard was blocked, tailscaile wouldn't work either_<p>But its not blocked. Hence tailscale works. Just like wireguard would work, if you configured NAT traversal in some way.
To get that working, you have multiple options, one of these being the STUN server.
Another being an active participants in the VPN which facilitates the connection (not just the initiation, which the STUN server would be doing). easier to configure and maintain, but less performant.<p>Tailscale themselves actually have an incredibly indepth article on how they've implemented it on their end, its a little aged at this point, but I suspect they havent changed much (if any) since<p><a href="https://tailscale.com/blog/how-nat-traversal-works" rel="nofollow">https://tailscale.com/blog/how-nat-traversal-works</a>
> i think youre not hearing what - at least i - was saying.<p>You said " it's nonsensical to say tailscale works in places where wireguard is blocked".<p>If by "blocked" you mean "blocked at the firewall level through some kind of adaptive block that will recognize a wireguard connection based on its behaviour/nature of packets/whatever" → then yes, of course tailscale will not work either as it uses wg under the hood.<p>If the OP message "tailscale has a much better chance to work when you need it most. WireGuard is blocked by too much stuff" means "I installed wireguard and it does not work (because whatever) but tailscale consistently delivers" → then it is not nonsensical at all. It is the right tool to start with.<p>> Tailscale themselves actually have an incredibly indepth article on how they've implemented it on their end<p>This is an excellent documentation to which I refer people as well.
> even if he's proud of being such, as you seem to be<p>Of course on Internet nobody knows you are a dog. But hey, I may be someone who wrote a part of the Linux kernel in 1994, ran IT operations for a company that was big (big!) and then almost vanished (not my fault :)) and produces open source that you may have even used if you are "technical" as you say.<p>And set up WG in so many places, including a frontend that unfortunately did not get the worldwide success it should have :)<p>With this modest introduction - tailscale works where wireguard does not. I am not sure why my example was not obvious. You can reach the machine at my friend's with tailscale, not with plain wireguard.
Of course if you open ports in the right places then yes! And check a few more things.<p>Now - how would you set up <i>plain</i> Wireguard in a place without the possibility of exposing a port, or even that does not have a public IP - and initiate the connection from outside that place? I would love to learn something. Without rebuilding tailscale (or whatever other solutions with STUN or whatnot).
I’ve never noticed wireguard be blocked by something, have you experienced this?
This is great. If you’re skeptical, vibe coding in the go is great because of how async the agentic coding workflows can be. Nothing like fixing a bug in the dentist office.<p>Lots of different technical solutions for how to do this, including the Claude and ChatGPT mobile apps nowadays. I use Tailscale. Choose what works best for you and enjoy.
I’m also vibing from the iphone. Termius connects via ssh to remote server where I run claude code. Ssh connects also over a wireguard connection. So ports are not an issue because they are all available via wg in a secure way. Additionally I have code server running there automatically port forwards and giving me ssl. So when I run “pnpm dev” in tmux in ssh then I access it via <a href="https://3000.dev.mydomain.com" rel="nofollow">https://3000.dev.mydomain.com</a> which works great for development.
> I wanted to vibe code from bed.<p>In this case, I think using Termux + SSH would be more convenient and compatible with all devices running sshd.
Yes but that's boring. Look at this it has cool ASCII and a QR. At this point no typing, just vibe-voice ask to build the thing and fix the error. Then we can have some tea, earl grey, hot.
I don't know if "more convenient" would be the words I would use. Setup on this project is very easy, it has very straightforward instructions. Meanwhile, I did a quick 5 minute pressure test of what you suggested and found myself with more questions than answers. I am not saying one way is better than the other, I am just thinking that for those that don't breathe SSH/VPN/Wireguard/Terminal Emulators/etc.. this project is actually far easier to understand.<p>Also, funny enough on compatibility, but "Termux" is not on iOS, so it fails that basic check. But there's alternatives, of course. Just an observation.
Also <a href="https://github.com/chriswritescode-dev/opencode-manager" rel="nofollow">https://github.com/chriswritescode-dev/opencode-manager</a> is getting there with a proper interface.
Love it, I've been looking for something like this for a while now. But please add a password to it if you have the time. I might chip in by next if you're open to contributions.
Genuine question here: How is this better than a mobile SSH client + something like Tailscale or Yggdrasil?
I wanted a secure solution, that still can be run in one command, and came up with this, <a href="https://gist.github.com/thomasht86/86f0f8f62db1839054abd8a7e501ff7d" rel="nofollow">https://gist.github.com/thomasht86/86f0f8f62db1839054abd8a7e...</a>
This command:<p><pre><code> lsb_release -cs
</code></pre>
Doesn't work for Linux Mint 22.2<p>What you want is UBUNTU_CODENAME from /etc/os-release (in the case of Linux Mint 22.2, it's "noble")<p>EDIT: Actually, I'm not even sure you can do $(command) inside /etc/apt/sources.list.d/*
I like this but I hate how everything has to be tied to AI now to get attention. “I wanted to vibe code-“ who cares? It’s a neat tool, do we have to force AI into it?
It’s the tool‘s use case, which provides valuable background information about its technical choices.
Normally we get a few "but why would you make this?" comments. Maybe let's not discourage people who actually give us the answer upfront.
Very cool, indeed.<p>One nit-pick: Terminus requiring a lot of setup work:<p>Terminus is trivial to use with a rented VPS. But, ptn solves a different problem
Love it.<p>Laziness - the mother of (most) invention.
[dead]
Further information concerning tunneling protocols, sshd/ ssh is accessible in the man site:<p>[1]:<a href="https://man.openbsd.org/sshd.8" rel="nofollow">https://man.openbsd.org/sshd.8</a><p>[2]:<a href="https://man.freebsd.org/cgi/man.cgi?ssh" rel="nofollow">https://man.freebsd.org/cgi/man.cgi?ssh</a>