使用 Tailscale 和 Beszel 保护我的服务器并了解其功能
4 分•作者: SyedFazil•11 天前
我最近花了一个周末来改进我的VPS设置，结果比我预期的学到了更多关于网络知识的东西。
我有两个一直困扰我的问题：
我的SSH端口仍然暴露在互联网上。我知道基于密钥的身份验证通常是安全的，但我一直不喜欢让它保持开放。
我没有简单的方法来知道某个服务是否崩溃，或者我的VPS实际使用了多少CPU、内存或磁盘空间，而且我不想每次都SSH进去查看情况。
我最终的解决方案是Tailscale + Beszel。
在设置过程中，我深入研究了Tailscale在底层如何与WireGuard、NAT打洞、DERP中继协同工作，以及SSH如何仍然可以通过基于UDP的VPN工作。
我将学到的所有内容都写成了一篇博客文章，其中包含设置Tailscale和Beszel的详细指南。
https://syedfazil.dev/blogs/tech/tailscale-beszel-vps/
我希望帮助任何遇到同样问题的人，并寻求有经验人士的反馈。
查看原文
I recently spent a weekend improving my VPS setup, and I ended up learning a lot more about networking than I expected.<p>I had two problems that kept nagging me<p>My SSH port was still exposed to the internet. I know it's generally safe with key-based authentication, but I never liked leaving it open.<p>I had no easy way to know if a service had crashed or how much CPU, RAM, or disk space my VPS was actually using and I didn't want to SSH into it to see what's happening everytime.<p>The solution I ended up with was Tailscale + Beszel.<p>While setting it up, I went down a rabbit hole learning how Tailscale works under the hood with WireGuard, NAT hole punching, DERP relays, and how SSH still works over a UDP based VPN.<p>I wrote everything I learned into a blog post with a detailed guide on setting up Tailscale and Beszel.<p>https://syedfazil.dev/blogs/tech/tailscale-beszel-vps/<p>I am looking to help anyone who is facing the same problem and for feedback from experienced folks