• 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!
  • 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.

Resolved Activation issue, no properly formed ip address

S

swiftbash

New Pleskian
Hello,

I recently installed a plesk obsidian trial key for web host edition on my VMware workstation and activated just fine.

After a while, I decided to install it on my physical hardware. And when I tried to use the other trial key, it failed with "No Properly Formed IP Addresses (Error code 2)" error. I have disabled the firewall, tried to activate from command line and all with no luck. I can properly telnet and nslookup ka.plesk.com with no problem, so I don't know whats happening.

Here some information that may help:

OS: Windows Server 2019 Datacenter
OS for the VM: Same as physical machine
Debug Mode: Disabled.
 

Attachments

  • error.PNG
    error.PNG
    13.2 KB · Views: 8
According to Software Requirements for Plesk Obsidian, a static IP address should be configured on the server before installing Plesk for Windows. If Plesk is installed before assigning a static IP address to a network adapter, it can cause various issues and will inevitably create configuration conflicts.
 
  1. Press Start > enter Windows Firewall with Advanced Security.
  2. Click Outbound Rules > New Rule..., select Port, 5224, Allow the connection, and apply it to all profiles.
 
You must log in or register to reply here.

Similar threads

N
Issue This IP address is not configured properly
Replies
4
Views
3K
The 8th
The 8th
M
Issue This IP address is not configured properly
Replies
4
Views
3K
kirk macdonald
kirk macdonald
J
Issue Additional IP addresses configuration randomly breaks
Replies
2
Views
2K
JulienP
J
I
Issue Slave DNS Manager: "named" service doesn't work on primary server
Replies
11
Views
5K
ingmarcofilippini
I
Dukemaster
Issue Plesk licence key update failed (Network failure / Couldn't resolve host name)
Replies
12
Views
4K
AYamshanov
AYamshanov
Back
Top