- This topic is empty.
Viewing 6 posts - 1 through 6 (of 6 total)
Viewing 6 posts - 1 through 6 (of 6 total)
- The forum ‘Other’ is closed to new topics and replies.
The forums ran from 2008-2020 and are now closed and viewable here as an archive.
I can’t seem to find a tutorial that works.
I’m trying to redirect an old domain and anything typed after /
to redirect to a new domain.
For example ( =>
equals redirect ):
domain.net
=> domain.me
domain.net/something
=> domain.me/something
Try
location / {
rewrite ^(.*)$ http://www.domain.me/$1 redirect;
}
Nginx config file domain.net.conf
in /etc/nginx/sites-available
, don’t forget to system link it to sites-enabled
folder and reboot Nginx.
server {
listen 80;
server_name domain.net;
root /folder/on/the/server/www;
location / {
rewrite ^(.*)$ http://www.domain.me/$1 redirect;
}
location ~ /\.ht {
deny all;
}
}
Each of the domains that your server is responding to should have its own config file. So if you are responding to domain.net
and domain.me
each needs seperate config files. You would place these in the sites-available
folder. Then you would system link them, similar to what a2ensite
does for Apache, to the sites-enabled
.
sudo ln -s /etc/nginx/sites-available/domain.me.conf /etc/nginx/sites-enabled/domain.me.conf
sudo service nginx reload
The names are not really important. That’s more for our conviniance. Server name and document root we really care about. Nginx just loads the config files. You can have eveyrthing in one file if you wanted to.
So I would leave the default as is. If that’s your main website, then just copy that config file, name it old.site.config
if you want, then just add the code above, responding to appropriate domain. It’s really up to you how you want to structure it.
EDIT: Linked to wrong video, this one is using wildcard subdomains. I’ll leave it here if someone find it useful. Let me go find the correct one.
Watch this and you’ll see the process: https://serversforhackers.com/editions/2014/03/25/nginx/