Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
After deploying VMware vSphere Data Protection (VDP) using the vSphere Web Client, you experience these symptoms: The VDP plug-in does not display in the vSphere Web Client You can see the VDP plug-in in the vSphere Client In the Web Client log (virgo.log) file, you see entries similar to:Downloading plugin package from https://VDPIP:8543/vdp-plugin-package.zipError unzipping https://10.9.98.229:8543/vdp-plugin-package.zip java.net.ConnectException: Connection timed out: connectjava.net.PlainSocketImpl.socketConnect(Native Method)java.net.PlainSocketImpl.doConnect(Unknown Source)java.net.PlainSocketImpl.connectToAddress(Unknown Source)java.net.PlainSocketImpl.connect(Unknown Source)java.net.SocksSocketImpl.connect(Unknown Source)java.net.Socket.connect(Unknown Source)com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source)sun.net.NetworkClient.doConnect(Unknown Source)sun.net.www.http.HttpClient.openServer(Unknown Source)sun.net.www.http.HttpClient.openServer(Unknown Source)sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)sun.net.www.protocol.https.HttpsClient.New(Unknown Source)sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)java.net.HttpURLConnection.getResponseCode(Unknown Source)sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown Source)com.vmware.vise.util.http.ConnectionManager.connect(ConnectionManager.java:173)com.vmware.vise.util.http.SimpleHttpClient.connect(SimpleHttpClient.java:179)com.vmware.vise.util.http.SimpleHttpClient.executeMethodResponseAsStream(SimpleHttpClient.java:102)com.vmware.vise.vim.extension.VcExtensionManager.writePackageToFile(VcExtensionManager.java:433)com.vmware.vise.vim.extension.VcExtensionManager.downloadPackage(VcExtensionManager.java:405)com.vmware.vise.vim.extension.VcExtensionManager.access$100(VcExtensionManager.java:61)com.vmware.vise.vim.extension.VcExtensionManager$1.call(VcExtensionManager.java:301)com.vmware.vise.vim.extension.VcExtensionManager$1.call(VcExtensionManager.java:298)java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)java.util.concurrent.FutureTask.run(Unknown Source)java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)java.lang.Thread.run(Unknown Source)com.vmware.vise.vim.extension.VcExtensionManager Done expanding plugin package to C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity\com.vmware.vdp2-5.5.6.56 Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This issue occurs due to one or both of these reasons: Port 8543 is blocked between vCenter Server and VDP The VDP plug-in package is missing
To resolve this issue, when: The port is blocked, revise the firewall tables in vCenter Server to add port 8543 open in both directions between vCenter Server and VDP and restart the firewall.or/and The VDP plug-in package is missing, re-install the VDP plug-in.To re-install the VDP plug-in: Download vdp-plugin-package.zip via https://VDPIP:8543/vdp-plugin-package.zip from the system which can communicate with VDP Configure page. RDP to the machine where the Web Client is installed. Navigate to the directory - C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity\ Note: in VCSA 5.5 , the folder is: /var/lib/vmware/vsphere-client/vc-packages/vsphere-client-serenity Create a folder with the name as in the log files, such as com.vmware.vdp2-5.5.6.56. Copy the extracted files from vdp-plugin-package.zip to this folder. Restart the Web Client service. Note: Step 2 brings the VDP plug-in up on the vSphere Web Client if needed, but step 1 is required regardless of step 2.
For more information, see Location of vSphere Web Client service logs (2004090).Location of vSphere Web Client 5.x service logs