calm.like.a.bomb

I’m on fosstodon

  • 2 Posts
  • 40 Comments
Joined 11 months ago
cake
Cake day: July 24th, 2023

help-circle









  • Thanks for the great explanation.

    So, currently, as I said, I’m using nginx proxy manager and do this:

    • reverse proxy to all my services inside the internal network on http: *arr stuff, rss reader, jellyfin and some other minor things. All of them use name.local.home notation. I’m using a local DNS for this, of course.
    • reverse proxy to just two services externally on https under wildcard certificates - both are non-standard names and the names are not related to the services themselves. For both these services I use Authelia with 2FA, so even if an attacker guesses the subdomain name, they’ll have to bypass that. As far as I can see in my logs, there are no attempts to breach my services. This is what I want to replicate and I’m planning on testing it.

    On the other hand, You gave me a good idea about using *.lab.domain.com getting resolved by the local DNS and the main *.domain.com by my public DNS. I’ll give this a try too in the near future. Another plan for me is to start using Authentik, as I saw it’s a bit better than Authelia in some areas, even though it may be overkill for a little project - I’ll have to see.







  • calm.like.a.bomb@lemmy.dbzer0.comtoSelfhosted@lemmy.worldDocker - what use is it?
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    3 months ago

    The answer is yes in both cases.

    1. Docker has an internal networking setup. You can create a “network” and all containers in that network communicate with each other, but not with other containers in other networks. So you can set up a VPN container in a network and all containers in that netowrk could use the VPN to route their traffic through.
    2. You can configure your VPN container to expose some ports that it uses to communicate, and then the “regular applications” can make use of those ports to connect through the VPN.