theit8514

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.

They finally added the last bit of data to this Session store that broke the whole application. 16MB of data being read/written from store on every http request. 50% of all http request processing was handling the Session middleware.

I hate developers who don't spend the very minimum to understand the environment they work in.

Ipv6 is a wild beast. It often doesn't need a dhcp server and instead will rely on routers sending out periodic router advertisement/announcement messages with a prefix to be used and your device will configure its address based on that prefix.

Dunno how smart it was to download and run. Could have been a compromised dev account.

It's a product of the format being parsed twice. Each line should be 80 characters with an = at the end, then a carriage return+newline(lf) to continue the line. Somewhere the cr+lf got converted to just an lf and then when reparsed it removed the lf plus the next character, making it still conain the equals but not the next letter of the message.

Here's a better technical explanation if you care: https://youtu.be/SVVnkNZWJhk

When connected to your internal network, what is the results of:

nslookup sub.domain.tld AGH.IP.Address

This should respond authoritative with the IP you need to access NPM's VIP IP address. If that is not the case, let us see your AGH configuration for your sub.domain.tld.

If that does return the correct IP, verify that it responds to https using curl on Linux or windows (replace curl with curl.exe)

curl -vvvI https://sub.domain.tld/

If this is not connecting or showing a cert error then there's a misconfiguration on the NPM side. Screenshots of your site configuration for one of the sites would be helpful. The domain name should match sub.domain.tld (not your duckdns) and be bound to the let's encrypt cert.

Technically Zero is 0-0 since One hasn't been set to anything yet.

Kinda shocks me that most of these cli apps still have no method of securing these credentials. No encryption with passphrase, no integration with password/secret managers. Just a plaintext credentials file in a static location.

IIRC there is a non-tor browser, which is included for things like logging in to wifi captive portals. Not sure I understand exactly what you're after but you can uninstall the package if needed.