I am trying to setup a brand new Banana Pi M1+ onto Balena. I have several Raspberry Pis in other fleets, on the same network, that are fully connected.
However the Banana Pi, connects, but never establishes its VPN into Balena.
Using the Local Balena SSH I was able to get in and run the systemctl status for openvpn, and see this error.
This appears to be even before any code or containers that I would be deploying to it, is there a problem with the certs? Is this something I can fix?
EDIT:
Also just to clarify, I am not using openBalena or anything, this is the normal hosted Balena.
I did try re-flashing to a new SD card, but I only have one of the physical devices. Both instances only ever get to ‘Heartbeat’ only. If I deploy code, it runs just fine and I can locally get to it, but I cann ot use any of the functions that need the VPN, like the Public Device URL.
Hi, could you share the output of the commands journalctl -u openvpn -xef and openvpn --version on your bananaPi device? This is quite an old OS version and we have seen some issues with openvpn compatibility, before, but having some extra logs might help determine the cause.
If you guys need me to open this one up for Remote Support somehow, I am more than willing to. I understand that the nature of the problem is that its not hitting the VPN, so I can setup another device on the same network that IS (like a Raspberry Pi) and allow you guys to get in that way if needed.
Sorry for hijacking the thread, but I’m also having issues with BananaPI. I’m trying to use the supervisor API, but since Banana’s supervisor is still in version 7, it won’t work with my script. The OS is still 2.12.
I cannot see anything obvious that explains the problem on the logs. My first instinct is that this could be a time synchronization issue, but we would need more testing to confirm.
One thing you could both try is the following.
We publish our test images in our staging site balena-staging.com and I see there are newer OS images (2.46.1) for the bananaPI M1+. You can download one of the images from that site and then configure it to run against balena-cloud using the balena os configure command from our CLI.
If the VPN / missing supervisor endpoints persist, we can take it from there.
I also wanted to let you know that we are working on improvements to our OS deployment process so soon device type images will be created much faster after a OS changes are published. We have no hard ETA on this feature, but the improvements are being actively worked on.
Hello, I am afraid im not familiar with the balena-staging.com site. That site directly doesnt seem to load, but balena-staging.io does. I tried signing up at the io version, but never got the verification email.
I tried looking on the github page for the balena account, but dont see anything specific to staging. Looking at other forum posts it does look like there is a staging side of Balena you are supposed to be able to sign up for?
I checked the spam filter a few times but no go, perhaps im just not being patient enough.
Hello @stokes776 I spoke with the balena devices team.
It looks like the OS available on staging (2.46.1+rev2) is not going to be released on production. The current draft image in production is based on 2.99.26, so it’s pretty old compared with the current one.
At balena we are trying to automatize all the new OS releases with all the device types. Sadly the bananaPi M1+ does not have an automated testing. At the moment, the recommendation here is to support this device yourself until we have customers requesting for us to support it or a community member want to support it themselves in production.
Hello @fjuliofontes welcome to the balena community!
We do not recommend to use staging environment unless you have to test an OS version that will go to production. Why would you like to use the staging version?
Hello,
For the same reason as @stokes776. I’m currently testing the BananaPi-M1+ and I’m having the exact same issue. Impossible to have an ssh connection over the balena dashboard.
@fjuliofontes sorry for replying too late. Sadly as we said above the OS version is very old and there are some incompatibilities with the current VPN version we are running.
Currently the only possibility is that you can support your own OS following the balena instructions, as the focus of the balenaOS team is on OS automatization right now.
I know it’s not the best solution for you, but we can’t do much more here. Let us know if you need support we will be happy to help
Hi, we are currently deciding whether adding the bananaPi to the automated CI/CD pipeline is feasible or we will be forced to deprecate the device type support.
