You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[<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.
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?
The text was updated successfully, but these errors were encountered:
Docker image information
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:
When I look into the logs, I'll see this:
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:
Reproduction steps
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?
The text was updated successfully, but these errors were encountered: