Status check when using oauth2-proxy

[DBLouis]

Hi
My Dashy has OIDC authentication enabled, as all of my apps. For apps that have "native" OIDC support, status check returns 200, for the others that uses oauth2-proxy, it returns 401.
Any guess why that happens and can I fix it somehow?

[NotAFlightRisk]

That 401 is oauth2-proxy turning away the status check itself. Dashy runs the checks from its server, not your browser, so they don't carry your login cookie. Apps with native OIDC answer that anonymous request themselves (a login page, or a redirect Dashy follows to one), so they show as up.

Easiest fix is to point the check straight at the app, around the proxy, with statusCheckUrl (any address the Dashy server or container can reach):

- title: My App
  url: https://app.example.com
  statusCheckUrl: http://192.168.1.20:8080

If Dashy can't reach the app directly, you can tell it a 401 counts as up. Bear in mind that only tells you teh proxy is answering, not the app behind it:

- title: My App
  url: https://app.example.com
  statusCheckAcceptCodes: '401'

Or let a health path through with oauth2-proxy's --skip-auth-route (e.g. --skip-auth-route=GET=^/health$) and use that as your statusCheckUrl.

Both Dashy options are in the status check docs.