New Member
Posts: 3
Registered: ‎08-17-2015
Accepted Solution

PowerBeam M5 can't connect to UNMS

PowerBeam M5 , can't connect to UNMS 0.9.3

 

XW.v6.0.7-beta.31512.170822.1626

 

only PowerBeam has this problem , other devices work great with UNMS

I've got this :

UNMS [?]: Enabled but unreachable

 

syslog:

 

Aug 26 08:41:08 udapi-bridge[20659]: connecting to 138.68.109.xx:443
Aug 26 08:41:08 udapi-bridge[20659]: connection established
Aug 26 08:41:08 udapi-bridge[20659]: failed to decrypt AES-encrypted message
Aug 26 08:41:08 udapi-bridge[20659]: failed to decode message from UNMS
Aug 26 08:41:08 udapi-bridge[20659]: disconnecting

 

 

UNMS 0.9.3 is on cloud digitalocean 


Accepted Solutions
Ubiquiti Employee
Posts: 52
Registered: ‎02-27-2017
Kudos: 9
Solutions: 7

Re: PowerBeam M5 can't connect to UNMS

@szymek I appears there is an issue in 0.9.x that prevents PowerBeams M2/5 from connecting. It's going to be fixed in the next release. We might consider releasing 0.9.4 with the fix, but there is only very limited support for AirMax M devices in 0.9.x so we will probably wait for 0.10.0 (scheduled in two weeks) which also comes with more AirMax features.

View solution in original post


All Replies
New Member
Posts: 20
Registered: ‎04-13-2015
Kudos: 1

Re: PowerBeam M5 can't connect to UNMS

I am having the same issue on PowerBeam M2's and M5"s

Ubiquiti Employee
Posts: 52
Registered: ‎02-27-2017
Kudos: 9
Solutions: 7

Re: PowerBeam M5 can't connect to UNMS

[ Edited ]

@szymek @jonwentz 

We are currently investigating the issue. I have few questions for you:

 

- How did you connect the devices? Through UNMS Discovery, UMobile or did you manually copy&pasted UNMS key to device?

- Did all PowerBeams failed to connect or only some?

- We had a bug in 0.9.0 that could cause this behaviour - Did you first tried to connect the devices with 0.9.0 and later updated to 0.9.3?

 

Anyway the error is in the AES key exchange process. You can find workaround on our wiki. Find the key by device's MAC address, delete it and connection should work.

New Member
Posts: 3
Registered: ‎08-17-2015

Re: PowerBeam M5 can't connect to UNMS

- Copy&pasted UNMS key to device

- All PowerBeams has failed to connect

- First 0.9.2 , later updated to 0.9.3 , problem was same on 0.9.2 and 0.9.3

Ubiquiti Employee
Posts: 52
Registered: ‎02-27-2017
Kudos: 9
Solutions: 7

Re: PowerBeam M5 can't connect to UNMS

@szymek I appears there is an issue in 0.9.x that prevents PowerBeams M2/5 from connecting. It's going to be fixed in the next release. We might consider releasing 0.9.4 with the fix, but there is only very limited support for AirMax M devices in 0.9.x so we will probably wait for 0.10.0 (scheduled in two weeks) which also comes with more AirMax features.

Ubiquiti Employee
Posts: 317
Registered: ‎01-26-2017
Kudos: 95
Solutions: 32

Re: PowerBeam M5 can't connect to UNMS

We have released UNMS hotfix v0.9.4. Please let us know if you still have issues connecting PowerBeams after the update.

New Member
Posts: 20
Registered: ‎04-13-2015
Kudos: 1

Re: PowerBeam M5 can't connect to UNMS

Now have all PowerBeam M2's and M5's connected to UNMS

Regular Member
Posts: 486
Registered: ‎03-10-2009
Kudos: 262
Solutions: 9

Re: PowerBeam M5 can't connect to UNMS

Same issue over here:

 

PowerBeam M5 with v6.1.2, and UNMS 0.10.3

 

I can connect to UNMS all AC devices, but none M series can connect :-(

 

Víctor De La Nuez
WiFi Canarias
Wireless ISP, Canary Islands, Spain
Ubiquiti Certified Trainer
¡Visita nuestro canal en youtube!
New Member
Posts: 4
Registered: ‎05-24-2017

Re: PowerBeam M5 can't connect to UNMS

Have the same problem with Nanostation locoM5

Some can connect but two devices can't connect to the UNMS

 

I can ping both devices from UNMS and visa verca and  devices can ping UNMS server. Both devices are located in the same subnet as normal ones.

 

Take a look at attachment, looks like connection to the UNMS server is broken for some reason.

2017-10-21_22-24-28.png
New Member
Posts: 18
Registered: ‎04-20-2017
Kudos: 1
Solutions: 1

Re: PowerBeam M5 can't connect to UNMS

My PowerBeamM5  v6.13   can't connect to UNMS  v0.10.4

need help

 

Nov 29 22:55:53 udapi-bridge[3217]: failed to write CA certificates to temporary file
Nov 29 22:55:53 udapi-bridge[3217]: connecting to 192.168.0.5:443
Nov 29 22:56:53 udapi-bridge[857]: watchdog: restart!
Nov 29 22:56:53 udapi-bridge[3218]: udapi-bridge 0.1.0-no-git
Nov 29 22:56:53 udapi-bridge[3218]: ca_cert_load_all_file: error scanning /etc/persistent/udapi-bridge: No such file or directory
Nov 29 22:56:53 udapi-bridge[3218]: failed to write CA certificates to temporary file
Nov 29 22:56:53 udapi-bridge[3218]: connecting to 192.168.0.5:443
Nov 29 22:57:53 udapi-bridge[857]: watchdog: restart!
Nov 29 22:57:53 udapi-bridge[3219]: udapi-bridge 0.1.0-no-git
Nov 29 22:57:53 udapi-bridge[3219]: ca_cert_load_all_file: error scanning /etc/persistent/udapi-bridge: No such file or directory
Nov 29 22:57:53 udapi-bridge[3219]: failed to write CA certificates to temporary file

 

Ubiquiti Employee
Posts: 3,444
Registered: ‎09-08-2017
Kudos: 1326
Solutions: 261

Re: PowerBeam M5 can't connect to UNMS

@ve2se Hello Jean-Pierre. This is an interesting case. First of all it would be good to check the network path between device and UNMS. You can use this article as a guide. If the device can see to UNMS then there is probably something wrong there. We would like to get your logs and MAC address of the device to find out what is happening. You can send those to my email radek.skrivan(at)ubnt.com

UBNT_Alternate_Logo.png
UNMS Support - If you want to report an issue please use this guide.

Check out our ever-evolving Help Center for answers to many common questions!

New Member
Posts: 18
Registered: ‎04-20-2017
Kudos: 1
Solutions: 1

Re: PowerBeam M5 can't connect to UNMS

Solve my issue  ,  Network tab , wrong  secondary dns ip

Jean-Pierre

Highlighted
New Member
Posts: 5
Registered: ‎05-09-2017

Re: PowerBeam M5 can't connect to UNMS

I am having the same issue with my Rocket M3, Nanobridges and Nanostations. They all have v6.1.3 and I am getting the error - Enabled but unreachable.

 

The log shows the following:

 

Dec  7 17:00:43 udapi-bridge[5231]: failed to write CA certificates to temporary file
Dec  7 17:00:43 udapi-bridge[5231]: connecting to 10.70.85.243:443
Dec  7 17:01:04 udapi-bridge[5231]: connection error (10.70.85.243:443)
Dec  7 17:01:04 udapi-bridge[5231]: connecting to 10.70.85.243:443
Dec  7 17:01:25 udapi-bridge[5231]: connection error (10.70.85.243:443)
Dec  7 17:01:25 udapi-bridge[5231]: connecting to 10.70.85.243:443
Dec  7 17:01:43 udapi-bridge[3590]: watchdog: restart!
Dec  7 17:01:44 udapi-bridge[5238]: udapi-bridge 0.1.0-no-git
Dec  7 17:01:44 udapi-bridge[5238]: ca_cert_load_all_file: error scanning /etc/persistent/udapi-bridge: No such file or directory
Dec  7 17:01:44 udapi-bridge[5238]: failed to write CA certificates to temporary file
Ubiquiti Employee
Posts: 3,444
Registered: ‎09-08-2017
Kudos: 1326
Solutions: 261

Re: PowerBeam M5 can't connect to UNMS

@Guderz90  It seems like a network problem between the device and UNMS. Can you please check that connection? Here is an article with some basic guide. It may also be worthwhile to check your DNS settings since it helped @ve2se solve his situation.

UBNT_Alternate_Logo.png
UNMS Support - If you want to report an issue please use this guide.

Check out our ever-evolving Help Center for answers to many common questions!

New Member
Posts: 8
Registered: ‎01-21-2018

Re: PowerBeam M5 can't connect to UNMS

can you print screen where to get the unms key

New Member
Posts: 5
Registered: ‎05-09-2017

Re: PowerBeam M5 can't connect to UNMS

[ Edited ]

On the user interface of the UNMS server, you click and the new box that pops up has the link for the key which you can copy and paste on the services tab of the device.

EDIT: Screenshot deleted for security reasons.

New Member
Posts: 1
Registered: ‎11-08-2014

Re: PowerBeam M5 can't connect to UNMS

Hi Guys !!

 

I faced a similar issue. The UNMS status shows "Enabled but Unreachable". The network connectivity to the UNMS server was fine. I was able to ping to the UNMS server.

 

I did the following steps to resolve this issue.

 

1- Disbale the UNMS service from the "Services" tab.

2- Saved the Settings.

3- Enable the UNMS service again.

4- Clicked the "Edit" button next to Key and pasted the Key from UNMS portal [Settings -> Connection].

5- Save the settings again.

6- Now, check the UNMS status from the "Main" tab

 

 

 

Ubiquiti Employee
Posts: 3,444
Registered: ‎09-08-2017
Kudos: 1326
Solutions: 261

Re: PowerBeam M5 can't connect to UNMS

@juberpasha  Hello Juber. The process you describe should be enough to solve some issues. I am not sure if your issue is currently fixed or not. If there is still an issue I can help you if you send me your UNMS logs and a device support info from the affected device. Please, send those files to my email radek.skrivan(at)ubnt.com and include URL of this thread in the message.

UBNT_Alternate_Logo.png
UNMS Support - If you want to report an issue please use this guide.

Check out our ever-evolving Help Center for answers to many common questions!

New Member
Posts: 1
Registered: ‎09-03-2018

Re: PowerBeam M5 can't connect to UNMS

In my case:

UNMS 0.12.2

in one time, all devices lost connection with UNMS "Enabled but unreachable"

My solution:

1. In UNMS, delete all problem devices

2. On each device, change fdqn name to IP address of UNMS server.

3. Authorize devices in UNMS server

P.S. I understand that devices can not connect by server name, but I do not understand why.

in Tools/Traceroute - device resolve name of UNMS server normally.

Ubiquiti Employee
Posts: 3,444
Registered: ‎09-08-2017
Kudos: 1326
Solutions: 261

Re: PowerBeam M5 can't connect to UNMS

@dsm150 Hello Alex. 

I understand that devices cannot connect by server name, but I do not understand why in Tools/Traceroute - device resolve name of UNMS server normally.

This is a rather complex issue. There may be a number of possible reasons for this behavior. From the top of my head, I remember a case where a Primary DNS was filled accurately but secondary DNS was not filled at all, and this configuration caused the device to be unable to connect to UNMS while using a hostname, but pinging the hostname worked all right. The cause was that ping used the primary DNS while UNMS connector used the secondary one. Also, there is a bug, specific to EdgeSwitch devices. Once a connection to UNMS is established it is not attempted again even if something causes it to break. It is necessary to restart the switch to reconnect to UNMS. 

The first step, to find out what happened would definitely be checking the logs

UBNT_Alternate_Logo.png
UNMS Support - If you want to report an issue please use this guide.

Check out our ever-evolving Help Center for answers to many common questions!