Comment on My selfhosting setup so far

ExLisper@lemmy.curiana.net ⁨1⁩ ⁨day⁩ ago

• innocentz3r0@programming.dev ⁨1⁩ ⁨day⁩ ago

  I access it using the hostname of the device (since netbird and tailscale both let you do that)

  I also open docker ports only for localhost, and use caddy to reverse proxy subdomains to the respective localhost ports. Less port clutter from outside this way. Ofcourse things like SFTPGo’s SFTP port is an exception

  Also, vaultwarden requires HTTPS?? Ah drat, that’s not good :/ I don’t have experience with that.

  original

  • ExLisper@lemmy.curiana.net ⁨1⁩ ⁨day⁩ ago

    Also, vaultwarden requires HTTPS?? Ah drat, that’s not good :/ I don’t have experience with that.

    Yes, the clients work only over HTTPS. Caddy can handle that:

    vaultwarden.cosmos.internal {
            tls /opt/caddy/certificate.crt /opt/caddy/private.key
            handle /* {
                    reverse_proxy http://localhost:8081/
            }
    }
    

    The certs need to be generated for this specific domain:

    openssl req   -x509   -newkey rsa:4096   -keyout key.pem   -out cert.pem   -sha256   -days 36500   -nodes   -subj "/C=XX/ST=StateName/L=CityName/O=CompanyName/OU=CompanySectionName/CN=cosmos.internal"
    

    Some more details are here: bitwarden.com/help/certificates/ under “Using a self-signed Certificate”

    original

    • innocentz3r0@programming.dev ⁨1⁩ ⁨day⁩ ago

      Ah, as long as self-signed certs are an option, I can work with that :)

      original