-
-
Notifications
You must be signed in to change notification settings - Fork 269
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
NanoPiR2s Edge X 0.61 not working #3637
Comments
Nano Pi R2s 0.61 Firmware not working, no aggregation no vos server connextion token key missing. Tried with Edge X same problem it wont even show server status. So which hardware is rhe best for testing? |
So R2S is booting correctly ? |
NanoPi R2s with 0.61 6.6 wont show lan and does not connect to lan 192.168.100.1. Edge X 0.61 6.6 boots coorectly, assigns lan 192.168.100.1 I can connect to gui but when setting are applied, keys and ips of wan, the status page wont work.
Alvaro Panesso
Correo | ***@***.***
Web | Pici.com.co
Insta | Picicorp
Whtasapp | +573108490885
…________________________________
De: Ycarus (Yannick Chabanois) ***@***.***>
Enviado: Monday, November 4, 2024 3:40:30 AM
Para: Ysurac/openmptcprouter ***@***.***>
Cc: Alvaro Panesso ***@***.***>; Author ***@***.***>
Asunto: Re: [Ysurac/openmptcprouter] NanoPiR2s Edge X 0.61 not working (Issue #3637)
So R2S is booting correctly ?
You configured it correctly with the IP and key of your VPS server ?
—
Reply to this email directly, view it on GitHub<#3637 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMUMNJM4BJZGKSMZDQMTFSTZ64XH5AVCNFSM6AAAAABRDE7Y6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJUGEYDKMZVHE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I don't understand, it's about NanoPi R2S or about Ubiquiti EdgeRouter X or both ? |
I´m workinmg with both. The Edge is bricked will continue with NanoPi R2s. |
For R2S, I think it's a network issue. |
Expected Behavior
Current Behavior
Specifications
The text was updated successfully, but these errors were encountered: