NGINX Integration setup is extremely easy. Our Frequently Asked Questions section covers this topic.
Payment related
- Q: How much does one license cost ?
A: One license cost $20.00 USD. - Q: Does any periodical (monthly, yearly) payment exists?
A: No, you have to pay ONCE. - Q: How can I pay for NGINX integration?
A: You can pay for NGINX integration using PayPal or Webmoney. - Q: I use REMSYS server management service. How much should I pay for NGINX Integration on a server managed by REMSYS?
A: Licenses for servers we manage are FREE of charge. - Q: My web server has Plesk control panel. Can I use NGINX Integration for my server?
A: At this moment only Cpanel is supported. Plesk and Directadmin versions will be available soon. - Q: I do plan to change my server. Will my NGINX Integration license work with new server?
A: No, it will not. You have to buy a new license. - Q: Can I use one NGINX Integration license for several servers?
A: No, you can't. Each license is valid only for one server. Please contact our sales department at sales@remsys.com for bulk licensing.
Technical related
- Q: What are NGINX Integration technical requirements ?
A: NGINX integration could be setup on the servers running Centos/RHEL 4.X, Centos/RHEL 5.X/FreeBSD 7.X, Apache 1 or 2, Cpanel version 11.25 or later. - Q: How can i check if NGINX Integration is appropriate for my server?
A: First of all check the minimal technical requirements (see above). For a precise verification download the verification script and run it on the server. - Q: Is there any additional nginx, Apache or Cpanel adjustment need?
A: No additional adjustments are required. NGINX Integration works automatically. - Q: How to disable NGINX Integration?
A: /usr/local/nci/bin/nci --unregister - Q: How to Enable NGINX Integration?
A: /usr/local/nci/bin/nci --register - Q:Where is located nginx main configuration template?
/usr/local/nci/conf/nginx_main.tpl - Q: What Template Variables can be used in nginx main configuration template?
A: |MAIN_IP| - cPanel main IP
|APACHE_PORT| - port on which apache is listening for incoming connections
|NGINX_CONFIG_DIR_VHOSTS| - path to nginx vhosts
|HOSTNAME| - server hostname - Q: Where is located nginx vhosts configuration template?
A: /usr/local/nci/conf/nginx_main.tpl - Q: What Template Variables can be used in nginx vhosts configuration template?
A: |DOMAIN_NAME| - Domain Name
|DOMAIN_ALIASES| - Domain Aliases
|DOCROOT| - Domain Document Root path
|SITE_IP| - Domain IP
|APACHE_PORT| - Port on which apache is listening
|PROXY_REDIRECTS| - list of [proxy redirects fro domains/aliases
|PROXY_PASS| - |SITE_IP|:|APACHE_PORT| - Q: How to regenerate nginx main configuration file after nginx_main.tpl change?
A: /usr/local/nci/bin/nci --create_nginx_main - Q: How to Regenerate vhosts files after nginx_vhost.tpl change?
A: /usr/local/nci/bin/nci --create_nginx_vhosts - Q: How to update NGINX Integration for Linux?
A: You can do it from repository:
yum --enablerepo=nci update ncior from Package:
-- Download packet from reposetupnginx.com/packages/$version/
-- Upload to server
-- Unpack downloaded archive
-- Goto unpacked directory
-- Run sh update.sh - Q: How to update NGINX Integration for FreeBSD?
A: From Package:
-- Download packet from reposetupnginx.com/packages/$version/
-- Upload to server
-- Unpack downloaded archive
-- Goto unpacked directory
-- Run sh update.sh - Q: How to create custom templates for specific VirtualHosts Server Name?
A: Templates should be placed in: /usr/local/nci/conf/custom/$customer_name/$virtual_host_server_name.tpl
Where $customer_name is cPanel customer name
$virtual_host_server_name is ServerName field value in VirtualHost.
You can use: /usr/local/nci/conf/nginx_vhost.tpl as initial template, just copy it into new location and adjust as you need. Template variables you can use are same as for nginx_vhost.tpl
Example: For domain of user "testuser"
ServerName testdomain.com
Path to template file should be /usr/local/nci/conf/custom/testuser/testdomain.com.tpl - Q: Why does nginx does not serve static pages for wildcar domains?
A: There is special synthax for wildcard domains in nginx. The only wildcard domains that are same as in apache have for: *.domain.com
All other forms, like: www.*.domain.com and others should have prefix: "~"
Example: ~www.*.domain.com
Also proxy_redirect directive does not recognize regular expressions in first argument, so redirect via Location and Refresh will not work corectly.
So to handle somehow these domains via nginx ( without serving static files, by default )
there is template file called: nginx_vhost_wildcard.tpl
If you want nginx to serve static content you will have to make a custom template for your wildcard VirtualHost
Changelog
- v0.5.1 - Fixed licence check ( It was giving error )
- v0.5 - Removed the IPs limit in rpaf configuration ( Linux )
Fixed buffer overflow in XML hooks processing - v0.4 - Fixed generation of nginx virtual hosts for wildcard domains based on separate template
Memory Leaks Fix - v0.3 - Added Ability to create custom templates for VirtualHosts.
Bug Fixes In nginx vhosts files generation and Hooks checks
Fixed generation of nginx virtual hosts for wildcard domains based on separate template - v0.2 - Bug Fixes.
Added handling of /scripts/postupdateuserdomains hook. - v0.1 - Initial Release
Didn't find answer on your question? Please, send your question on support@remsys.com and we will publish it on FAQ page.
Check NGINX Integration and your server compatibility before ordering.
Want to have nginx on your customized server? We will do it for you.Learn how to implement it.
