Absolutely yes.

Many a times when the projects become huge, the user data generated and stored can run into few 100 GBs and in extreme cases even into TBs. Typically this data will be stored in a data folder within the website root or off it within the user tree. Therefore many IT consultants and experts may advise that you would need to go for a higher specification VPS in order to accommodate this data.

Here we would like to assert that nowadays most VPS vendors offer volumes/block-storage which can be easily attached to a VPS. The price of this volume/block-storage is significantly less that the cost of the VPS.

Lets have a scenario where your PHP project is using 1-2 GB for running the website, but the data folder in itself is using 400 GB . Now here we also assume that your project runs well on a 2 vCPU core 4 GB RAM VPS ( Cloud Pro – Rs.2525 per month – https://n99panel.com/our-plans/ ) . For the CPU and RAM spec required, this VPS spec has only 80 GB SSD. Obviously this would not suffice. Therefore someone may believe that that a higher spec VPS i.e.  Cloud Pro – C8R32 would be required which would cost Rs.18600 per month. But now lets say we were to attach a 400 GB volume to the previous VPS. The price of the volume is Rs.12 per GB per month. Thereby the 400 GB volume would cost Rs.4800 per month. Therefore the total cost would be Rs.2625+Rs.4800 i.e. Rs.7425 per month . thus considerably lower.

Imp. GST @ 18% is applied to all prices.

Yes. We do provide the capability to have a modified PHP setup at three levels – PHP-FPM, SSH and Cron

Even though the default extension set handles most cases out of the box, but we are more than willing to go an extra mile to get your PHP setup working as per your requirement. You would simply need to send us your requirements (assuming they are technically possible), and in about one working day’s turnaround time, we can provide a customized PHP setup.

in-fact we have already done successful setups for customers who required solutions pertaining to MongoDB, Magento etc.

Yes, surely you can override or specify PHP INI directives.

There are two ways to go about it

1. From within N99panel, under a VHost/Website, click on the edit icon against the label ‘Apply Custom PHP INI Settings’ . In the subsequent form place each INI directive on a separate line, and then click ‘Apply INI Settings’ . Upon a successful submission, the FPM w.r.t. the VHost/website would be restarted and the new directives should be applicable provided they are semantically and technically correct. For a list of valid PHP INI directives, please follow this link : https://www.php.net/manual/en/ini.list.php . This feature does not work if custom PHP is choosen.
2. The custom PHP directives can also be set on per dir basis by using a .user.ini files . The directives set using this method, apply only to that particular directory and do not apply to the full directory tree. As mentioned above, each directive has to be placed in a separate line. Based on the type of directive, many master directives can be overridden with a corresponding entry in the .user.ini file.

Yes. You can run cron jobs in N99panel.

To run a cron job, you would need to do two things
1. Create/Update cron jobs from within List Users >> User >> User Cron
2. Enable CronD from within List Users >> User >> Manage SSHD/CronD

The cron daemon/process uses UTC time. Therefore you would need to accordingly adjust time/period values of your cron entries.

Also to the cron daemon/process the entire user directory tree with all VHosts/Websites gets exposed.

Yes.  Sure you can run Laravel projects on N99panel.

In Laravel, the exposed public directory is project_folder/public . If your Laravel project directly runs on the domain name, then under N99panel’s website/VHost management interface, you would need to extend the root dir for which you would need to place public under the requisite field/option of root dir extension.

In-case you are running Laravel into a sub-folder like example.com/myproject , in that case you would need to use the url-alias functionality of N99panel.

Also you would very likely need PHP and composer commands in the SSH terminal. In order to use this functionality, please enable Full SSHD flavor under Manage SSHd/Crond, for the respective user. Now relevant PHP interpreter is available in the form of phpXX where XX is the PHP version. For PHP 7.4, it would be php74 and similarly for PHP 8.1, it would be php81 . Similarly for composer 7.4 (which uses PHP 7.4) is usable via composer74 and composer 8.1 (which uses PHP 8.1) is available as composer81 .

Yes. Git CLI is available via SSH. You can use the Git CLI to integrate your projects or workflows with a code repository like Github.

Yes. It can be done.

MongoDB can easily be installed from within N99panel.

When MongoDB is installed, it would run on port No.: 27017 which would be globally accessible.

Upon successful installation of MongoDB, a MongoDB admin user will be created with a password. Details of the same would be shown when the installation is initiated.

You would need to use MongoDB Compass ( https://www.mongodb.com/products/tools/compass ) to manage MongoDB upon successful installation

You also have the option to change the password of the MongoDB admin user, after a successful installation

To use MongoDB from within your PHP scripts, you would need to choose PHP 8.1 (MongoDB) flavor, and your PHP script would need to connect to the MongoDB server’s private IP 172.16.26.1

MongoDB can also easily be used with NodeJS apps. To learn more about NodeJS, please cehckout this FAQ : https://n99panel.com/blog/ufaq/does-n99panel-support-nodejs/

N99panel is technically a vendor agnostic platform i.e. it is not technically tied down with any cloud vendor or provider.

Though the plans mentioned at our website are with Linode/Akamai cloud. But if you want to run the N99panel VPS on any other cloud vendor like AWS, Digital Ocean, Vultr or Contabo etc., please send us the URL of your specific VPS specification, and we would send you the custom quote of the same with N99panel.

While integrating CloudFlare, if you are using ‘Proxy’ for the website’s IP address, you may encounter an issue w.r.t. the SSL/TLS mode. The most likely symptom of this issue will be shown in the browser as ‘too many redirects’

The root cause of this issue is that SSL/TLS mode is being automatically set to ‘Flexible’, even though by default it was ‘Full’. This typically happens when Cloudflare detects that the nameservers of the domain have correctly been updated to the one’s issued by the Cloudflare.

This issue is already been mentioned in Cloudflare’s forum – https://community.cloudflare.com/t/ssl-changes-to-flexible-and-i-have-to-change-it-back-to-full/584065

A workaround to this issue is that after you have added your website/domain in the Cloudflare panel, under SSL

1. Change SSL Mode to Flexible
2. After 1-2 min, change it back to Full

This should work. In-case if you again see too many redirects error, again check this mode in the Cloudflare’s panel and/or the redirection logic of your website a.k.a .htaccess

Absolutely yes.

All system users created by you have SSH/SFTP access.

In order to ensure user level isolation, each SSH user would have a port assigned to that particular user. You would need to use that port to SSH/SFTP into the VPS. The assigned SSH port is shown with the N99panel console.

But there maybe a scenario whereby you can only access port 22 (the common port for SSH). In order to work with it, from within the N99panel console you can map the port 22 to a particular user. At any given time only one user can be mapped to port 22. For e.g. if userA has been mapped to port 22, when you map userB, the mapping of SSH port 22 will be removed from userA, and the new mapping with be then with userB.

Also SSH access comes with three modes – Minimal, Moderate and Full, with varying number of commands. The default mode is Minimal, but you can easily update it from List Users -> Manage SSHD/CronD

Under N99panel a VHost/Website is present under a user as /home/user/website_public_html . If a user is exmpl , and the website is example.com , VHost/Website path would be /home/exmpl/example.com_public_html .

The PHP code is not able to access the folders above this path i.e. it will not be able to access /home/exmpl/fldr1 nor it will be able to access /home/exmpl . This scenario is indeed desired as a matter of security practices. But if you wish to use /home/exmpl/fldr1 , you can use it via the external/expose dir feature under N99panel -> List Users -> User -> Expose Dirs . A typical entry under that option would be

/home/exmpl/fldr1:/home/exmpl/fldr1:example.com

But if you wish to use the full user tree i.e. /home/exmpl , then the entry would be

USER_HOME_DIR:USER_HOME_DIR:example.com

This expose dir or external dir feature can also used to access mounted volumes or block storage. For that, checkout the following link : https://n99panel.com/ufaq/can-large-external-volumes-be-attached-to-the-vps/

In N99panel, there is no limit for the number of users you can have. A user in N99panel us defined as a system user with its own SSH password.  To host a website or a VHost, you need to first create a user. A user can have one or more websites under it.

There is no limit on number of websites or users that you can make within N99panel. Only limitation is the VPS capability. For e.g. if the VPS has only 1 vCPU core and 1 GB RAM, then ideally you can put 3-5 moderate traffic websites. More sites can be places on a VPS with a higher specification.

Under N99panel even if a user account is empty (with minimal SSHD/SFTP flavor and disabled CronD), the latent or hidden space used by it is about 270 MB . The latent space is also used by a website/VHost, even when it is empty. It is about 540 MB

The reason for this usage of latent space is containerization, the technology that ensures isolation of user accounts and websites/VHosts with each other, thus ensuring overall security of the system as such isolation prevents spread of attacks/malware from an infected account or a website to other parts of the system, thus improving the overall security.

To reduce this latent space usage, if the server admin is the person managing all accounts, placing multiple websites/VHosts under a single user account can further reduce this usage. For e.g. if you run 5 websites under a single account, the total latent space used will be about 0.27 GB + 2.7 GB i.e. 2.97 GB . Were you to run these 5 websites under 5 different accounts, the usage in that case would be 1.35 GB + 2.7 GB i.e. about 4 GB.

N99panel panel allows you to upload/manage files/directories via any SFTP compliant client file FileZilla (highly recommended). FileZilla includes many advance features which make most file managers redundant. Now within N99panel, we have implemented ‘Directory Traversal’ under user accounts. From within it, you can do three operations which otherwise maynot be possible in a SFTP File Manager. These operations are – archive generation (making a zip file), archive extraction and recursive removal of  folder tree.

Now if you are running a WordPress based website, there are several file manager plugins available like File Manager ( URL : https://wordpress.org/plugins/wp-file-manager/ ) , Advanced File Manager ( URL : https://wordpress.org/plugins/file-manager-advanced/ ) etc.

If you are work on a Linux or a Mac client, you can also do a SFTP mount on to your local file system. You would need to Google it in order to make that work.

Each valid website or a VHost when setup properly i.e. the IP address of the website should point to the VPS, will have its SSL certificate automatically configured at the time the website is added or later (on scheduled intervals) when its IP begins pointing to the VPS. The free certificate is issued by Let’s Encrypt and is valid for three months. ideally this certificate is automatically renewed within three months, but for reasons like wrong IP pointing etc., it can get delayed or may not get renewed.

In the case where you have purchased a SSL certificate, you can have it configured from N99panel console.

Yes. Its is possible.

The main requirement for running Magento with Elasticsearch is that you would need to go for a VPS which has RAM greater than 8 GB.

As your Magento setup may also require custom PHP extensions/setup, please refer to the following answer for more details . https://n99panel.com/ufaq/can-i-have-a-custom-php-environment-with-extra-extensions/

Yes. It is.

There are two modes of malware scanning – Realtime and OnDemand.

Realtime malware scanning scans for malware etc. in the new files or the files that have changed, The default mode of realtime scanning is detect & clean. So if you find files that have the extension .quarantined and are 0 bytes, very likely it represent the actual file which was detected and cleaned. In case for any reason you wish that realtime scans do not clean the detected file(s), please place a file ignore_scan.txt under /home/user . You can enter the full path of the file or the folder you wish to exclude from realtime scans. ignore_scan.txt can contain multiple entries with each entry on a separate line.

W.r.t. OnDemand scanning, it can be initiated by a N99panel admin user from within the N99panel interface. There are two modes under which OnDemand scanning can be done – Detect and Detect & Clean. In-case a malware is found, you can then download the relevant report pertaining to that particular scan. The OnDemand scanning also considers ignore_scan.txt as mentioned previously.

Yes. Each website/VHost created under N99panel would have their own Redis instance. The name of this Redis instance is shown user website/VHost details/mgmt page. This Redis instance in in-fact a hostname.

This Redis instance can be used appropriately where required in your project. This Redis instance runs on its default port i.e. 6379.

Yes. Varnish, a page caching servicem is available under N99panel.

By default Varnish is not enabled for a website/VHost. When you wish to use Varnish w.r.t. your website, within N99panel’s console, go to Details/Manage menu of the website/Vhost. There you would have the link/button to manage Varnish.

There are five options for Varnish :

• Disable
• Enable – Config 1
• Enable – Config 2
• Enable – Config 3
• Purge/Clear-cache

With WordPress you can easily use Varnish and enable auto-purging of content (when it changes), by using the Proxy Cache plugin .

Very important : When you are doing design/coding changes of your website, please disable Varnish in that case. Varnish cache or any cache for that matter should only be enabled in production ready mode.

The Varnish setup is primarily optimized and configured for WordPress setups. W.r.t. available varnish configs

• Varnish Config 3 covers 95%+ cases/scenarios and thus results in effective caching
• Varnish Config 2 covers 60%+ cases/scenarios and thus sometimes varnish cache may get bypassed
• Varnish Config 1 covers 25%+ cases/scenarios

When Varnish and specifically, when a higher number configuration is applied, it may impact certain sections of the website in unexpected ways, as certain cookies/sessions will have no effect based on varnish configuration selection. After applying a Varnish configuration, you should thoroughly check all parts of the website, and also ensure security and privacy is not compromised.

If you migrated a website and you are seeing the error ‘too many redirects’, most likely in your .htaccess file there may be lines pertaining w.r.t. HTTP to HTTPs redirection. Please comment those lines. This should solve the problem in most cases.

But if your site is a WordPress website and still this problem is present, then most likely it is caused due to some redirection plugin. Please disable or move/remove the plugin or plugin folder to sort out this issue.

To effectively manage HTTP to HTTPS redirection, N99panel console already provides the in-built functionality. Under a website’s/VHost’s details/management section, the interface ‘HTTPS forced redirect:’ allows you to specify the option which you require.

Under N99panel multiple PHP versions are available. There are three ways PHP is used
– FPM (via browser)
– CLI (Command Line Interface)
– Cron daemon

PHP usage via FPM is handled from within N99panel interface. Each VHost/Website under N99panel can have its own PHP version

When using PHP CLI via SSH, ‘Full SSHD flavor’ needs to be enabled for the respective user under ‘Manage SSHd/Crond’. Following points/info be considered
– Multiple PHP versions as accessible via php70 (PHP 7.0), php71 (PHP 7.1), php72 (PHP 7.2), php73 (PHP 7.3), php74 (PHP 7.4), php80 (PHP 8.0), php81 (PHP 8.1), php82 (PHP 8.2). The default PHP version accessed via php command is PHP 7.4
– Multiple corresponding composer versions are accessible via compose70, composer71, composer72, composer73, composer74, composer80, composer81
– To use composer with PHP 8.2, please use the following command to access composer php82 /usr/local/bin/composer

When using PHP with Cron daemon or cronjobs, ‘Full SSHD flavor’ needs to be enabled for the respective user under ‘Manage SSHd/Crond’ and the following be considered
– Refer to the article on how to use Cronjobs on N99panel – https://n99panel.com/ufaq/can-i-run-cron-jobs-in-n99panel/
– Multiple PHP versions are accessible using full paths of php executables as under
— /usr/bin/php70 (PHP 7.0)
— /usr/bin/php71 (PHP 7.1)
— /usr/bin/php72 (PHP 7.2)
— /usr/bin/php73 (PHP 7.3)
— /usr/bin/php74 (PHP 7.4)
— /usr/bin/php80 (PHP 8.0)
— /usr/bin/php81 (PHP 8.1)
— /usr/bin/php82 (PHP 8.2)
– Multiple corresponding composer versions are accessible as under :
— Composer with PHP 7.0 – /usr/bin/php70 /usr/local/bin/composer
— Composer with PHP 7.1 – /usr/bin/php71 /usr/local/bin/composer
— Composer with PHP 7.2 – /usr/bin/php72 /usr/local/bin/composer
— Composer with PHP 7.3 – /usr/bin/php73 /usr/local/bin/composer
— Composer with PHP 7.4 – /usr/bin/php74 /usr/local/bin/composer
— Composer with PHP 8.0 – /usr/bin/php80 /usr/local/bin/composer
— Composer with PHP 8.1 – /usr/bin/php81 /usr/local/bin/composer
— Composer with PHP 8.2 – /usr/bin/php82 /usr/local/bin/composer

A typical cron job may look like

*/15 * * * * /usr/bin/php80 /home/user/vhost_public_html/phpscript.php

The above cron will execute the above script every 15 min.

If you require a custom PHP extension, please let us know so that we can make it available for you.

N99Panel is a control panel with a set of advance tools and options which lets you run any WordPress or WooCommerce or any PHP site seamlessly on your VPS .

N99panel supports PHP versions right from PHP 7.0 to 8.2. Each website or a VHost can have its own PHP version. While choosing a PHP version, you also get the option to choose maximum PHP processes limit.

Choosing the correct PHP processes limit is very essential in order to manage outages or spikes in the web traffic, and to ensure that the VPS keeps running smoothly.

For a detailed article, please refer to : https://n99panel.com/ufaq/php-versions-and-their-cli-usage/