Cannot connect to open hotel wifi anymore, getting wrong key when connecting

Mabye just special problem for MT1300 and MT300N-V2. But I cannot fully confirm.

@alzhao I have created an account just to reply to this thread. I have been following this thread for the past month as I have had similar issues, where 203default, 211stable, 212snapshots (multiple), 215beta do not work for the router I’m trying to connect to.

I do not believe the user “mbg” is the only one with issue. I am using the Beryl and have been able to connect to other routers on other networks successfully before, but I am on travel and have not been able to connect to the router at this AirBnb (I do not have access to the router I’m trying to connect to).

I have also tried other “tricks” in other threads such as switch the frequency to 20 Hz only and trying to connect to the 5G router connection instead of the 2.4 with no success.

Is there anything I can provide you to assist with troubleshooting this issue? If yes, please provide the instructions on how to provide that.

I used to get the “wrong key” error message on 211stable, but after the upgrade to 215beta1, there is no wrong key message, but I am still unable to connect. I am able to connect directly to the wifi using my laptops (even my 10 year old laptop connects) and phones just fine, but I bought the travel router for a reason…

First try to connect to the WiFi, after it failed get the log. You can ssh to the router and use command logread to get the log. Or just get in luci.

2022-05-27_beryllog.zip (14.0 KB)
@alzhao See the uploaded text file for the log. Please let me know if you need anything else.

I found it connected the 5G of “Airbnb Guest” form the log.

But didn’t it lose it 5 seconds later?

@JerryZhao @elorimer

You are both correct. When connecting to the 5G of “Airbnb Guest”, it seems to connect for a brief time with the a pop-up message of Success and then automatically drops.

On the 2.4 when connecting, I am unable to connect. In the 211stable version, I had received a “Wrong Key” error message when trying to connect (I forget whether it was 2.4 or 5G).

Please let me know if you there’s anything else I can provide to help with the troubleshooting.

Make its 2.4G SSID and 5G SSID different. Then try it.

@JerryZhao The router I am trying to connect to is not accessible to me, so I am unable to make the SSID different for the 2.4 and 5.

I had considered that to be a possible cause for this issue, but only the Beryl is having issues connecting to that router (my phone and laptops are all able to connect to the router just fine). Is this a known bug for the Beryl? If yes, are there workarounds?

Different GL iNet routers have different chip sets. The MT1300, MT300m-v2 and n300 use the MTK chip sets and I think are still using proprietary drivers provided by GL iNet. I have seen on my n300 and others have reported issues getting the MTK based products to connect to some networks. I know that GL iNet has made changes over time to make this better, but all of my ARxxx based routers, that use a different chipset without the need for a proprietary driver seem to connect to different APs with fewer issues then I have had with my n300 router. Although I own multiple GL iNet routers, it is the reason I only own 1 GL iNet router based on the MTK chip set.

You may want to do a search through this forum on issues with the MTK based products.

1 Like

I checked the log. It connects and then disconnect immediatelly.

From the bssid I cannot find what is the device vendor. Can you find out what is the router they are using?

@alzhao According to the owner, I am actually connecting to an access point, which is an “UAP-AC PRO”. The main router is an AT&T provided router (I was not given a specific name/model for this) and the internet provider is through AT&T.

Please let me know if you need anything else for your troubleshooting.

Jumping in with the same issue on a UAP-AC and UAP-AC-PRO setup on their 7166 build. This happened after updating from their 4.xx builds

Are you using AX1800? Firmware 3.x does not have this problem?

I’m sorry I left out the details. I’m using Ar300m on current firmware. The UAP was on fw 6.0.1.9 and getting wrong key errors and was seeing those errors in the Unifi logs.

I think @spittlbm was referring to the upgrade from UAP-AC from 4.xx build to 7166 build?

I just got my new Flint, this one connects perfectly to the WiFi where the beryl has problems. Using newest stable for Flint.

Correct.

I suspect something similar is happening with both your original setup and mine.

Here are the pertinent logs from my 300M trying to connect to the Unifi UAP-AC-PRO: 300M06072022 - Pastebin.com