• 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 Plesk EC2 License Change?

elecboy

New Pleskian
I have been deploying 2 or 3 Plesk a month in AWS. Today when I do my normal routine and I am setting up the Plesk server, I get a message that I need to have a license. What happened? I normally use this route without problems. The last time I deployed an Instance was like one week ago. Did the license change?

You can see in the image it says the software in this case Plesk in included.
 

Attachments

  • Lic1.png
    Lic1.png
    53 KB · Views: 5
  • Plesk.png
    Plesk.png
    13.8 KB · Views: 5
We have not changed the licensing rules for AWS Plesk images. There is a possibility that when you deployed the image, the paid license did not arrive for it for some reason, and it continued to work with the trial license. In this case, I think you could ask Plesk Support assistance. They'll figure out what happened.
 
Just for reference, there was a bug found in version 18.0.37 that was creating the server with no license, and they fixed this.
 
Back
Top