Nginx proxy managers/nginx configuration given by authentik does not work

[SpiderUnderUrBed]

Describe the bug

The provided configuration to put in Nginx Proxy manager and sometimes even nginx, makes nginx and nginx based configs appear as offline, yeilding a error

To Reproduce
Steps to reproduce the behavior:
Get the compose file for authentik, add a section for nginx proxy manager, then try authentiks proxy setup with Nginx proxy manager, (copy and paste it in Nginx advanced configuration box)

Expected behavior
It should work out of the box, the authentiks configuration for Nginx Proxy manager or nginx. It should not appear offline. Nginx proxy manager should not return errors for it being incorrectly configured.

Screenshots
If applicable, add screenshots to help explain your problem.

Logs
Output of docker-compose logs or kubectl logs respectively

[root@docker-98131251dcd3:/var/log/nginx]# cat error.log
2024/06/06 07:48:28 [emerg] 207#207: "map" directive is not allowed here in /data/nginx/proxy_host/3.conf:47
2024/06/06 07:48:28 [notice] 211#211: signal process started

Version and Deployment (please complete the following information):

• authentik version: [e.g. 2021.8.5]
  Latest
• Deployment: [e.g. docker-compose, helm]
  Docker compose
  Additional context
  Add any other context about the problem here.
  These issues have been refrenced in these github discussions
  Nginx Proxy Manager - Proxy Host Custom Locations #7323 and NPM (nginx proxy manager) "map" directive is not allowed here for authentik nginx config #10004
  One of which I opened recently, because I was looking for a solution specific to nginx proxy manager and the awnser given to the other discussion Nginx Proxy Manager - Proxy Host Custom Locations #7323 was for bare metal nginx

Removing the first few lines helped aliviate one error but lead to many more, this would be a headache to try and troubleshoot, #7323 goes over some of the fixes that can be made but there are more issues i encountered given that this isnt bare metal nginx.

[pythonius21]

I can also confirm.

I found a working one from: https://geekscircuit.com/set-up-authentik-sso-with-nginx-proxy-manager/

Hopefully this helps you!

[Joey4tunato]

I'm experiencing the same sort of error except I'd get a 525 SSL handshake error. It keeps saying the SSL is invalid however I know it works since I use the same certificate to access my authentik instance on a FQDN. The tutorial mentioned above isn't helpful as I tried it 3 different times while starting over from scratch. I believe this is an actual bug.

[Joey4tunato]

Hey found a fix for you! Use an older advanced config to input into NPM.

[SpiderUnderUrBed]

I found a config that worked for my awhile ago, ill share it later, anyways this is marked as a bug in hopes that a contributer will hopefully update the documentation given in authentik for setting up NPM.

[masterwishx]

i think its becouse websocket in new config ...

[IoSonoPiero]

So, the issue is still there with the latest Authentik version, 2024.6.0.
I used the link from @pythonius21, but I have problems with Websocket "enabled" applications.
I'm unable to understand how to fix this using the standard code generated by Authentik.