Forge Load balancer issues and forceScheme https
In production environment I use a load balancer through Forge so there is the https LB and then 2 http servers. I have set the correct https:// url for both APP_URL and ASSET_URL. I unfrotunately am hitting 2 different errors with Filament depending if I set
If I don't force https, then certain things like the Filament Logout link don't work, because for some reason it's pointing to http:// and results in an error rather than a redirect. But things like the Reset Password function work as expected (though the email sends with http reset link which redirects to https).
If I force https, then the Filament Logout link works. But the Reset Password link results in 403 invalid signature error. I already tried setting trusted proxies middleware '*' (at+headers) but that didn't make a difference.
Is there a way to tell Filament to use https for the Logout (and all other) links, without setting URL::forceScheme('https')?
There was another user who last message said they needed to force https in the AWS ELB configuration. Don't currently have access on the project I'm on so wondering if there's another way. Invalid Route Signature: Password Reset
URL::forceScheme('https')If I don't force https, then certain things like the Filament Logout link don't work, because for some reason it's pointing to http:// and results in an error rather than a redirect. But things like the Reset Password function work as expected (though the email sends with http reset link which redirects to https).
If I force https, then the Filament Logout link works. But the Reset Password link results in 403 invalid signature error. I already tried setting trusted proxies middleware '*' (at+headers) but that didn't make a difference.
Is there a way to tell Filament to use https for the Logout (and all other) links, without setting URL::forceScheme('https')?
There was another user who last message said they needed to force https in the AWS ELB configuration. Don't currently have access on the project I'm on so wondering if there's another way. Invalid Route Signature: Password Reset
