Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Missing documentation] "Failed to validate OpenID login: realm and return_to do not match" behind NPM deployment #175

Open
0xmex opened this issue Oct 17, 2024 · 4 comments
Labels

Comments

@0xmex
Copy link

0xmex commented Oct 17, 2024

Docker image information

[<system> lanager-docker-compose]# docker images zeropingheroes/lanager
REPOSITORY               TAG       IMAGE ID       CREATED       SIZE
zeropingheroes/lanager   develop   1b07d902aa8e   3 weeks ago   197MB
[<system> lanager-docker-compose]#

Bug description
I've set up the LANager and put it behind npm. I can reach the website. But when I am trying to log in, I get an error:

Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.

When I look into the logs, I'll see this:

[2024-10-17 18:56:43] production.ERROR: Failed to validate OpenID login: realm and return_to do not match {"exception":"[object] (SocialiteProviders\\Steam\\OpenIDValidationException(code: 0): Failed to validate OpenID login: realm and return_to do not match at /var/www/lanager/vendor/socialiteproviders/steam/Provider.php:89)

I've put the https Domain in the .env. It's the same as on npm. But somehow it doesn't get condoned by Steam.

.env:

APP_KEY=base64:<bas64id>
APP_URL=https://play.mydomain.tld
APP_TIMEZONE=Europe/Berlin

STEAM_API_KEY=<mySteamAPIKey>

#TRUSTED_PROXIES=

DB_PASSWORD=<myPassword>
DB_ROOT_PASSWORD=<myPassword>

Reproduction steps

  1. Set up a fresh LANager install
  2. Set up the env as described
  3. Start the site
  4. Initialize it with the script
  5. Put the LANager behind a npm
  6. Access the site through the intended subdomain
  7. Try to log into Steam

Expected behavior
Error message as seen above

Bevore posting this, I've played around with the "TRUSTED_PROXIES" variable. When I've added the IP of the npm container it worked as intended. Maybe this needs to be added to the official documentation?

@ilumos
Copy link
Contributor

ilumos commented Oct 17, 2024

Hi there, when you say "put it behind npm" can you share more details? I only know npm as the package manager. Thanks

@0xmex
Copy link
Author

0xmex commented Oct 17, 2024

Hi @ilumos,

npm is the appreviation for nginx proxy manager :)

@ilumos
Copy link
Contributor

ilumos commented Oct 17, 2024

Yep no rush

@0xmex
Copy link
Author

0xmex commented Oct 17, 2024

Sorry, wrong issue ticket (:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants