To provide users with an interface for managing NAT, a new extension, called NAT Manager, was created by means of Plesk Extensions SDK.
Comment
Posts Tagged NAT
5 results.
12/3/2013 Houston, TX – cPanel, Inc. is thrilled to release cPanel & WHM software version 11.40, which is now available in the STABLE tier. cPanel & WHM version 11.40 offers support for IPv6 and 1:1 NAT, an API Shell, and more. IPv6 Support cPanel & WHM is now IPv6-enabled with …
11/5/2013 Houston, TX – cPanel, Inc. is thrilled to release cPanel & WHM software version 11.40, which is now available in the RELEASE tier. cPanel & WHM version 11.40 offers support for IPv6 and 1:1 NAT, an API Shell, and more. IPv6 Support cPanel & WHM is now IPv6-enabled with …
6/24/2013 Houston, TX- Anticipated this week, June 24th, 2013, 11.39 will be pushed to the EDGE tier. This new build includes the following changes and updates to cPanel & WHM software: -Added support for using cPanel & WHM in a 1:1 NAT environment -Dovecot is upgraded to version 2.2 and …
The following new features have been implemented:
[+] Running PPA behind NAT. Administrators can configure PPA to run behind a router with NAT.
[+] Notifications for customers and resellers. Administrators can set up custom e-mail notifications about PPA events for customers and resellers.
[+] Troubleshooting improvements. Administrators can use the services_on_node tool to check whether service nodes run all the required services and whether all the required TCP ports are open on the nodes.
The following features have been improved:
[*] The performance of the migration tool was improved.
[*] PHP 5.4 is now automatically installed on Windows-based service nodes.
The following bugs have been fixed:
[-] Administrators could not register Windows-based service nodes if the administrator’s password contained the ^ symbol.
[-] Customers subscribed to service plans without shell access could switch on shell access for their accounts in Panel.
[-] After migration from Plesk 10.4 or later, subdomains could not be resolved in the DNS.
[-] When two user accounts with coinciding system user names were migrated from Plesk to PPA, the migration tool renamed one of them to avoid conflicts. After migration, the website owner whose system user account was renamed could no longer edit the files of their site.
[-] Auxiliary users were migrated without mail accounts if, during migration, the corresponding subscription was not yet provisioned in PPA.
[-] Failed removal of a provider’s branding subscription resulted in the inability to create a new branding subscription.
[-] Mail services were not properly switched off for providers’ branding subscriptions. This caused issues with deleting the subscriptions.