#

Pivotlar’s NGINX Config Manager provides a safe, user-friendly interface to view and customize your NGINX configuration — without needing to SSH into the server or manually edit .conf files. It empowers advanced users and developers to fine-tune site behavior, domain handling, logging, and routing in a structured and modular way.

Accessing the NGINX Config #

To manage NGINX settings for a specific site:

1. Go to your Pivotlar Dashboard.
2. Navigate to Sites and open the site you wish to manage.

• Click on the EDIT NGINX button to open a modal window containing your site’s current NGINX

Configuration Sections Overview #

Listen on Ports #

Defines which ports NGINX listens to for incoming requests.

 listen 80;
 listen [::]:80;
 listen 443 ssl http2;

• Default is port 80 (HTTP).
• Also listen for port 443 (HTTPS) when using SSL
• Only modify this if running services on alternative ports.

Server Name Configuration #

Controls which domains or subdomains the server block will respond to.

server_name topnewsnetwork.org;

• Recommendation: Ensure all active domains used for this instance are listed here to prevent routing issues.

Logging Paths #

Controls where NGINX stores access and error logs.

error_log /var/log/nginx/topnewsnetwork.org-error.log;
access_log /var/log/nginx/topnewsnetwork.org-access.log;

• Use these logs to diagnose traffic anomalies, errors, or performance bottlenecks.
• Useful for debugging 4xx/5xx issues and load behavior.

Document Root #

Purpose: Sets the root directory from which NGINX serves files.

root /home/anus/websites/topnewsnetwork.org;
index index.php index.html index.htm;

• Ensure your site’s public directory is correctly mapped.
• Missing or misconfigured index files may result in 403 Forbidden errors.

Saving Your Changes #

Once you’ve made edits:

• Click Save Changes in the bottom right of the editor to immediately apply your configuration.

Best Practices #

• Do not remove system config markers (e.g., # DO NOT REMOVE), as they ensure platform compatibility.
• Use custom/ folders to isolate your modifications and avoid conflicts during updates.
• Always validate your config syntax and check logs after saving.
• Restart PHP-FPM or clear caches only if changes require it.

Need Help? #

Reach out to our support team via support@pivotlar.com