• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Broken Netowrk Configuration when Adding IP Address via Plesk on Windows Server 2016

B

Ben Swayne

New Pleskian
TITLE:
Broken Netowrk Configuration when Adding IP Address via Plesk on Windows Server 2016​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx, Version 17.5.3 Update #4 on Windows Server 2016 (x64)​
PROBLEM DESCRIPTION:
Provisioning (Adding) a 2nd IP Address via Plesk Onyx on Windows Server 2016 resulted in not "adding" an IP but replacing the primary IP configuration entirely! This included remove the gateway and DNS entries as well.

Example: "https://samplehost.com:8443/admin/ip-address/add"

I was using an Amazon EC2 instance which by definition is a NAT'd configuration.​
STEPS TO REPRODUCE:
The original IP was configured in Plesk with a public IP and marked as "shared" IP Type. The 2nd IP I was adding was not provided a public IP at that time and marked as dedicated.

Plesk's mishandling of adding a 2nd IP made the Amazon EC2 instance publicly inaccessible due the change in primary private IP address.

(I had to remote desktop into another EC2 instance in the same availability zone and remote desktop via the private Amazon network to the private IP of the server to repair the IP configuration and restore public accessibility.)​
ACTUAL RESULT:
Adding 2nd IP, replaces the primary IP configuration of the ethernet interface.​
EXPECTED RESULT:
Adding a 2nd IP should not touch the primary ethernet interface configuration but simply add an additional IP to the existing ethernet configuration.​
ANY ADDITIONAL INFORMATION:
Perhaps this bug would not happen if I had made the original IP configured as "Dedicated IP Type" and then added the second IP as shared. I'm not sure and cannot spend my afternoon testing various orders of operations for this bug.​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
You must log in or register to reply here.

Similar threads

Talistech
Resolved Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.
Replies
1
Views
924
Talistech
Talistech
majdi draouil
Question Need Help Configuring Plesk Web Access on Server with Custom Ports - IP Accidentally Pointed to Domain
Replies
3
Views
518
majdi draouil
majdi draouil
C
Issue Failed to update the IP address" when repairing PHP-FPM configuration for all domains
Replies
2
Views
11K
scsa20
scsa20
Talistech
Resolved Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.
Replies
3
Views
910
Talistech
Talistech
K
Resolved Adding an IP for primary DNS server via CLI returns error
Replies
3
Views
2K
Peter Debik
P
Back
Top