cachethq / Docker

A Dockerized version of Cachet.
https://cachethq.io
BSD 3-Clause "New" or "Revised" License
411 stars 285 forks source link

Invalid signature Error 403 - Docker #385

Open djanand2000 opened 4 years ago

djanand2000 commented 4 years ago

I have Cachet running via Docker and during the verify email stage,the instance gets redirected to "subscribe/verify" and returns a 403-Invalid Signature . Error Message : Something went wrong on our servers while we were processing your request. Invalid signature. Should i try to execute "php artisan key:generate" and "php artisan config:cache && php artisan cache:clear " from inside the container to resolve the issue? Cachet Docker version: latest Can you please help ?

vikramarsid commented 4 years ago

@djanand2000 I am facing same issue..there hasn't been any solution for past couple of months..

djanand2000 commented 4 years ago

@vikramarsid , The weird thing is I have 2 instances of Cachet running and during the verify email stage, one instance gets redirected to "/subscribe/manage" and returns a 500 error while the other stays at "subscribe/verify" and returns a 403-Invalid Signature. The instance returning the 500 error has verified the user . The main difference that I have noticed is wrt the request, the working instance is HTTP and other is HTTPS. I am assuming a new value needs to be entered in the .env file.

djanand2000 commented 4 years ago

Hello Team, Could you please help me out here. Thanks

obsidian33 commented 3 years ago

I am only getting the 403-Invalid Signature when following the link 'Manage subscription' from a notification email. I am able to edit the subscriber in the dashboard and I noticed the difference between the two URLs is that the dashboard URL has a signature parameter while the one in the email notification does not.

manfred-warta commented 1 year ago

Problem still exists in v2.4 docker image. Can confirm @obsidian33 that via the dashboard the links are working to change the parameters. Actually we send these links to the subscribers that they can adjust their settings. Not nice, but a workaround for now :-)