Ask Why does my Laravel forge domain redirect fail to function?

[Brajet]

i have some redirects up.
two of them are fine, ***.domain.com, named as such.
the third one is not working...i set it almost a week ago, and it redirects to the IP, the same IP the working two are redirected to, but it comes up with a 404 NGinx error and doesnt display as the correct name, just http://ip

its configured exactly like the other two sites in regards to bluehost/forge config, which function perfectly.

a related issue is that i had a wordpress blog at domain.com/blog, unrelated to laravel forge, which now redirects to a 404 nginx. in fact, everything at my domain except my two working redirects does, even gibberish.

this leads me to believe im redirecting everything from bluehost to forge. is this standard practice? only my 3 subdomains are redirected on bluehost.

 

[Anthony Joshua]

That kind of redirect problem on Laravel Forge usually happens when the Nginx configuration wasn't updated correctly after adding or changing the domain. Sometimes Forge caches the old site settings, so even if you add a redirect rule, it won't take effect until you redeploy or restart Nginx. You might also want to check if your SSL certificate or DNS settings are pointing to the right IP. A mismatch between them can stop the redirect from working entirely.

 

[Felix😎]

It sounds like the issue might be with your Nginx configuration on Forge. If all traffic, including your main domain and /blog, is redirecting to Forge, there might be a "catch-all" setting in Nginx that's grabbing everything. You'd need to check if there's a default server block in Forge that's taking over requests not explicitly set for the subdomains. Also, double-check your DNS records in Bluehost to make sure only the three subdomains are pointing to Forge, and the root domain is still pointing to your WordPress hosting. It doesn't seem like standard practice to redirect everything unless it's intentional.