nazcov
Filament v3 w. Laravel 11 and AWS hosting
Could be, I'll check up on it. I was wondering whether the issue is related to the CNAME
api.xxx.com and in reality Filament is just a subdirectory on that api.xxx.com/dashboard etc. I'll try to investigate more in details. I was just wondering if there was an obvious thing that I was missing.
Thanks!6 replies
Filament v3 w. Laravel 11 and AWS hosting
No but as I read the docs this is only for limiting requests from other urls?
The "issue" here is a reverse dns issue I think. Given thet our CNAME is dashboard.xxx.com but the real deployment is located on api.xxx.com and thus it redirecta to this.
So if I'm correct there are 2 ways out of this.
1. Is to somehow setup a reverse dns with the filament part of the api.
Or
2. Separate the API and filament, but I'm unsure if this is possible?
Maybe there are other options, I'm just guessing a bit here.
Does what I say make any sense?
6 replies