NGINX proxyauth documentation is incorrect #423

Closed
opened 2026-05-17 21:01:04 -05:00 by TheFrenchGhosty · 2 comments
TheFrenchGhosty commented 2026-05-17 21:01:04 -05:00 (Migrated from github.com)

Describe the bug:

The documentation says:


  # url to send auth_request. Should be ${APP_URL}/api/authz/auth-request
  proxy_pass http://voidauth:3000/api/authz/auth-request;

So I did use the URL I set in my voidauth APP_URL config, meaning I used:

 proxy_pass https://auth.mydomain.com/api/authz/auth-request;

This caused a 500 error

However if I use the internal voidauth url (ie: http://127.0.0.1:3000/api/authz/auth-request; ) , it works

I'm assuming the documentation is wrong

Additional context:

Good job, other than that, this was super easy to setup compared to Authentik, hopefully a security audit happen soon so that it's safe to use for stuff exposed to the internet :)

### Describe the bug: <!-- A clear description of the bug --> The documentation says: ``` # url to send auth_request. Should be ${APP_URL}/api/authz/auth-request proxy_pass http://voidauth:3000/api/authz/auth-request; ``` So I did use the URL I set in my voidauth APP_URL config, meaning I used: ``` proxy_pass https://auth.mydomain.com/api/authz/auth-request; ``` This caused a 500 error However if I use the internal voidauth url (ie: http://127.0.0.1:3000/api/authz/auth-request; ) , it works I'm assuming the documentation is wrong ### Additional context: <!-- Any additional information that you think might be important --> Good job, other than that, this was super easy to setup compared to Authentik, hopefully a security audit happen soon so that it's safe to use for stuff exposed to the internet :)
notquitenothing commented 2026-05-17 22:26:06 -05:00 (Migrated from github.com)

Thanks for opening an issue! Indeed it does look like the documentation is incorrect

Thanks for opening an issue! Indeed it does look like the documentation is incorrect
TheFrenchGhosty commented 2026-05-17 23:10:19 -05:00 (Migrated from github.com)

@notquitenothing Good to hear I'm right, I spent more than 1-2 hours trying to figure out what was causing the 500, so glad to hear it wasn't for nothing 🙃

@notquitenothing Good to hear I'm right, I spent more than 1-2 hours trying to figure out what was causing the 500, so glad to hear it wasn't for nothing 🙃
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
adam/gate#423
No description provided.