CAP can not connect to CAPSMANV2 Certificate error

RouterOS Wireless Networking
1

I’ve CAPsman/CAP setup running on ROS 6.23 and Capsman V2.

I can connect the caps to the capsman with no certificate, but if i try and set certificate to request to lock it to the capsman I’m getting the error below on the capsman unit

21:06:55 caps,error [::ffff:192.168.188.2:57647,IssueCert] requests certificate, but failed to issue: a valid certificate with the same common name already exists! (7)

Previously the CAP’s were working on this Capsman, but I tried to move them to a new capsman server, but that failed to lock (certificate issue again) so moved them back.

Any ideas?

2

Note: CAPsMAN v2 is NOT compatible with current CAPsMAN v1 (CAPsMAN v1 CAP devices will not be able to connect to CAPsMAN v2 and CAPsMAN v2 CAP devices will not be able to connect to CAPsMAN v1). It means that both CAPsMAN and CAP devices should have wireless-cm2 package installed in order to make CAPsMAN v2 system to work.
If you want to try out the CAPsMAN v2 upgrade all the CAPs and the CAPsMAN to latest RouterOS version and install wireless-cm2 package.

3

Both cap and capsman are V2

4

Found the problem. Helps when look afresh.

I already had certificates in for the AP and so it was rejecting as it thought had already issued the certs. Revoked them and then tried again to set certificate=request and it happily re-issued and all connected fine.

5

Hello everybody, I’m new in this forum.
How do you revoke the certificate?
I have the some problem, but unable to solve.

Someone may help me?
Regards
Luca

6

Look in System->Certificates and select the ones you want to remove and select revoke. You’ll not be able to delete the device certificates unless you revoke and delete the CA.

7

Hi.
I had the same problem. I just delete Cert from CAPsMAN and create new one. It’s starts working :slight_smile:

8

cAP ac, certificates

/system routerboard pr
board-name: cAP ac

/interface wireless cap set enabled=no
/certificate remove numbers=0,1
/interface wireless cap set enabled=yes

9

Revoke certificate is a sollution ok, but this happens whenever my caps are reset to default and ask for a new certificate. is there any sollution that do not need any revoking process?

device already has certificate but lost it after reset.

i think capsman should be creating a new certificate for that caps and kill old one.

what you think?

10

Hi
I have the same problem .. one of my caps has losted its certificate and now when I enable caps I see this error in the log : handshake failure

I revoked the certificate in capsman but nothing happened and same error again

what should I do ???

11

Did you check on the CapsMAN Manager that youhave NOT checked “Require Peer Certificate” ?
if remote cap request certificates and this option is enabled in the manager, the ssl request fail
that’s did the trick in my scenario

12

Hello..
I have 4 caps and one of them can’t get certificates even though all of them are has the same setting.
Cap4 with dhcp is enabled from CAPsMAN with bridge access like other three
Versions are the same
Q: it has something about ip route list?
…

  • for just a few seconds it recognized caps4 in cap tab of cap4
    Any thoughts?
13

Thanks for that! I had two of my four CAPs that refused to cooperate with handshake failures. Once I unticked Require Authorization in my CAPsMan everybody fell into line and played nice.