login does not work somehow

[wibed]

• docker info

  ...
  Insecure Registries:
  127.0.0.1:5000
  127.0.0.0/8
  ...

• values.yaml

  secrets:
  htpasswd: flux:$2y$05$BwBTGNGhCxcgimdKnN1TbuB8tpw/Zj7Yyzwve4.vYYX9FhcIX8VyS
  persistence:
  enabled: true
  storageClass: csi-driver-nfs
  size: 1G

• verify

  % echo 'flux:$2y$05$BwBTGNGhCxcgimdKnN1TbuB8tpw/Zj7Yyzwve4.vYYX9FhcIX8VyS' > test.htpasswd
  % htpasswd -vb ./test.htpasswd flux testtest123
  Password for user flux correct.

• login via port-forward

  
  kubectl -n docker-registry port-forward svc/cluster0-docker-registry  5000:5000

% docker login -u flux 127.0.0.1:5000 Password: Error response from daemon: Get "http://127.0.0.1:5000/v2/": dial tcp 127.0.0.1:5000: connect: connection refused

- exec -- ps
```yaml
PID   USER     TIME  COMMAND
    1 1000      0:10 /bin/registry serve /etc/docker/registry/config.yml
   69 1000      0:00 ash
   75 1000      0:00 ps

• exec -- echo $REGISTRY_AUTH_HTPASSWD_PATH

  /auth/htpasswd

• exec -- cat /auth/htpasswd

  flux:$2y$05$BwBTGNGhCxcgimdKnN1TbuB8tpw/Zj7Yyzwve4.vYYX9FhcIX8VyS

• exec -- nc -w2 -z 0.0.0.0 5000 && echo true

  true

• % nc -w2 -z 127.0.0.1 5000 && echo true

  true

• % curl -vvv 127.0.0.1:5000/v2/

• Trying 127.0.0.1:5000...

• Connected to 127.0.0.1 (127.0.0.1) port 5000 (#0)

  GET /v2/ HTTP/1.1 Host: 127.0.0.1:5000 User-Agent: curl/8.1.2 Accept: /

  < HTTP/1.1 401 Unauthorized < Content-Type: application/json; charset=utf-8 < Docker-Distribution-Api-Version: registry/2.0 < Www-Authenticate: Basic realm="Registry Realm" < X-Content-Type-Options: nosniff < Date: Wed, 10 Jan 2024 13:32:43 GMT < Content-Length: 87 < {"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":null}]}

• Connection #0 to host 127.0.0.1 left intact

why tho?

[wibed]

this might not be related to the registry at all

https://github.com/rancher-sandbox/rancher-desktop/issues/6294

[QuinnBast]

I think this is a registry issue...

Our registry just suddenly stopped working out of nowhere with the same errors you are facing above. Nothing in our helm chart has changed though... The registry had been working fine for 4-5 months now, but we are now getting 401s...

I've verified the htpasswd file has the correct user credentials, but any time that I attempt to docker login or nerdctl login to the registry it returns a 401 Unauthorized.

Edit: This ended up being incorrect SSL configuration on our side. The 401 was misleading...