Deprecated cPanel API 1 usage detected
Hello,
Today I received this message by email :
You are receiving this notification because one of your accounts uses a custom cPanel integration or plugin that relies on the cPanel API 1 system. We deprecated cPanel API 1 in 2012 and plan to begin removing it from the product in cPanel & WHM version 88. This server is currently on cPanel & WHM version "86.0.4".
It happened after I gave root access to a system administrator. I'm afraid he implemented a malware of something.
Anyway, how should I take action regarding this email ?
Thank you :)
-
As the email says "your accounts uses a custom cPanel integration or plugin that relies on the cPanel API 1 system", and they "plan to begin removing it (cPanel API 1) from the product in cPanel & WHM version 88". Probably your server was updated to v.86 and it triggered that email. 0 -
This sounds like the official notification that goes out when you're using a plugin/integration that utilizes cpapi1, we have recently been taking great strides to move everything to uapi in the anticipation for the removal of cpapi1. You should identify the specific plugin/integration that relies on this and move to an updated version that does not utilize cpapi1 or find an alternate solution for it. 0 -
This sounds like the official notification that goes out when you're using a plugin/integration that utilizes cpapi1, we have recently been taking great strides to move everything to uapi in the anticipation for the removal of cpapi1 and cpapi2. You should identify the specific plugin/integration that relies on this and move to an updated version that does not utilize cpapi1 or find an alternate solution for it.
How can i find the plugin that use cp api1 ?0 -
In the email I"m seeing usr/local/cpanel/base/frontend/paper_lantern/index.html 52
how do identify the plugin?0 -
In the email I"m seeing
usr/local/cpanel/base/frontend/paper_lantern/index.html 52
how do identify the plugin?
I'm getting the same email any ideas what you need to do to fix?0
Please sign in to leave a comment.
Comments
6 comments