We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
This package is working locally, but as soon as i deploy to production any links generated by this package are returning that they are invalid.
Example link: https://example.com/approve/8?expires=1519637818&signature={hash}
If you check that timestamp, you will see it is for 7 days time, however it returns false on the validate method.
validate
After modifying the source files to do a check, it's this code which is failing:
if (!$this->hasValidSignature($url)) { return false; }
The site is working locally.. and my .env file does have an APP_KEY - help.
The text was updated successfully, but these errors were encountered:
Probably this is due to some configuration of the project on your server. Pretty sure your problem is not caused by a bug in the package itself.
Try to find the differences between your local environment and the server.
A first good step would be to run php artisan config:clear.
php artisan config:clear
Sorry, something went wrong.
I am facing same issue and have executed php artisan config:clear still facing issue. Can anyone help ?
No branches or pull requests
Hi,
This package is working locally, but as soon as i deploy to production any links generated by this package are returning that they are invalid.
Example link: https://example.com/approve/8?expires=1519637818&signature={hash}
If you check that timestamp, you will see it is for 7 days time, however it returns false on the
validate
method.After modifying the source files to do a check, it's this code which is failing:
The site is working locally.. and my .env file does have an APP_KEY - help.
The text was updated successfully, but these errors were encountered: