10-11-2016 02:28 AM
I have an Aruba Central configuration with several Instant cluster located in the whole country. The captive portal is not working anymore cause to the revokation of the internal certificate.
Where can i upload my owne certificate for the accesspoints in Aruba Central?
Thanks in advanced,
Joshua van Riessen
Solved! Go to Solution.
10-11-2016 04:46 AM
Please check here: http://community.arubanetworks.com/t5/Controller-l
If you have urgent issues, please contact your Aruba partner or Aruba TAC (click for contact details).
10-11-2016 04:55 AM
Thanks for the fast reply.
however i cannot find the certificate option within Aruba Central.
The problem is when the Instant accesspoints are managed with Aruba Central the options in Aruba Instant are very limited and you can only configure it with Aruba Central.
10-11-2016 07:45 AM
You can contact Central TAC in the short term and they can push a certificate to your sites that is not revoked.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
10-14-2016 04:03 PM - edited 10-14-2016 04:24 PM
Is it necessary that the version is shown (126.96.36.199-188.8.131.52_56794)?
I have in my Aruba Central the 184.108.40.206-220.127.116.11_56428 latest version and when I try the downgrade to the 18.104.22.168-22.214.171.124_56794 version, then I get the following message:
<<Firmware available but no supported. Please proceed with caution.>>
Although I when try the downgrade to other version, like 126.96.36.199-188.8.131.52_56164, only I get the "Available" message, without extra warning messages.
I downgrade with "Custom Build" type at the 184.108.40.206-220.127.116.11_56164 firmware, and then, I upgrade to the 18.104.22.168-22.214.171.124_56428 latest firmware that I had at first with "Custom Build" type too, but I still have the revoked cert problem in Google Chrome browser.
Greetings and thanks in advance.
10-17-2016 12:10 AM
The message <<Firmware available but no supported. Please proceed with caution.>> is right. This is an firmware custom build for this problem in combination woth Aruba Central.
In the screenshot below you can see my accesspoint running at the firmware. The message for the newer firmware can be ignored until there is an update where the certificate is renewed of maby an option is build into Aruba Central to upload one.
Can you try it with the custom firmware: 126.96.36.199-188.8.131.52_56794.
12-02-2016 01:16 PM
Just an update on how we solved our issue.
After the custom build downgrade we got login error messages at cloud splash page.
The thing that solved our issue was to create a new empty group and after you create the empty group, add the AP to the group. TAC informed us that this will cause the AP to drop all their existing configuration and peak the new one.
For us this was the missing ingredient.
After that everything works we without the need for an public certificate.
A second issue that we had, is that with the above solution we lost the ability to do bandwidth limit, it just didn't work anymore. We got that solved with the creation of a security/access rule for bandwidth limit in the network profile.