TrumpetX

This is most definitely AI assisted. I won't say vibe coded, but this has the hallmarks.

I think it might have been related to being on Linux. I'm not using flatpack or snap, but it was just something that wasn't supported. I wish I remember what it was.

I was unable to use Chromium. I forget why, but I snagged real Chrome after hitting errors and my Google search telling me the issue.

I then immediately removed real Chrome.

Are you reading dungeon crawler carl too?

I understand why some would do this. It's definitely a more secure setup, but I highly doubt "most". I like having passwords on my work laptop. I couldn't sync there with a VPN, for example. My wife, kids and parents aren't going to run VPNs on their phones, etc.

Isn't that there point though? Remote synchronizing?

I have a 2013 MacBook running Ubuntu. No wifi drivers so I bought an Ethernet dongle off of eBay for $10. Runs immich pretty well.

Amen

This. This is the way. It solves this problem completely, but utilities somehow refuse it. It's almost like their argument is not in good faith ...

What are you using for a reverse proxy? There's some nginx websocket settings I had to do before things worked properly. I use cloudflare, but just for the DNS/cdn stuff, not their zero trust things.

server {
  server_name my.domain.com;
  client_max_body_size 2048M;

  location / {
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Host $host;
    proxy_pass http://10.10.10.30:13378/;  # My Wireguard Tunnel up to the VPS
    # proxy_cache_bypass  $http_upgrade; # This was added by Certbot
    # WebSocket support
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
  }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/my.domain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/my.domain.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = my.domain.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

  listen 80;
  listen [::]:80;

  server_name my.domain.com;
    return 404; # managed by Certbot
}

I don't disagree with you, but for a single server hosting multiple projects with differing system dependencies, docker is amazing. I've come around to using it for this practical reason.

Using docker over direct installation always feels like an unnecessary interface layer that just complicates things and introduces points of failure.