Skip to main content
When managing a server on a platform like ORIV, knowing where to find configuration files is crucial.

​
How To Find Default Paths in ORIV

This guide provides detailed information on how to find default paths for PHP, Nginx, MySQL, and other related configurations on an ORIV server.

​
1. Site Path

The site path is where the files for each of your websites are stored. This directory typically contains the website’s HTML, PHP scripts, images, and other assets needed to display and run the site. Keeping your site files organized and accessible in this directory makes it easier to manage and update your site. For most setups on ORIV, the standard site path is:
  • Site Path:
Replace with the actual name of your website. For example, if your site is named “example.com” the path would be /var/www/example.com
This location is commonly used because it keeps site files separate and organized under the /var/www directory, which is a conventional location for web files on Linux servers.

​
2. NGINX Configuration Path

Nginx is a powerful and popular web server used to serve websites and applications. Each website that Nginx serves typically has its own configuration file, which contains settings such as server names, root directories, and proxy configurations. These configuration files are stored in the following path:
  • Nginx Config Path:
Here, should be replaced with the name of your specific site. For example, a website named “example.com” would have its configuration file at /etc/nginx/sites-available/example.com
After creating or modifying a configuration file in this directory, you usually create a symbolic link in the /etc/nginx/sites-enabled/ directory to activate the site.

​
3. PHP FPM Pool Configuration

PHP FastCGI Process Manager (FPM) is a PHP handler that allows for faster processing and better performance by managing pools of PHP workers. Each site or application can have its own FPM pool configuration, which specifies settings like the number of child processes, memory limits, and execution timeouts. These pool configuration files are located in:
  • PHP FPM Pool:
Substitute with the version of PHP that your site is using, such as 7.4 or 8.0. For example, if you are using PHP version 8.0, the path would be /etc/php/8.0/fpm/pool.d. Within this directory, you will find files named after your site or application, which contain pool-specific settings with the www.site-username.conf format.

​
4. Find Default Paths for PHP INI Configuration

The php.ini file is the main configuration file for PHP. It sets important options such as memory limits, file upload sizes, and execution time. There are separate php.ini files for different execution contexts: one for PHP-FPM (used by web servers like Nginx) and another for the CLI (Command Line Interface). The paths for these files are: For NGINX
  • FPM Configuration:
  • CLI Configuration:
For OLS
Replace with the specific PHP version you are using. For instance, if using PHP 8.0, the FPM configuration path would be /etc/php/8.0/fpm/php.ini, and the CLI path would be /etc/php/8.0/cli/php.ini. These files control the PHP environment for web and command-line scripts, respectively.

​
5. Find Default Paths for SSL Certificates

SSL certificates are essential for securing the connection between a user’s browser and your server. Certificates can come from different sources, such as Let’s Encrypt, which provides free SSL certificates, or custom providers like Cloudflare. The paths to these certificates vary depending on the source:
  • Let’s Encrypt Certificates:
  • Custom, Cloudflare, or Other Certificates:
Replace with your actual site name. For example, the path for a site named “example.com” using Let’s Encrypt would be /etc/letsencrypt/live/example.com/fullchain.pem. For custom certificates, ensure that the files are placed in the /etc/nginx/ssl// directory and referenced correctly in your Nginx configuration.

​
6. Log File Paths

Log files are vital for monitoring and troubleshooting server operations. They record information about server access, errors, and other events, providing insights into server performance and identifying issues. Common log file paths include:
  • Debug Log:
This file logs PHP-related debugging messages for sites using WordPress or custom PHP scripts.
  • Nginx Log:
This directory contains general log files related to Nginx, capturing various server events.
  • Nginx Access Log:
This file logs all access requests to your site, providing details about visitor IPs, request types, and response statuses.
  • Nginx Error Log:
This file logs any errors encountered by Nginx, including configuration issues, server errors, and script errors.
  • MySQL Log:
This directory contains logs related to MySQL database activities, which can be useful for monitoring queries, replication issues, and server performance.

​
7. 7G Firewall Configuration

The 7G Firewall is a set of rules designed to protect web servers from common threats like spam, SQL injection, and other malicious attacks. Configuration files for the 7G Firewall on an ORIV server can be found here:
  • General 7G Configuration:
This file contains the main rules that apply to the entire server.
  • Site-Specific 7G Configuration:
This file includes conditional rules tailored for individual sites. These files are critical for securing your server and should be reviewed and updated regularly to adapt to new threats.

​
8. Site Backup Path

Backing up your site is crucial to prevent data loss. On ORIV servers, backups are typically stored in a hidden directory under the root user’s home directory:
  • Backup Path:
This directory contains backup archives of your site files and databases. Regularly check this directory to ensure backups are being created and consider copying backups to an off-site location for added security.

​
9. Redis User File Location

Redis is a popular in-memory data structure store used as a database, cache, and message broker. On ORIV servers, user access control for Redis is managed using the users.acl file:
  • Redis User File:
This file defines user permissions and access control lists (ACLs) for Redis. Make sure to configure this file to restrict access appropriately and secure your Redis installation.

​
10. Cron job List Path

Cron jobs are scheduled tasks that run automatically at specified intervals. They are useful for automating repetitive tasks such as backups, updates, and maintenance. The list of cron jobs is typically stored in:
  • Cronjob List Path:
This directory contains files that define scheduled tasks for various applications and scripts. You can add or modify cron jobs here to schedule tasks like database backups, system updates, and routine maintenance scripts. These paths are common default locations on ORIV servers, but they can vary based on your specific configuration or server setup. It is always a good practice to double-check these paths, especially after custom configurations or installations, to ensure your server operates securely and efficiently.