Hi, use prisma studio for my production database on render following this guide: https://github.com/blitz-js/blitz/wiki/How-to-Run-Prisma-Studio-in-Production-on-Render.com. It used to work fine but now, after a few weeks not using it, I'm getting this error in prisma studio:

Error in HTTP Request (Status: 401) {}

It's probably something with authentication. If I enter the wrong password I don't see this error popup but the login window clears. So the reason for this error are not invalid credentials. In the logs I can see this:

{
  "level": "error",
  "ts": 1622364163.8549633,
  "logger": "http.log.access",
  "msg": "handled request",
  "request": {
    "method": "POST",
    "uri": "/api",
    "proto": "HTTP/1.1",
    "remote_addr": "10.123.123.123:54321",
    "host": "<http://prisma.mydomain.com|prisma.mydomain.com>",
    "headers": {
      "Content-Length": [
        "220"
      ],
      "Accept-Encoding": [
        "gzip, deflate, br"
      ],
      "Te": [
        "trailers"
      ],
      "X-Forwarded-For": [
        "123.123.123.123"
      ],
      "Origin": [
        "<https://prisma.mydomain.com>"
      ],
      "X-Forwarded-Proto": [
        "https"
      ],
      "User-Agent": [
        "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0"
      ],
      "Accept": [
        "*/*"
      ],
      "Accept-Language": [
        "en-US,en;q=0.5"
      ],
      "Content-Type": [
        "application/json"
      ],
      "Dnt": [
        "1"
      ],
      "X-Request-Start": [
        "1622366163855563"
      ]
    }
  },
  "common_log": "10.201.104.156 - - [30/May/2021:06:12:43 +0000] \"POST /api HTTP/1.1\" 401 0",
  "duration": 0.00003197,
  "size": 0,
  "status": 401,
  "resp_headers": {
    "Server": [
      "Caddy"
    ],
    "Www-Authenticate": [
      "Basic realm=\"restricted\""
    ]
  }
}

I re-deployed the whole app and tried different browsers and users but always get the same error. I'm not quite sure if this is a prisma issue but maybe you have an idea how to debug it. Thanks!

Update to the newest version and that should be gone already.

@janpio I already use the newest version 2.23.0🤔

Ohoh, then we only fixed that recently.

Thanks, this bug is gone in 2.24.

Nice 😄