Hello,

I stopped using TeamViewer a very long time ago. Since then, I’ve been using DWService and I’m quite happy with it. I like the fact that I can access to the terminal without launching any graphical component on the machine (which is handy for my headless servers, and allows me not to open SSH port). I also like the fact that it works even if my VPN server is down, as I can access remote servers that aren’t accessible via the web when they’re no longer reachable through my VPN.

However, there are a few issues that are bothering me more and more. I’ve switched my mum’s computer to Fedora and, whilst it worked perfectly under Windows, remote control is very buggy under fedora because the connection isn’t great. Furthermore, it’s impossible to access the screen if the computer isn’t unlocked.

So, I’d really like to find a solution that meets my criteria:

  • Accessible via a web browser
  • Ideally open-source
  • Free
  • Ideally self-hostable, but I’m worried that if, for example, my reverse proxy or VPN crashes, I won’t be able to access my machines to debug them?
  • Allows access to servers without a monitor
  • Allows access to computers running Fedora without the need for prior unlocking

Thanks!

  • Decronym@lemmy.decronym.xyzBEnglish
    1·
    3 hours ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    LXC Linux Containers
    SMB Server Message Block protocol for file and printer sharing; Windows-native
    SSH Secure Shell for remote terminal access
    VPN Virtual Private Network

    4 acronyms in this thread; the most compressed thread commented on today has 14 acronyms.

    [Thread #132 for this comm, first seen 16th Oct 2026, 18:50] [FAQ] [Full list] [Contact] [Source code]

    • Nik282000@lemmy.caEnglish
      2·
      1 day ago

      Guacamole in an LXC container and a virtual desktop in another.

      Requires no client side software, supports totp, lets me do remote admin on weird stuff like printers and home routers.

  • 7EP6vuI@feddit.orgEnglish
    5·
    1 day ago

    why don’t you want to open an ssh port? what’s wrong with that?

    just disable password authentication, and maybe get fail2ban. am i missing something?

    • neidu4@piefed.socialEnglish
      7·
      1 day ago

      Optional extra, which I do: Change the SSH port to something non-standard. It’s not more secure, but it does cut down on the logspam.

      • lntl@lemmy.mlEnglish
        11·
        1 day ago

        IMO ssh is the tool you’re describing. My ssh server is exposed to the WAN and is configured like this:

        • set to a random port to reduce spam (completely eliminated it for me)
        • set PasswordAuthentication no
        • set PermitRootLogin no
          • lntl@lemmy.mlEnglish
            5·
            1 day ago

            root is a user account that has all privileges and is what bots are programmed to probe, so exposing it introduces unnecessary risk. IMO there’s no reason to permit root login via ssh in any circumstance, ever, in all cases, absolutely.

            For all the people thinking, “well the world doesn’t work in absolutes, there’s always a special case!” There isn’t.

            If a user needs to use elevated permissions, there are many ways to do that without exposing root. sudo(8) is one way to do that.

            • DougPiranha42@lemmy.worldEnglish
              4·
              1 day ago

              Thanks for the great explanation! Seems like because logging in as root is never necessary and indeed never done; people confuse sudoer for root login.

            • 7EP6vuI@feddit.orgEnglish
              1·
              1 day ago

              do you use sudo with a password? this and the unknown username is what get as additional security then?

          • Guiorgy@lemmy.mlEnglish
            1·
            22 hours ago

            Without root user login, the attacker would have to guess not only the password to the user but also the username (hopefully it’s not something simple like admin), and once you are logged in you can use sudo -i to chage into root, which will require a password, therefore, we also disable password login so if someone does manage to somehow compromise the SSH user, they’d still need the password to become root.

            • 7EP6vuI@feddit.orgEnglish
              1·
              3 hours ago

              guess not only the password

              what password? shouldn’t we all use ssh-keys by now?

          • lewy@lemmy.worldEnglish
            1·
            1 day ago

            sudo -i is what I would do or su root if your other user is not a superuser.

      • Guiorgy@lemmy.mlEnglish
        1·
        22 hours ago

        You could spin a publicly exposed WireGuard daemon firewalled to allow peers access to the non-public SSH port only, which would result in double encryption, but would give you the peace of mind that an attacker would have to compromise both at the same time, which is very unlikely. Plus, WireGuard is very cheap to deploy and produces no logs. We use that model in my office to access our server.

        Edit: Otherwise, as others mentioned, you’d move the SSH daemon to a random port, disable password login and weaker keys and cyphers, setup Fail2ban, and optionally setup GeoIP blocking (only allow IPs from your region to connect).

  • cerothem@lemmy.caEnglish
    3·
    1 day ago

    For remote access I use two solutions that both have the features your looking for.

    The first one which I have used for longer than I can remember is MeshCentral https://github.com/Ylianst/MeshCentral

    This one works great, is web based, let’s you access a shell, or you can make port tunnels been agents, access RDP or vnc in the web UI, the file system etc.

    it’s a really great one stop shop that more than covers what you’re looking for.

    The second is RustDesk https://github.com/rustdesk/rustdesk with the betterdesk server and web UI https://github.com/UNITRONIX/BetterDesk

    This one scratched my TeamViewer itch and weekend pretty well. It’s newer than MeshCentral and not as easy to setup however on top of the web client it’s got apps which in my opinion provide a better experience for remote desktop access than MeshCentrals novnc client especially around copy paste.

    All in all, of your looking for something ultra easy I recommend MeshCentral, it’s minor quirks around novnc are so easy to overlook since it just works so well.

    If you want a modern TeamViewer then go with RustDesk/betterdesk but it’s newer and needs some extra work to get going.

    All these projects are open source, free, self hostable, has headless file and terminal access, and have web clients.

    For using Linux on any remote solution you pretty much have to run the desktop on x11 instead of Wayland. I don’t know if any software has found a great Wayland solution yet.

    • CodandChips @lemmy.mlEnglish
      1·
      23 hours ago

      Rustdesk seconded here, I found it fairly straightforward to setup on Mint. I previously had used TeamViewer and AnyDesk