luckylinux

@thecodeassassin I expanded it quite a bit too :laughing: , if you are interested. There are better search support for disk size in particular, only counting hdd, nvme, ssd, etc....

I made some progress with setting everything to STARTTLS and feeding the Letsencrypt Certificates to Mailrise directly. So traefik is out of the loop now.

@mlsmaycon : any News on this ? It's really unfortunate I'm not getting anything working. At least the Webpage should show something useful IMHO, not just crash the entire thing...

I just noticed there might be something related to Traefik Reverse Proxy going on ... At the moment I only had the Dashboard reverse Proxy, but trying a Netbird Installation...

In my case I am getting the same message but with a different "cause" (syntax error). I had manually changed to running (on the master): a. `/etc/salt/master` - configured `user`...

@MartinEmrich Ah, alright, I missed that part, sorry about it. Not sure what is better security wise: having systemd session lingering to "kickstart" the user `/run/user/` userid and then all...

My "solution" mentioned in the other post is to apply a patch `salt-pip` itself: https://github.com/saltstack/salt/issues/65980#issuecomment-2084731676 Patch and Instructions (as well as a LONG Explanation / Analysis / Test) is provided...

> As far as I know there is no communication between two containers. The registry just adds `realm` to the `Www-Authenticate` header. The client (`curl`, `docker login`) is just using...

So I made some progress. One issue is that I had `realm: "https://127.0.0.1:5001/auth"` Whereas I'm using Traefik Proxy, so I should have been using just the Internal Hostname AND without...

And if I setup another Traefik Configuration for the new subdomain I createed, I get this: ``` Error: authenticating creds for "docker.MYDOMAIN.TLD": Requesting bearer token: invalid status code from registry...