Creating Redirect Rules in forge that redirect to a different site

Yeah, those settings are for individual urls, not site-wide.

In forge, go to the "old.site.com" "site details" settings page. Scroll down to the bottom of the page. There is a "files" dropdown button. Select "Edit Nginx Config" from it. You'll get a popup containing the current config.

This should be your site definition to redirect everything from old.site.com to new.site.com.

server {
        listen 80;
        listen [::]:80;
        server_name old.site.com;
        return 301 http://new.site.com$request_uri;
}

That will redirect all urls to old.site.name to new.site.name, including any parameters. So, http://old.site.com/something/else would redirect to http://new.site.com/something/else

Instead of deleting everything that currently exists in the config for that site, I would comment out each line with a # at the beginning of the line, just in case there is a problem. Or better, if you know how, backup that config file before editing (via ssh).

Thanks @Cronix, guess that would have been too easy to be true. I've got a copy saved so time to jump in I guess, thanks for the advice!

@Cronix sorry to bug you, but is there any other steps to take after editing the Nginx config file? I've updated and saved it but I'm not getting the redirect, could be something else going on with our servers but I wanted to make sure I didn't need to do anything else before it would take effect.

Is it a regular domain or ssl?

They're both ssl, what I've got looks like this just with the actual sites changed:

server {
    listen 80;
    listen [::]:80;
    server_name www.site.com;
    return 301 https://new.site.com$request_uri;
}

Is it possible that returning https is what's throwing it off? My new site automatically redirects to https so maybe I should just return http

Edit: Well, I tried having it return http://new.site.com$request_uri; but still not getting any redirect.

I was going to suggest listening to both 80 and 443 ports if it was ssl.

Is that server block listed as the first thing in the nginx config?

@Cronix, turns out the issue was caused by something a co-worker had set up on the other server, not anything with the nginx file. Thank you so much for your help dude, I really appreciate it!