🇨🇦

  • 11 Posts
  • 518 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle

  • Given the mechanical saftey built into those switches, Unfortunately I guess that leaves us with two reasonable possibilities:

    A) One of the pilots was somehow mistaken on the function of those switches and toggled them when they should not have. Then they genuinely thought they hadn’t when asked why they had cutoff fuel.

    Or

    B) One of the pilots chose to cut off fuel supply to both engines, intentionally bringing down the plane. They then lied to the other pilot when asked why they’d cutoff fuel.











  • An $11/yr domain pointed at my IP. Port 443 is open to nginx, which proxies to the desired service depending on subdomain. (and explicitly drops any connection that uses my raw ip or an unrecognized name to connect, without responding at all)

    ACME.sh automatically refreshes my free ssl certificate every ~2months via DNS-01 verification and letsencrypt.

    And finally, I’ve got a dynamic IP, so DDClient keeps my domain pointed at the correct IP when/if it changes.


    There’s also pihole on the local network, replacing the WAN IP from external DNS, with the servers local IP, for LAN devices to use. But that’s very much optional, especially if your router performs NAT Hairpinning.

    This setup covers all ~24 of the services/web applications I host, though most other services have some additional configuration to make them only accessible from LAN/VPN despite using the same ports and nginx service. I can go into that if there’s interest.

    Only Emby/Jellyfin, Ombi, and Filebrowser are made accessible from WAN; so I can easily share those with friends/family without having to guide them through/restrict them to a vpn connection.






  • Trying to set that up to try out, but I can’t get it to see/use my config.yaml.

    /srv/filebrowser-new/data/config.yaml

    volumes:

    • /srv/filebrowser-new/data:/config environment:
    • FILEBROWSER_CONFIG=“/config/config.yaml”

    Says ‘/config/config.yaml’ doesn’t exist and will not start. Same thing if I mount the config file directly, instead of just its folder.

    If I remove the env var, it changes to “could not open config file ‘config.yaml’, using default settings” and starts at least. From there I can ‘ls -l’ through docker exec and see that my config is mounted exactly where it’s supposed to be ‘/config/config.yaml’ and has 777 perms, but filebrowser insists it doesn’t exist…

    My config is just the example for now.

    I don’t understand what I could possibly be doing wrong.

    /edit: three hours of messing around and I figured it out:

    • FILEBROWSER_CONFIG=“/config/config.yaml”

    Must not have quotation marks. Removed them and now it’s working.


  • Decided to do some more reading on this topic. TIL:

    TCP, the more common protocol; requires at least one side to have a port forwarded through their NAT to the client, so the other side can make a connection to that open port.

    uTP on the other hand, can ‘holepunch’ by sending a packet to a known IP, which opens a port through the sending clients NAT, specifically for that IP. That port can then be used to send and receive by either side until it closes due to inactivity.

    So, torrent clients can use uTP holepunching to open a port without requiring manual forwarding, then advertise that open port to public trackers. Client ‘A’ will try to connect to an IP+port it got from the tracker and get ignored (because the recipient NAT isn’t expecting data from that IP and drops the packets). Then when client ‘B’ decides to connect to client ‘A’, 'A’s port will now be open and allowing data from 'B’s IP, thus establishing a connection.

    This is slower than a direct connection because both clients need to be made aware of each other and decide to attempt to connect at reasonably similar times. It also requires public trackers with peerexchange enabled and the torrents cannot be flagged as private.



  • FolderSync selectively syncs files/folders from my phone back to my server via ssh. Some folders are on a schedule, some monitor for changes and sync immediately; most are just one-way, some are two-way (files added to the server will sync back to the phone as well as uploading data to the server). There’s even one that automatically drops files into paperless-ngx’ consume folder for automatic document importing.

    From there BorgBackup makes a daily backup of the data, keeping historical backups for years with absolutely incredible efficiency. I currently have 21 backups of about ~550gb each. Borg stores this in 447gb of total disc space.