Search for a command to run...
Here to give you guys a good read, in a different way with each blog. Not a niche-specific blogger. To be honest, I'm just blogging with the aim of applying knowledge to achieve practical goals.
No comments yet. Be the first to comment.
Python
Make a Github repo, and push the code to the repo. Login to the server by SSH Check if git is installed or not at the server, if not sudo apt update sudo apt install git Generate an SSH key on the VPS server, To establish a secure con...
If you're trying to install Node.js on your Ubuntu machine, you may have noticed that the version of Node.js you get is not always the latest one available. You might be wondering why that is the case. So why this happens? When you install Node.js on...
Hey there, In the past few days, I have been seeing here everyone is talking about debugging. I like the way Hashnode gives these writing goals which indeed will result in more technical writers. So here I am talking about the Debugging too. But let'...
Hey there, let me tell you something. I was tired of constantly switching between different operating systems on my computer. Windows for photoshop, Linux for coding - it was a never-ending cycle that I just couldn't seem to escape. That's why I deci...
By default, Nginx doesn't block unwanted access to your web server when it's done directly to your server's IP address. This means that anyone can potentially access your server's resources. Here is how you can fix this issue.
An Nginx web server installed and running.
Must be logged in with SSH and basic Linux commands
Open your Nginx configuration file using a text editor. Typically, the file is located at /etc/nginx/sites-available/
You can use the command, nano filename to edit the file.
Step 1: Your default_server should close all connections
Modify your Nginx default.conf /etc/nginx/sites-available/default.conf,
server {
listen 80 default_server;
listen [::]:80 default_server;
server_name "";
return 444; #CONNECTION CLOSED WITHOUT RESPONSE
}
This change closes the connection whenever Nginx receives a request without a domain name.
Step 2: Your virtual host should check the server name and close unwanted connections
Modify your virtual host file, /etc/nginx/sites-available/example.com
server {
...
# Only allow access if the host is correct
# Block other domain access
if ($host !~* ^(example\.com|www\.example\.com)$) {
return 403;
}
...
}
This simply disconnects the connection if the request was made to an unexpected domain.
Test the Nginx configuration for any syntax errors:
sudo nginx -t
If the configuration test is successful, restart Nginx:
sudo service nginx restart
Done.