Hotspot Voucher Authentication Codes won't work after migrate from EAP Controller 3.2.10 to 4.4.6
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi at all,
we are currently using the old EAP Controller 3.2.10 with enabled Hotspot Authentication. We provide a guest-network with Hotspot-Portal using voucher-codes.
Now we are trying to migrate to the newest EAP Controller (currently we prepared 4.4.6 on our server).
We followed the migration guide on https://www.tp-link.com/de/omada-sdn/controller-upgrade/#content-1
which says that the the Hotspot Portal needs to be setup up again after migration. Under "Settings > Authentication" we created a new Portal with the same Portal-Name and settings as on the old controller.
After migration opening the hotspot managers shows that all existing voucher-codes have been copied. Looks good.
But connecting a device with the the network using the migrated voucher-codes don't work. The portal says that the code is invalid.
Trying to find out why, we created a new voucher-code which works out of the box. So there must some difference with migrated voucher-codes and new ones.
The only difference I can see is that the new one now has an entry in the column "portal".
I think there must be something missing during the migration. Does anybody have an idea how to fix that?
I find it interesting, that the "created time" is not really migrated, too. The old controller already got that column.
Dear @indigo,
Thank you for posting the problem on the TP-Link Community!
Regarding the issue that the migrated voucher codes are invalid, I'm afraid that it's designed like this.
After we migrate from Controller v3.2.10 to Controller v4.4.6, the previous Portal will be removed since it's incompatible, while the old voucher codes are not deleted but kept there without binding to a Portal (it's because TP-Link team try to keep the user's configuration as much as possible and leave this option for the user).
However, starting with Controller v4.3.5 and later version, it's required to bind the voucher code to a Portal before it can be used. So the old voucher codes are invalid, and you would need to create new voucher codes binding to a Portal to use them.
P.S. With the Controller v4.3.5 and later version, creating vouchers without selecting a portal is not allowed, otherwise, we'll see the error occurs like the image below.
Hey again,
I tried with different versions of Omada Controller to find out if its a bug.
First I installed the newest 5.0.3.0 on the target server. With that version I even cannot import the old backup. So 3.2.10 to 5.0.3.0 directly seems not possible:
OK, next try with the oldest version I could find on the TP-Link Download page: 4.1.5:
Importing the backup works but the voucher-codes seem to be wrong. My codes (type) are set up as unlimited logins with 1 user at a time. But the codes got migrated as 1 single use.
What about the next one: 4.2.8:
Hey, that looks better. The type seems to be correct now. So going from 3.2.10 to 4.2.8 looks good.
Now did an upgrade from 4.2.8 to 4.4.6:
Wow, the portal column gets magically filled with some valid stuff :-)
Ok, thats an interesting upgrade journey! Tomorrow I will try to log in with some of the codes.
Dear @indigo,
Thank you for posting the problem on the TP-Link Community!
Regarding the issue that the migrated voucher codes are invalid, I'm afraid that it's designed like this.
After we migrate from Controller v3.2.10 to Controller v4.4.6, the previous Portal will be removed since it's incompatible, while the old voucher codes are not deleted but kept there without binding to a Portal (it's because TP-Link team try to keep the user's configuration as much as possible and leave this option for the user).
However, starting with Controller v4.3.5 and later version, it's required to bind the voucher code to a Portal before it can be used. So the old voucher codes are invalid, and you would need to create new voucher codes binding to a Portal to use them.
P.S. With the Controller v4.3.5 and later version, creating vouchers without selecting a portal is not allowed, otherwise, we'll see the error occurs like the image below.
Dear @indigo,
As for this issue, did you import the backup file exported from the Controller v3.2.10 to the V5.0.30?
To figure out the issue, I'd like to escalate to the TP-Link support team for investigation.
They will reach you via your registered email address shortly, please pay attention to your email box later.
Sorry that I was not aware of the note that "Only the configuration file of controller v4.1.5 or above is supported".
So it's normal if you failed to restore the backup file of controller v3.x to the controller v5.x.
Please ignore the support email. Thank you for your valued feedback!