{"id":2984,"date":"2020-02-09T12:00:48","date_gmt":"2020-02-09T12:00:48","guid":{"rendered":"http:\/\/www.payneful.co.uk\/blogsplosion\/?p=2984"},"modified":"2020-01-26T16:41:13","modified_gmt":"2020-01-26T16:41:13","slug":"the-payneful-portfolio-redirecting-domain-names-to-mask-a-different-domain-path-using-nginx","status":"publish","type":"post","link":"https:\/\/www.payneful.co.uk\/blogsplosion\/2020\/02\/09\/the-payneful-portfolio-redirecting-domain-names-to-mask-a-different-domain-path-using-nginx\/","title":{"rendered":"The PAYNEful Portfolio – Redirecting Domain Names to Mask a Different Domain Path Using NGINX"},"content":{"rendered":"

Note:<\/strong> I wrote this post probably about three or four years ago, I’ve been sat on it for a while because a) I don’t know if it’s all that interesting and b) it might reflect poorly on my server admin skills. In the interest of transparency (and because I’m committed to this one blog a week malarkey) it finally gets published today.<\/p>\n

\n

Recently I have dabbling in some server fun, which means I’ve been engaging in activity that would make proper server admins cry with absolute rage.<\/p>\n

Let’s just say I have a website that makes use of RESTful URIs. We then have a system where we want to add a domain name but point it at a specific existing URI. For example…<\/p>\n

http:\/\/www.main-website.com\/restful\/uri\/long-string-of-parameters<\/pre>\n
…becomes the following…<\/p>\n
http:\/\/new-domain.com\/long-string-of-parameters<\/pre>\n
I could foresee a potential headache, as in my limited experience of tying domains to Linux servers you normally have to add stuff to sites-available and link it in sites-enabled. That could become an unscalable nightmare since we are looking at adding domains on a regular basis just to mask existing URLs!<\/p>\n
Poking around NGINX and the sites-available folder, I found a file called “catch-all” that contained the following…<\/p>\n
server {\r\n     return 404;\r\n}<\/pre>\n
Given that the only other files were for the main site’s config, it seemed obvious that this was a file to deal with “any other traffic”, which was interesting.<\/p>\n
In the NGINX config I also noted that there were several “include” statements like the following:<\/p>\n
include config-folder\/domain-name-here.com\/directory\/*;<\/pre>\n
This include seemed to be saying “include any config values from files in this directory”.<\/p>\n
Putting this new information together, I wondered if I could pass in a config file with directives for the domains we were looking to add. If I could, this should be easy enough to automate as it would just be a case of generating a new .conf file every time we add a domain!<\/p>\n
First, I pointed a test domain that we wanted to add to the system at the remote server’s ip in the domain registrar panel. This caused it to generate the default NGINX 404 page when accessing that domain, which made sense.<\/p>\n
\"NGINX
Quoth the server, 404.<\/div><\/div>\n
In the catch-all config file I added the following line at the top (note this was above<\/em> the server directive, not inside the curly braces with the 404!):<\/p>\n
include \/path\/to\/directory\/where\/we\/will\/add\/redirects\/*;\r\nserver {\r\n     return 404;\r\n}<\/pre>\n
This would mean that for any other traffic than the main domain, the config would check that directory for config files, and then just output a 404 if it couldn’t find or match anything.<\/p>\n
Then, in a new file in the freshly-created “redirects”1<\/a><\/sup> directory I referenced in the catch-all .conf I added the following to a file:<\/p>\n
server {\r\n     listen 80;\r\n     server_name new-domain.com;\r\n     location \/ {\r\n          proxy_pass http:\/\/www.main-website.com\/restful\/uri\/;\r\n     }\r\n}<\/pre>\n
Actually, I tell a lie – I originally just put a redirect to the main domain in there and, once I’d restarted NGINX, found that it worked! I only found proxy_pass was a thing after Googling how to “mask” a URL with NGINX<\/a>.<\/p>\n
Please note I originally wanted to place these redirect files in the secure NGINX directory but that threw up a small permissions issue that I will explain in a bit – instead, the folder is placed above the public root but in a location accessible by scripts (PHP, cli, etc.). Please do feel free to tell me how bad<\/span> an idea this is in the comments, and most importantly why! I need to learn.<\/p>\n
So I now had one domain masking another. Using PHP scripts I experimented using exec()<\/a> to create and populate a file with the details outlined above, and it worked, albeit after reloading the NGINX config each time to pick up on the changes. This wasn’t a problem – the domain redirecting process didn’t have to be instantaneous and I could just set a cronjob to run every hour and reload the config2<\/a><\/sup>.<\/p>\n
To reload the NGINX config is a one-liner…<\/p>\n
service nginx reload<\/pre>\n
…and doesn’t require NGINX to restart, so the website never has to disappear while everything reloads. I stuck it in a .sh file, gave it executable permissions (chmod +x) and tried running it. Surprise! It didn’t work.<\/p>\n
This is because you need to run it with “sudo” for elevated permissions. Bugger<\/em>. This is pretty much the problem I was having earlier when trying to generate the NGINX config files within the NGINX directory.<\/p>\n
You can automate sudo to run on the command line, but in almost every example given it requires either echoing out the root username and password (which doesn’t work if you’re doing it from a PHP script using PHP 5.6+ which, incidentally, is a BAD IDEA<\/span>) or you can have the username and password on the server in a file and read it in, which is a BAD IDEA<\/span>.<\/p>\n
After much Googling, I found the following article on StackOverflow<\/a>, which explained that I could just make an exception for that file to run without a password.<\/p>\n
I added the line to \/etc\/sudoers and promptly broke sudo on the server3<\/a><\/sup> because of a syntax error.<\/p>\n
\"Shit
An apt visual metaphor.<\/div><\/div>\n
Before I proceed any further, let me reiterate: DO NOT EDIT THE SUDOERS FILE FOR ANY REASON, NO, NOT EVEN FOR THAT REASON. NEVER EVER<\/strong> TOUCH IT!<\/p>\n
I’ve touched the sudoers file and broken it. Erm. What do I do now?<\/h2>\n
*Sighs*<\/p>\n
A lot of solutions to fix the sudoer file involve using pkexec<\/a> or rebooting the server in recovery mode<\/a>. For me, the former wasn’t installed (the cruel irony being that I needed sudo to install it) and the latter just completely locked me out as we rely on SSH keys for everything4<\/a><\/sup>.<\/p>\n
How I did fix it was to power down the box, reset the root password for the server using the hosting panel, boot it back up, “su” into the root account using the new password and then run “visudo” to remove the offending line that broke sudo in the first place. I resolved after that point to never, ever touch the sudoers file again.<\/p>\n
So how do we allow NGINX to run without a password?<\/h2>\n
How to add the exception line? That’s where sudoers.d comes in. Much the same way I could extend the NGINX config with other config files, you can do the same with the sudoers file<\/a>.<\/p>\n
I created a file called “scripts_permissions” (you can call it anything as long as it has neither a “.” or “~” in it) and added the following:<\/p>\n
#Allow nginx to reload config without a password\r\n[username] ALL=(root) NOPASSWD: \/usr\/sbin\/service nginx reload<\/pre>\n
Obviously you need to replace [username] with the user that needs access. This is when I found out that if you create a crontab file, the system will run those crontab functions as the user who created the file (not root)! Sound simple, but it can be confusing as I was putting the wrong user in the rule (I assumed it had to be the root account).<\/p>\n
This now means that I could run “sudo service nginx reload” on the command lineand it wouldn’t ask for a password. I set the cronjob to run once an hour during certain times on weekdays and hey presto! It now picks up on any new domain rules that I add to \/path\/to\/directory\/where\/we\/will\/add\/redirects\/ (obviously with a real filepath), albeit on an hourly refresh.<\/p>\n
The final point is to generate the redirects file containing the proxy_pass rules and move it to our redirects folder – this is simple enough to do in PHP using the exec() function or, if you want to be extra safe, dump the PHP-generated files to a directory and then have the system move the files to the sensitive directories so scrubby PHP isn’t soiling your file system with its treacherous clumsy fingers.<\/p>\n
Can you just use a wildcard DNS entry rather than separate subdomain config entries each time?<\/h2>\n
You can! You can just point a DNS entry for any subdomain at a server and these rules will still allow certain subdomains to proxy_pass specific URLs.<\/p>\n
There’s one problem (one which I don’t know the cause of) – say you have the following subdomains:<\/p>\n