Archer BE230 - Firmware v1.2.5 - Possible Open VPN Client bug
Archer BE230 - Firmware v1.2.5 - Possible Open VPN Client bug
Since upgrading to the above version I've not been able to get any Open VPN client connections working for TCP and UDP. Any ideas?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
That sounds crazy, but I received the same issue on start of March and was able to fix it just by reduce name of VPN Client in tp-link admin setup panel.
I used template like [City Country VPNProvider] and it didn't work - was permanently in Status Connecting, but after change name to some short view with 3-5 letters all OpenVPN clients were connected.
WireGuard is worked with any name. Try this hack, maybe will help.
- Copy Link
- Report Inappropriate Content
Hello @DanniCatsville,
Welcome to our community.
May I know whether your router is Archer BE230-v2-1.3.1 Build 20260106 rel.39388?
We have a beta firmware that may help it. If you can cooperate with us for further analysis, our tech team will likely reach out to you via email to continue troubleshooting. Please check your email inbox and confirm.
Thank you.
- Copy Link
- Report Inappropriate Content
@Joseph-TP Hello.
I rechecked this and can confirm that my router has firmware Archer BE230 v2.0 1.3.1 Build 20260106 rel.39388(4555).
Rgarding trying to use beta firmware - sorry, but don't think I can continue to be free QA specialist for TP-Link company, just have no time for it and don't want to take some risks again. I spent a few working day to verify the issue and troubleshooting instead to have them as really working days. And currently - OpenVPN connections are working for me. If my finding is correct, hope you will be able to test it and release correct firmware.
I understand that mistakes is happens, but was surprised by the lack of quality regression testing :) Is this issue specific for one routers model or for some amounts? As I understand, BE230 is like middle+ segment device from one of the newest line, so would like to have stable updates.
Thanks.
- Copy Link
- Report Inappropriate Content
Hi @DanniCatsville ,
Thanks for getting back to us.
We fully understand your feelings and respect your final choice.
More information and testing are needed to pinpoint the cause more accurately. If possible, you can also email us your backup file to help us better reproduce the anomaly you described. Of course, all of this is based on your wishes, and we fully understand and respect your decision.
We will also finalize the solution as soon as possible. I will update this as soon as there is any progress.
Best Regards.
- Copy Link
- Report Inappropriate Content
I had the same issue with OpenVPN suddenly stuck on "Connecting" post 1.3.1 firmware upgrade on BE230 V2. I followed the suggestion to change the VPN Description field from "BLA BLA" to "BLA" and suddenly everything works. This is a ridiculous bug which I assume you should be able to fix rather quickly and easily.
Thanks
- Copy Link
- Report Inappropriate Content
Hello @Val-MT ,
Thanks for your feedback and test results.
If it's convenient, we have a beta firmware version that might help. You can test the beta firmware to see if it works. If not, please provide us with the backup file or system log, as this will be helpful for further analysis.
The tech team will likely reach out to you via email to continue troubleshooting. Please check your email inbox and confirm.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 893
Replies: 16
Voters 0
No one has voted for it yet.