403 On password reset link

[DragonDuck24]

Current Behavior

I get a 403 (Invalid signature.) error when visiting the link it sends me though email after any password reset.

I don't see a spot for this so I'm putting it here:
Panel and wings are running in docker.
I am using NGINX to reverse proxy the panel to my domain and add the SSL cert.

Expected Behavior

The password reset page comes up without an error.

Steps to Reproduce

Send any password reset (create new account without password, or reset the password on an existing account)
Open link sent to your email.
Error

Panel Version

1.0.0-beta19

Wings Version

1.0.0-beta11

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

https://paste.pelistuff.com/QSim

Is there an existing issue for this?

• I have searched the existing issues before opening this issue.
• I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
• I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.

[SirEndii]

Mhh weird
That should be fixed in beta19 - can't reproduce this anymore

[DragonDuck24]

Yeah I have no idea what is going on.
Do you need any other information?

[lancepioch]

@DragonDuck24 does it still give you an error in the latest Pelican Panel version?

[DragonDuck24]

@lancepioch yes I still get the error on panel beta 19. I havent tried building main or anything else though.

[lancepioch]

@DragonDuck24 Thanks for the report, we've had multiple people test the latest versions with no way to reproduce this bug (including myself), the reset is working correctly with the latest version, thanks again.

[PeenDev]

I am also having this issue. upon using the setup account link in the email or a password reset link I am getting a 403 Invalid signature.

I am also on beta 19

[DragonDuck24]

@PeenDev would we be able to find something in common with our environments? I honestly have no clue what to do about it. I'm running docker on everything which should be consistent, so I feel it has to be something with our data or config or something.

[PeenDev]

I am running pelican panel in a proxmox vm running debian 12
php version 8.4.5
Panel version beta 19.
Wings version beta 11.

all my wings and panel are hosted locally on some servers I own.

I also have a VPS with a wireguard tunnel to my local network reverse proxied with caddy.

I don't think the proxy is the issue though since I tried the url with the local ip address instead of my domain and I got the same error.

I also have no logs to share since my panel hasnt generated any logs for the day.

my original install was beta 18 and I updated to 19.

[PeenDev]

I also went through the PR that supposedly addresses this issue #1182

and verified the changes actually applied to my local installation and they did.

[SirEndii]

Very odd
I would give beta20 a shot which should be coming out this weekend according to a pelican maintainer

[DragonDuck24]

Okay well here is my full info:
I am running Ubuntu server 24.04.1 LTS (not a vm)
Panel version beta 19 in docker
Wings version beta 11 also in docker
The panel docker image has PHP version 8.3.19
Caddy is hosting the panel inside the container

Wings and the panel are hosted on a local server (same machine for both panel and wings)

I am running MariaDB and redis as well.

I have an NGINX reverse proxy to make the panel public and add SSL, however I also dont think its the issue because I only made the panel public 3 days ago (making it so other people can use it), and I tested the password reset just before I did any of that to make sure it worked (then it didnt lol).

IIRC, I started on beta 13, updated to beta 16, then again to 19. I did so only by replacing the docker image version in my compose file.

[DragonDuck24]

@SirEndii Will do when it comes out