3810 and 2930F are the same Operating System type, so yes the same may apply.
As mentioned, this error means that the SSL connection cannot be setup, which others have resolved by changing firewalls to allow the switches communicate without any limitations to central; also make sure there is no SSL inspection being done on that traffic an any firewall or other security device.
Central On Premises does not have the same certificates as Central running in the public cloud. Here is an overview of what is needed for the server certificate in COP, so if there are no firewalls or other devices interfering with the connections between switch/activate/central(on-prem), you may have a look there.
If that doesn't work either, it's best to open a TAC case as details on the certificates and some interactive troubleshooting may be needed to find and resolve the issue.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Nov 18, 2024 01:23 PM
From: Tomrbs
Subject: 2930F Web socket Connection Failed Aruba Central
Hello,
I faced the same issue on my Aruba 3810 switch while trying to connect it to Aruba COP. Does the things you mentioned work for this switch too?
I appreciate your response
Original Message:
Sent: May 12, 2023 07:00 PM
From: ariyap
Subject: 2930F Web socket Connection Failed Aruba Central
this looks like a cert trust issue with Activate or something that is inline messing with
was this switch ever connected to Central?
------------------------------
If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.