• bluGill@kbin.social
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    10 months ago

    Nothing is exposed. There are things I want exposed, but I don’t want to keep security patches up to date, even if there is a zero day. I’m looking for someone trustworthy to hire for things that it would be useful to expose, but they are hard to find.

  • Justin@lemmy.jlh.name
    link
    fedilink
    English
    arrow-up
    3
    ·
    10 months ago

    There’s a wid range of opinions on this. Some people only access their services via tunnel, some people open most of their services up to the internet, as long as they’re authenticated. One useful option for https services is to put them behind a reverse proxy that require oauth authentication, which allows you to have services over the internet, without increasing your attack surface. But that breaks apps like Nextcloud and Lemmy, so it’s not a universal option.

    • BearOfaTime@lemm.ee
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      edit-2
      10 months ago

      Tailscale with the Funnel feature enabled should work for most ISPs, since it’s setup via an outbound connection. Though maybe they’re Super Cunts and block that too.

  • Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    10 months ago

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

    Fewer Letters More Letters
    DNS Domain Name Service/System
    HA Home Assistant automation software
    ~ High Availability
    HTTP Hypertext Transfer Protocol, the Web
    HTTPS HTTP over SSL
    IMAP Internet Message Access Protocol for email
    IP Internet Protocol
    NAS Network-Attached Storage
    NAT Network Address Translation
    Plex Brand of media server package
    SMTP Simple Mail Transfer Protocol
    SSH Secure Shell for remote terminal access
    SSL Secure Sockets Layer, for transparent encryption
    TLS Transport Layer Security, supersedes SSL
    VPN Virtual Private Network
    VPS Virtual Private Server (opposed to shared hosting)
    nginx Popular HTTP server

    15 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.

    [Thread #549 for this sub, first seen 26th Feb 2024, 21:45] [FAQ] [Full list] [Contact] [Source code]

  • ultorpha@lemmy.nz
    link
    fedilink
    English
    arrow-up
    4
    ·
    10 months ago

    Unlike most here, I’m not as concerned with opening things up. The two general guidelines I use are 1. Is it built by a big organization with intent to be exposed, and 2. What’s the risk if someone gets in.

    All my stuff is in docker, so compartmentalized with little risk of breaking out of the container. Each is on it’s own docker network to the reverse proxy, so no cross-container communication unless part of the same stack.

    So following my rules, I expose things like Nextcloud and Mediawiki, and I would never expose Paperless which has identity documents (access remotely via Tailscale). I have many low-risk services I expose on demand. E.g. when going away for a weekend, I might expose FreshRSS so I can access the feed, but I’d remove it once I got home.

      • ultorpha@lemmy.nz
        link
        fedilink
        English
        arrow-up
        2
        ·
        10 months ago

        I’ve never known a reason to expose the docker socket to Nextcloud. It’s certainly not required, I’ve run Nextcloud for years without ever granting it socket access.

        Most of the things on that linked page seem to be for Docker rather than Nextcloud, and relate to non-standard configuration. As someone who is not a political target, I’d be pretty happy that following Nextcloud’s setup guide and hardening guide is enough.

        I also didn’t mention it, but I geoblock access from outside my country as a general rule.

        • jkrtn@lemmy.ml
          link
          fedilink
          English
          arrow-up
          2
          ·
          10 months ago

          I was looking into setting up Nextcloud recently and the default directions suggest exposing the socket. That’s crazy. I checked again just now. I see it is still possible to set it up without socket access, but that set of instructions isn’t as prominent.

          I linked to Docker in specific because if Nextcloud has access to the socket, and hackers find some automated exploit, they could easily escalate out of the Docker container. It sounds like you have it more correctly isolated.

          • ultorpha@lemmy.nz
            link
            fedilink
            English
            arrow-up
            2
            ·
            10 months ago

            Was it Nextcloud or Nextcloud All in One? I’ve just realised that the Nextcloud docker image I use is maintained by Docker, not Nextcloud. It’s this one: https://hub.docker.com/_/nextcloud/

            I use Docker-compose and even the examples there don’t have any socket access.

            The all in one image apparently uses Traefik, which seems weird to use an auto configuring reverse proxy for an all in one image where you know the lay of the land. Traefik requires access to the docker socket for auto configuration. But you can proxy the requests to limit access to only what it needs if you really want to use it.

            • jkrtn@lemmy.ml
              link
              fedilink
              English
              arrow-up
              2
              ·
              10 months ago

              What I was looking at was the All in One, yes. I didn’t realize there was a separate maintained image, thank you! I’d much rather have a single image without access to the socket at all, I’ll give that a shot sometime.

              • ultorpha@lemmy.nz
                link
                fedilink
                English
                arrow-up
                1
                ·
                10 months ago

                One warning: in my experience, you can not jump two major versions. Not just it won’t work, but that if you try it everything will break beyond repair and you’ll be restoring from a backup.

                Two major versions can sometimes be a matter of a few months apart, so make sure you have a regular update schedule!

                (Also, people say never update to a X.0 release, the first version of a major release often has major bugs).

                TL;DR don’t take too long to update to new releases, and don’t update too quickly!

                Also, the docker image is often a day or so behind the new release, soNextcloud tells you an update is available but often you then need to wait until the next day to get the updated docker image. I guess this is because (as I’ve just learnt) the image is built by Docker not Nextcloud.

  • TDCN@feddit.dk
    link
    fedilink
    English
    arrow-up
    17
    ·
    10 months ago

    Everything is behind a wireguard vpn for me. It’s mostly because I don’t understand how to set up Https and at this point I’m afraid to ask so everything is just http.

    • Johannes Jacobs@lemmy.jhjacobs.nl
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 months ago

      Its not hard really, and you shouldn’t be afraid to ask, if we don’t ask then we don’t learn :)

      Look at Caddy webserver, it does automated SSL for you.

      • TDCN@feddit.dk
        link
        fedilink
        English
        arrow-up
        5
        ·
        10 months ago

        Thank you. It was mostly ment as a joke tho. I’m not actually afraid to ask, but more ignorant because it’s all behind VPN and that’s just so much easier and safer and I know how to do it so less effort. Https is just magic for me at the moment and I like it that way. Maybe one day I’ll learn the magic spells but not today.

        • Johannes Jacobs@lemmy.jhjacobs.nl
          link
          fedilink
          English
          arrow-up
          3
          ·
          10 months ago

          All software has issued, such is the nature of software. I always say if you selfhost, at least follow some security related websites to keep up to date about these things :)

              • andreas@lemmy.korfmann.xyz
                link
                fedilink
                English
                arrow-up
                2
                ·
                10 months ago

                few days late here, but that pastebin had some really good feeds 🙏 I noticed the OPML file was labeled FreshRSS and I also use FreshRSS. So I fixed up the feeds and configured FreshRSS to scrape the full articles (when possible) and bypass ads, tracking and paywalls.

                I figured I’d pay it forward by sharing my revised OPML file.

                I also included some of my other feeds that are related (if you or anyone else is interested).

                Some of the feeds are created from scratch since a few if these sites don’t offer RSS, so if the sites change their layout the configs may need to be adjusted a bit, but in my experience this rarely happens.

                I had to replace some of the urls with publicly hosted versions of the front-ends I host locally and scrape, but feel free to change it up however you like.

                https://gist.akl.ink/Idly9231/22fd15085f1144a1b74e2f748513f911

    • Fisch@lemmy.ml
      link
      fedilink
      English
      arrow-up
      9
      ·
      10 months ago

      I’ve been using YunoHost, which does this for you but I’m thinking of switching to a regular Linux install, which is why I’ve been searching for stuff to replace YunoHost’s features. That’s why I came across Nginx Proxy Manager, which let’s you easily configure that stuff with a web UI. From what I understand it also does certificates for you for https. Haven’t had the chance to try it out myself tho because I only found it earlier today.

      • ahal@lemmy.ca
        link
        fedilink
        English
        arrow-up
        6
        ·
        10 months ago

        NPM is the way. SSL without ever needing to edit a config file.

  • Atemu@lemmy.ml
    link
    fedilink
    English
    arrow-up
    7
    ·
    10 months ago

    Nothing I host is internet-accessible. Everything is accessible to me via Tailscale though.

  • Kusimulkku@lemm.ee
    link
    fedilink
    English
    arrow-up
    2
    ·
    10 months ago

    Jellyfin and Miniflux are internet facing because it would be turbo annoying otherwise to deal with them

  • EasternLettuce@lemm.ee
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    10 months ago

    Plex and jellyfin are open to the web. I know the prevailing wisdom is to put them behind a vpn but the reason I host media is to share it with friend and family and nobody will fuss with your service if it involves connecting to a vpn first

  • harsh3466@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    10 months ago

    Available to the internet via reverse proxy:

    • Jellyfin
    • Navidrome
    • Two websites
    • matrix chat server
    • audiobookshelf

    LAN only:

    • homepage
    • NGINX Proxy Manager
    • Portainer

    There’s more in both categories but I can’t remember everything I have running.

  • ALostInquirer@lemm.eeOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    Each time I’ve read into self-hosting it often sounds like opening stuff up to the internet adds a bunch of complexity and potential headaches, but I’m not sure how much of it is practicality vs being excessively cautious.

  • andreas@lemmy.korfmann.xyz
    link
    fedilink
    English
    arrow-up
    2
    ·
    10 months ago

    something like 95% stays local and is remote accessed via wireguard, The rest is stuff I need to host via a hostname with a trusted cert because apps I use require that or if I need to share links to files for work, school etc. For the external stuff I use Cloudflare tunnels just because I use DDNS and want to avoid/can’t use port forwarding. works well for me.

    • khorak@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      Just in case you missed this, you can issue valid HTTPS Certificates with the DNS challenge. I use LetsEncrypt, DeSEC and Traefik, but any other supported provider with Lego (CLI) would work.

  • pHr34kY@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    10 months ago

    Everything exposed except NFS, CUPS and Samba. They absolutely cannot be exposed.

    Like, even my DNS server is public because I use DoT for AdBlock on my phone.

    Nextcloud, IMAP, SMTP, Plex, SSH, NTP, WordPress, ZoneMinder are all public facing (and mostly passworded).

    A fun note: All of it is dual-stacked except SSH. Fail2Ban comparatively picks up almost zero activity on IPv6.

  • blackstrat@lemmy.fwgx.uk
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    I probably have more accessible from outside than not. Many are required: hosting a website, a media server I can access from anywhere outside the house, my phone system, etc. Some I used to use more than I do now: podcast service, that sort of thing. Then a bunch that are internal only. My phone connects home over Wireguard so that’s pretty convenient when out and about for accessing internal only systems.