After some trial and error, I've managed to successfully deploy public instances of privacy-respecting services! - eviltoast

Hi, you guys might know me from these three posts. After reading all of the comments, I’ve decided to purchase a Mini PC to host public instances of privacy-respecting services.

I’m here to bring some good news: I got it working perfectly! You can visit reallyaweso.me today and get a list of services that I’m hosting!

All services are deployed via Docker and proxied through Cloudflare. You might ask: “Why Cloudflare?”. It’s because I can’t port forward things on my home network. It really sucks that I’m depending on Cloudflare to do the port forwarding for me, but it is what it is.

If you want me to host a specific service that you want, feel free to comment on this post!

I would really appreciate it if you guys could checkout some services that I’m hosting, as I don’t know if everything went smoothly or not. Thank you guys so much for helping me on this journey!!

  • nutbutter@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 months ago

    I am not sure what you mean.

    The issue is, when using Cloudflare, they will terminate your TLS, then encrypt the data again with their own certificate, which is send to the visitor. When visitor interacts, their data is decrypted on Cloudflare’s servers, which they encrypt again eith our original certificate and send it back to us.

    Sure, hackers or sniffers might not be able to look at the sensitive data, but Cloudflare can. But do they, or do they not, is upto you, if you trust them or not.

    • bitwolf@lemmy.one
      link
      fedilink
      English
      arrow-up
      2
      ·
      8 months ago

      Oh I understand.

      I was referring to the “strict” tls option which enforces that Cloudflare connect to your node via tls instead of http.