-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gateway error when going to SETUP #763
Comments
Can you post a screenshot of the main status page immediately before hitting 'setup'? |
Note that this hardware is not in the support list. |
Oh? There's a difference between it and a Gen2? |
Please click on the text reading "!!!! UNSUPPORTED DEVICE !!!!" and post the information it should display. It's probably easy to add this. |
No such text |
? I see it in red on your first photo ? |
Oh duh..the banner.. node: NOCALL-80-102-111 !!!! UNSUPPORTED DEVICE !!!! br-lan F0:9F:C2:51:66:6F /proc/cpuinfo nvram |
BTW, the firmware is clearly shown at the selector webpage. That's where I got it |
While I see "Ubiquiti PowerBeam 5AC Gen2" and the "Ubiquiti PowerBeam 5AC 500" in the selector, I do not see the 400 variant listed. |
Am I mistaken that the hardware reports itself as "machine : Ubiquiti PowerBeam 5AC Gen2" |
That's reporting what the firmware loaded onto the device is, not the device itself which is identified by the hex code boardid. |
I saw /proc/cpuinfo and assumed it read the info from there OK, well guess I'll wait for the build |
A build should now be available. If you could verify that'd be fantastic. |
Really sorry for the delay. Yes, all is working fine with the new build |
I just flashed 2 PBE-5AC-400 with the latest nightly build (dated today). All went fine but when trying to get to SETUP, I'm prompted for credentials (which I enter) and then I'm greeted with a "Bad Gateway The process did not produce any response" error.
This is happening on 2 of 2 units
The text was updated successfully, but these errors were encountered: