• 3 Posts
  • 10 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle





  • Depends which route you wanna take:

    • cheap and works out-of-the-box - entry level synology/qnap/asustore
    • have some more room, cheap, expandable, want to tinker a bit: consider used/refurbished SFF/Tower, you can get some of them in very decent price, like HP Z230 (or other haswell+ CPU), slap truenas and there you go.

    Personally I prefer the more DIY approach, as it doesn’t lock me into hardware (e.g can diagnose/replace faulty parts instead of throwing away whole box) or software (synology actually use standard md/btrfs raid so it can be read by any modern linux). Although I was using Synology myself and was very happy about the software




  • On your own email server make sure that you have correctly setup dkim, spf, reverse dns, and the ip of server is not on any known denylist - but it still doesn’t guarante that your email server would not get flagged as a spam source.

    Or maybe setup transport rules that would try to deliver most emails directly, but to major providers like Gmail/outlook which are quite picky via smtp relay - at work we are using AWS SES to do that, it is not that expensive, but it depends on the volume.


  • As you are running cloudflared in docker container, by default 127.0.0.1/localhost equal that docker container. Easy fix is to add

    extra_hosts:
          - "host.docker.internal:host-gateway"
    

    to your cloudflared service in docker-compose. Then you can point tunnel to host.docker.internal and it should point to your docker host instead of localhost of container. (ofc after reloading services by docker-compose up -d)

    Another easy solution would be to make your owncast server listen on lan IP of your server, and point cloudflared tunnel to that