OpenID - (Error 500 Redirect Failed)

allthebits

New Member
Jan 30, 2025
2
0
1
Hello,
I have recently been trying to setup an OpenID realm in ProxmoxVE. I have followed the official documentation by Authentik and tried a YouTube tutorial for it.
No matter what I am trying, I always get the same error when trying to login using OpenID into Proxmox."OpenID redirect failed.Request failed (500)" I have searched through every forum/reddit post I could find about Proxmox and OpenID.

When I go to my issuer ID, it redirects to the URL + "well-known/openid-configuration" and I am able to see a lot of text data.

I am able to use Authentik with portainer successfully, but not Proxmox. I am not sure what special actions I need to take to get it configured correctly.


As suggested in some posts, I have tried with any without the trailing / for the Issuer and Redirect URL.

Any help is appreciated!


1738259354727.png

1738259748628.png
 
I use Keycloak. And there under "Redirect URIs/Origins" the URL was not enough. I had to add the URL with Proxmox's port 8006.
 
Hello,
I have recently been trying to setup an OpenID realm in ProxmoxVE. I have followed the official documentation by Authentik and tried a YouTube tutorial for it.
No matter what I am trying, I always get the same error when trying to login using OpenID into Proxmox."OpenID redirect failed.Request failed (500)" I have searched through every forum/reddit post I could find about Proxmox and OpenID.

When I go to my issuer ID, it redirects to the URL + "well-known/openid-configuration" and I am able to see a lot of text data.

I am able to use Authentik with portainer successfully, but not Proxmox. I am not sure what special actions I need to take to get it configured correctly.


As suggested in some posts, I have tried with any without the trailing / for the Issuer and Redirect URL.

Any help is appreciated!


View attachment 81688

View attachment 81690
Is this the tutorial you followed? Link: https://docs.goauthentik.io/integrations/services/proxmox-ve/
 
Last edited:

No, I've written my own.


But there from your link is also with the port 8006.
 
I use Keycloak. And there under "Redirect URIs/Origins" the URL was not enough. I had to add the URL with Proxmox's port 8006.

I normally do not have to include the port in the domain. When adding a port, I cannot access proxmox. I am using NPM. Though I have tried also tried using the authentik and proxmox server's actual IP addresses, instead of the domain/reverse proxy to test if NPM was causing issues.
 
I normally do not have to include the port in the domain. When adding a port, I cannot access proxmox. I am using NPM. Though I have tried also tried using the authentik and proxmox server's actual IP addresses, instead of the domain/reverse proxy to test if NPM was causing issues.
If you are using an identity provider like Keycloak, you must add the port, so that Keycloak knows what to access and where. "When adding a port": Where did you add the port. What are you using? How does NPM come into this? What have you configured and what are you trying to do?
 
  • Like
Reactions: fireon
Watching this as I have the same problem "OpenID redirect failed. Request failed (500)". All my other apps are working with Authentik, but Proxmox refuses :-(
 
It seems most people on youtube setting up authentik use a reverse proxy like traefik or nginix. Well, I didn't and also used a private CA for https connections. I installed the root in the browser and created a cert for both authentik and proxmox. authentik was a pain because even though I used docker and mapped the volume to the proper cert directory, you have to still go into the UI and under system -> brands and setup your domain, select the cert, and set it to default. That wasted a few hours. Then in proxmox, I finally realized that proxmox itself had to have access to the root (because it connects back to Authentik without the browser) so that means putting the private ca root into the Debian trust store. So copy it (extension .crt) here /usr/local/share/ca-certificates/ and then run update-ca-certificates. I DO need the trailing forward slash in my system for some reason. Finally, in the Authentik provider, the signing key had to use the same cert that I used for authentik ui. I guess all this is why people use reverse proxies and lets encrypt. Wasted an entire day :(
 
Last edited:
  • Like
Reactions: somebodyoverthere