MikeG
Desperately trying to fix gateway timeout on central filament panels
You'd think it would be fully infrastructure related, but then again, if I hit those routes when im not authenticated, it works fine (i.e it goes to the filament login page for that panel) ... And its working fine on Dev which is the EXACT same infra setup (through Laravel Vapor)
30 replies
Desperately trying to fix gateway timeout on central filament panels
Our production data is much larger ofcourse, so it must be something related to SQL. But then again, if I remove all resources on the panel, it still doesnt work. So its not coming from a resource
30 replies
Desperately trying to fix gateway timeout on central filament panels
Ye so this is also a rabbit hole i've gone down. Mainly because, on our dev server (using the exact same infra) its working fine (both those central panels). Its only broken on Production
30 replies
Desperately trying to fix gateway timeout on central filament panels
Ye we use Sentry, which also doesnt pick it up 😭 It seems completely infrastructure related because of it just not picking up any of the logging, but its weird that it only happens when your logged in and only on these 2 filament panels that are on our central domain and does not impact any of our tenant aware panels
30 replies