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

Problem setting expiration date

E

EduardoV

Guest
Hi

I'm using Plesk's RPC API to create client accounts. The limits of these accounts are set by using a client template and the only limit that varies is the expiration date.

I'm having a problem setting the expiration date. I'm sending the following packet:

<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.4.2.0">
<client>
<add>
<gen_info>
<pname>11_2611</pname>
<login>11_2611</login>
<passwd>11@887</passwd>
</gen_info>
<limits>
<expiration>1297407356</expiration>
</limits>
<template-name>PlanBasico</template-name>
</add>
</client>
</packet>


And I'm getting the following response:

<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.4.2.0">
<client>
<add>
<result>
<status>error</status>
<errcode>1024</errcode>
<errtext>expiration value is incorrect</errtext>
</result>
</add>
</client>
</packet>


I don't understand what is going on. Initially we were sending the number of years in unix time stamp format, but what it did was set up the expiration date as 1970 plus the number of years sent. Still, it didn't throw this error.
Now we're sending the current date plus the number of years of validity in the same format, and we're getting this error. What could be happening???
 
Back
Top