I played the demo and had fun with the mechanics, I just disliked some of the character names. I bought it and would be playing it but just don't have the time.

Maybe they'll finally fix these 525 misconfigured ssl errors.

If you update DNS, that would use DNS-01 challenge and you don't need port 80 open. I am using this challenge type to generate certs for completely internal services. The only reason to have 80 open would be to use HTTP-01 challenge, which requires your server to host a file on a specific url only via port 80. If your service is already public on 443, you could leave port 80 open with a simple http-to-https redirect.

Port 443 would need to be open if you want to use TLS-ALPN-01 challenge, but I would avoid this as it is not easy to use or configure.

My advice for internal services is to setup only DNS-01 challenge and configure your dns to be automatically updated using a dns plug-in. This should almost never fail validation.

Interesting to see Oakridge TN mentioned, though by this point I think most of what they did there was public knowledge and the city was open to the public.

Needs a little more jpeg. The right side is clearer with a 0 in the threes digit. This is 2000.

On the flip side of this, any reasonably sized environment should be running their own ntp pool for their servers to use. Being down one stratum is usually not that big of a deal for most environments.

Yay, now I can sort all those "permanently on early access and I'm kinda interested but don't want to be burned" titles.

Most of these backup solutions try to reduce the amount of data backed up, so the system will process each file and determine if the contents changed and only upload new data. In this case if you modify the file you may end up with 2 16 MB chunks that have slightly different data, and only when the old backup expires and the pruning process completes would one of those chunks be deleted.

Smaller chunks sizes means you get more files written to S3, but less duplicate data when deduping without compression.

I would check the term.log/history.log files in the /var/log/apt folder to see if there's another process installing those updates.

If I had to guess, the container station might be giving the docker container a new network/ip address, one that the NAS is not using so that port 443 works and doesn't conflict with the NAS. If you start the container station then inspect the container you might see how they do it, but macvlan is typically how you would configure it.

services:
  my-lan-service:
    image: nginx:latest
    container_name: lan_container
    # 1. Attach the service to the custom macvlan network
    networks:
      lan_network:
        ipv4_address: 192.168.1.200  # The dedicated LAN IP for this container
    # 2. Ports are exposed directly to the LAN; do NOT use the "ports" block
    restart: unless-stopped

networks:
  lan_network:
    driver: macvlan
    driver_opts:
      parent: eth0                  # Change to your host's physical network interface name
    ipam:
      config:
        - subnet: 192.168.1.0/24    # Matches your physical local network setup
          gateway: 192.168.1.1      # Your physical router IP

I wonder if this is an Nvidia thing. It's been working quite well on my AMD hardware. I played for like 4 hours yesterday and then left the game open for 2 more by accident and it was still stable. I did lower some environment graphics settings to reduce microstutters but otherwise it's running quite well at 60 fps.

Check ethtool to make sure your link is actually operating at 2.5gbit with full duplex. You may need to make sure the kernel module for that ethernet nic supports 2.5gbit.