UNMS Docker setup - any feedback?

Currently reading
UNMS Docker setup - any feedback?

239
112
NAS
DS218+ 8GB RAM, DS212
Operating system
  1. Windows
Mobile operating system
  1. Android
  2. iOS
Setup UNMS on my NAS, trying to connect to my router and while UNMS can find the router, see all it's info (up time, MAC, FW version, model, etc.) it can't connect to it when I provide my router credentials.

Wondering if anyone here has any experience w/running UNMS on their NAS, and any suggestions.
Config below, I changed the TCP and UDP ports to avoid conflicts, and am using the revised TCP port for my connection.

Any steps I'm missing?

(I'm also asking in the Ubiquiti forum, but wanted to check here as well. Container I'm using is UNMS1-Nco640.

1585259643144.png
 
Hello Danabw,

I'm even missing a step before this my docker isn't even starting correctly, giving error "nc: bad address 'unms-postgres'", are you familiar with this?

Did you configure any specific "volume" or "environment" setting in the docker TAB?


 
239
112
NAS
DS218+ 8GB RAM, DS212
Operating system
  1. Windows
Mobile operating system
  1. Android
  2. iOS
@eco123 - I didn't do anything special to set volume or environment. Downloaded the UNMS Docker image from teh Registry tab, then started it (first time start it launches into the container Settings) from the Container tab. The only things I configured were port settings you can see in my screen shot above.

When I did launch the UNMS container after completing settings, it took a very long time to load, but finally did load and I could log into UNMS.

Are you using the Nico640 UNMS Docker container? That's the one I used.

At this point I believe my issues aren't w/the Docker/NAS side, as I've been unable to connect to my router (UNMS finds it, but can't make the connection to it) from Synology, from a Ubuntu VM using VirtualBox on my WIn laptop, or from a pi3 I have. I may reset my router and reload my config to see if that helps...I don't have to have UNMS working, but you know how it is, once you start on something like this you just want to make it work!! ;-)

I'm sorry I can't help you either!
 
239
112
NAS
DS218+ 8GB RAM, DS212
Operating system
  1. Windows
Mobile operating system
  1. Android
  2. iOS
@eco123

FYI - I worked w/Synology support and they weren't able to help me w/NAS instance of UNMS being unable to connect to the router.

They asked me if I could fall back to default ports (e.g., 443) but noted I could not as the NAS uses those for services, and they then said NAS isn't a supported platform, so can't help any further.

So I've fallen back to running a VirtualBox VM w/ubuntu in brided mode on laptop and that works fine, connection to router is immediate.

If you find a way to make it work on your NAS love to hear it, as I'd prefer not to have to run a VM on my laptop.
 
239
112
NAS
DS218+ 8GB RAM, DS212
Operating system
  1. Windows
Mobile operating system
  1. Android
  2. iOS
You know, I don't know. :) I've only ever run VMs via VirtualBox on my laptop (Windows). Never thought about running it on the NAS. I'm not sure that would help solve my basic problem, if I'd still the issue of not being able to use standard ports (443/80) which may be the blocking issue.

That said I am now very interested in whether I can run a VM on my DS218+...guess I'll have to go do some googling.
 
141
36
NAS
DS1815+
Operating system
  1. Linux
  2. macOS
Mobile operating system
  1. iOS
Or maybe you can create a macvlan in docker and then create the container. The benefit of this that you have all the ports then for your container. Look for the pihole/adguard thread here b
 

jeyare

Subscriber
2,486
833
NAS
Synology, TrueNAS
Operating system
  1. Linux
  2. Windows
Setup UNMS on my NAS, trying to connect to my router and while UNMS can find the router, see all it's info (up time, MAC, FW version, model, etc.) it can't connect to it when I provide my router credentials.

Wondering if anyone here has any experience w/running UNMS on their NAS, and any suggestions.
Config below, I changed the TCP and UDP ports to avoid conflicts, and am using the revised TCP port for my connection.

Any steps I'm missing?

(I'm also asking in the Ubiquiti forum, but wanted to check here as well. Container I'm using is UNMS1-Nco640.

View attachment 1012

So, step by step:
- you have Installed Ubiquiti Network Management System (UNMS) from Nico640 container
- all your ports are configured OK in Docker environment (2055/udp, 443, 80)
- did you mean, that you can't connect from UNMS portal directly to the router? Y/N
- what was the answer from the Authentication process, when you failed to connect to your router directly from the UNMS? Any Logs from /home/unms/data/logs ? When you are not familiar with SSH, you can use this way - It is also possible to download logs directly from the UNMS Web UI in Settings > Maintenance > Download Support Info
- you wrote: "Config below, I changed the TCP and UDP ports to avoid conflicts, and am using the revised TCP port for my connection." .... did you mean ports at NAS side? Because Container ports are unchanged. Then do you have open FireWall in NAS for such ports? Check it pls.
- what about your router logs?

Rest of your troubles:
1. When I did launch the UNMS container after completing settings, it took a very long time to load, but finally did load and I could log into UNMS.
Yes, it is ok, because, when you are performing usage of the UNMS on DS212+, it's really more than undersized, from performance point of view. There is CPU based on single core Marvell Kirkwood 88F6282, what is really too slow CPU for such system as UNMS. Even with the slow speed RAM and just 512MB for entire NAS.
Maybe you have different NAS.
 
239
112
NAS
DS218+ 8GB RAM, DS212
Operating system
  1. Windows
Mobile operating system
  1. Android
  2. iOS
Thanks, I'll look at that thread.

I am interested, generally, if my DSM281+ 8GB RAM could reasonably run a Ubuntu VM, if anyone has experience w/that level DSM running a VM. Not sure, but seems like it might be a little underpowered.
 

jeyare

Subscriber
2,486
833
NAS
Synology, TrueNAS
Operating system
  1. Linux
  2. Windows
Hello Danabw,

I'm even missing a step before this my docker isn't even starting correctly, giving error "nc: bad address 'unms-postgres'", are you familiar with this?

Did you configure any specific "volume" or "environment" setting in the docker TAB?


When you will read correctly container author's GitHub site, you will find how to setup the environment, even volume:

- ./volumes/unms:/config
 

jeyare

Subscriber
2,486
833
NAS
Synology, TrueNAS
Operating system
  1. Linux
  2. Windows
Thanks, I'll look at that thread.

I am interested, generally, if my DSM281+ 8GB RAM could reasonably run a Ubuntu VM, if anyone has experience w/that level DSM running a VM. Not sure, but seems like it might be a little underpowered.

Then you need correct your NAS from 212 to 218+ in your profile :cool: , because it is important for some help
DS218+ is too different and ready for UNMS in Docker, even more
 

jeyare

Subscriber
2,486
833
NAS
Synology, TrueNAS
Operating system
  1. Linux
  2. Windows
and also, your NAS has max. 6GB no 8GB ... to be sure - but still enough for the lot of containers
 
239
112
NAS
DS218+ 8GB RAM, DS212
Operating system
  1. Windows
Mobile operating system
  1. Android
  2. iOS
So, step by step:
- you have Installed Ubiquiti Network Management System (UNMS) from Nico640 container
- all your ports are configured OK in Docker environment (2055/udp, 443, 80)
- did you mean, that you can't connect from UNMS portal directly to the router? Y/N
- what was the answer from the Authentication process, when you failed to connect to your router directly from the UNMS? Any Logs from /home/unms/data/logs ? When you are not familiar with SSH, you can use this way - It is also possible to download logs directly from the UNMS Web UI in Settings > Maintenance > Download Support Info
- you wrote: "Config below, I changed the TCP and UDP ports to avoid conflicts, and am using the revised TCP port for my connection." .... did you mean ports at NAS side? Because Container ports are unchanged. Then do you have open FireWall in NAS for such ports? Check it pls.
- what about your router logs?

Rest of your troubles:
1. When I did launch the UNMS container after completing settings, it took a very long time to load, but finally did load and I could log into UNMS.
Yes, it is ok, because, when you are performing usage of the UNMS on DS212+, it's really more than undersized, from performance point of view. There is CPU based on single core Marvell Kirkwood 88F6282, what is really too slow CPU for such system as UNMS. Even with the slow speed RAM and just 512MB for entire NAS.
Maybe you have different NAS.

@jeyare

Thanks very much for your reply!

So, step by step:
- you have Installed Ubiquiti Network Management System (UNMS) from Nico640 container
  • Yes
- all your ports are configured OK in Docker environment (2055/udp, 443, 80)
  • Ports are mapped in the container settings: 8443:443, 8080:80 to avoid conflicting w/Synology services that use 443/80
- did you mean, that you can't connect from UNMS portal directly to the router? Y/N
  • UNMS can find the router and ID it. However when I try to connect from UNMS (enter admin credentials in UNMS) the connection fails to complete. I know that UNMS does reach the router, as the router updates w/a new UNMS key, but the router can't communicate back to UNMS to complete the connection.
- what was the answer from the Authentication process, when you failed to connect to your router directly from the UNMS? Any Logs from /home/unms/data/logs ? When you are not familiar with SSH, you can use this way - It is also possible to download logs directly from the UNMS Web UI in Settings > Maintenance > Download Support Info
  • I get a "Connection timeout" message in the UNMS UI.
  • UNMS logs attached
- you wrote: "Config below, I changed the TCP and UDP ports to avoid conflicts, and am using the revised TCP port for my connection." .... did you mean ports at NAS side? Because Container ports are unchanged. Then do you have open FireWall in NAS for such ports? Check it pls.
  • I don't use the Synology firewall, it is disabled.
  • The connection I am trying to make is within my home network, UNMS to router, then router talks back to UNMS. The same connection works from the VirtualBox Ubuntu UNMS instance on my laptop does work.
- what about your router logs?,
  • Synology support didn't seem to find anything useful in the router log, adding it here below:
Code:
tail -n 30 /var/log/unms.log
2020-03-29 20:15:23 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:15:23 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:15:43 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:15:43 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:16:03 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:16:03 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:16:23 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:16:23 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:16:43 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:16:43 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:17:03 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:17:03 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:17:23 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:17:23 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:17:43 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:17:43 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:18:03 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:18:03 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:18:23 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:18:23 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:18:43 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:18:43 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:19:03 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:19:03 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:19:23 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:19:23 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:19:43 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:19:43 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:20:03 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:20:03 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101

Thanks for any help/suggestions you may have! Running the UNMS instance on the NAS is the simplest solution for me, still hoping I can make that work.
 

Attachments

  • UNMS-Logs.zip
    1.8 MB · Views: 6
239
112
NAS
DS218+ 8GB RAM, DS212
Operating system
  1. Windows
Mobile operating system
  1. Android
  2. iOS
and also, your NAS has max. 6GB no 8GB ... to be sure - but still enough for the lot of containers

I upgraded the RAM! Added a 4GB to the expansion slot a while back, ran memory tests and it's working perfectly. :)
 
239
112
NAS
DS218+ 8GB RAM, DS212
Operating system
  1. Windows
Mobile operating system
  1. Android
  2. iOS
A
Then you need correct your NAS from 212 to 218+ in your profile :cool: , because it is important for some help
DS218+ is too different and ready for UNMS in Docker, even more

Ah, forgot that totally. Will do! I still have both, but the DS218+ is the actual working platform, DS212 just gets backups sent to it...
 

jeyare

Subscriber
2,486
833
NAS
Synology, TrueNAS
Operating system
  1. Linux
  2. Windows
@jeyare

Thanks very much for your reply!

So, step by step:
- you have Installed Ubiquiti Network Management System (UNMS) from Nico640 container
  • Yes
- all your ports are configured OK in Docker environment (2055/udp, 443, 80)
  • Ports are mapped in the container settings: 8443:443, 8080:80 to avoid conflicting w/Synology services that use 443/80
- did you mean, that you can't connect from UNMS portal directly to the router? Y/N
  • UNMS can find the router and ID it. However when I try to connect from UNMS (enter admin credentials in UNMS) the connection fails to complete. I know that UNMS does reach the router, as the router updates w/a new UNMS key, but the router can't communicate back to UNMS to complete the connection.
- what was the answer from the Authentication process, when you failed to connect to your router directly from the UNMS? Any Logs from /home/unms/data/logs ? When you are not familiar with SSH, you can use this way - It is also possible to download logs directly from the UNMS Web UI in Settings > Maintenance > Download Support Info
  • I get a "Connection timeout" message in the UNMS UI.
  • UNMS logs attached
- you wrote: "Config below, I changed the TCP and UDP ports to avoid conflicts, and am using the revised TCP port for my connection." .... did you mean ports at NAS side? Because Container ports are unchanged. Then do you have open FireWall in NAS for such ports? Check it pls.
  • I don't use the Synology firewall, it is disabled.
  • The connection I am trying to make is within my home network, UNMS to router, then router talks back to UNMS. The same connection works from the VirtualBox Ubuntu UNMS instance on my laptop does work.
- what about your router logs?,
  • Synology support didn't seem to find anything useful in the router log, adding it here below:
Code:
tail -n 30 /var/log/unms.log
2020-03-29 20:15:23 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:15:23 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:15:43 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:15:43 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:16:03 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:16:03 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:16:23 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:16:23 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:16:43 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:16:43 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:17:03 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:17:03 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:17:23 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:17:23 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:17:43 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:17:43 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:18:03 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:18:03 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:18:23 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:18:23 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:18:43 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:18:43 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:19:03 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:19:03 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:19:23 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:19:23 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:19:43 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:19:43 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101
2020-03-29 20:20:03 INFO  unms: connecting to 192.168.10.5:8443
2020-03-29 20:20:03 ERROR connection error (192.168.10.5:8443): HS: ws upgrade response not 101

Thanks for any help/suggestions you may have! Running the UNMS instance on the NAS is the simplest solution for me, still hoping I can make that work.

seems to be ws problem there
look at here and check it pls, send me result
 
239
112
NAS
DS218+ 8GB RAM, DS212
Operating system
  1. Windows
Mobile operating system
  1. Android
  2. iOS
Crap...I Googled and Googled on this, I don't know how you found that discussion so quickly.

Regarding "here" above, do you mean to complete the steps at the end of the discussion thread you pointed to, namely?
  • Create a record on my internal DNS server, such as "unms.localdomain.local" pointing to my NAS' IP address
    • I did this on the EdgeRouter
      (set system static-host-mapping host-name <unms.localdomain.local> inet <192.168.10.5>
      commit
  • then in UNMS settings :
    • I did all of below
    • UNMS/UNMS Hostname/IP : replaced the IP address with a DNS record
    • UNMS/Date format : changed to ISO (YYYY-MM-DD), not sure this makes any difference
    • Devices/Ping address : put the DNS name instead of the NAS' IP address
That didn't help - UNMS and the router still can't complete their connection, same connection timeout message in UNMS.
 
239
112
NAS
DS218+ 8GB RAM, DS212
Operating system
  1. Windows
Mobile operating system
  1. Android
  2. iOS
I noticed another post that mentioned web socket...missed the "ws" in "...ws problem" in your post initially.

I tried the tests recommended on the UI support page referenced in the post in the thread you found. Unfortunately the support page doesn't really say what to do if your results don't match up w/expectations... :)

Ping/traceroute, etc.

Ping
- successful, I can ping via ip or local host name.
traceroute -n (could not use -n parameter, gave bad command result)
Code:
[email protected]~$ traceroute unms.localdomain.local
traceroute to unms.localdomain.local (192.168.10.5), 30 hops max, 38 byte packets
 1  unms.localdomain.local (192.168.10.5)  0.219 ms  0.159 ms  0.147 ms
[email protected]:~$ traceroute 192.168.10.5
traceroute to 192.168.10.5 (192.168.10.5), 30 hops max, 38 byte packets
 1  unms.localdomain.local (192.168.10.5)  0.294 ms  0.233 ms  0.145 ms
curl --insecure https://192.168.x.x:443/v2.1/nms/version
Code:
[email protected]:~$ curl --insecure https://192.168.10.5:8443/v2.1/nms/version
{"version":"1.1.6","build":"1.1.6+release.e6ec4747d.20200313095214","deployment":"","time":"[email protected]:~$

Web socket test: Didn't see anything like the results the UI page said I should see

UI support page expected results:
Code:
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: xxxxxxxxxxxxxxxxxxxxxxxxxx=

My results:
Code:
HTTP/1.1 200 OK
Server: nginx
Date: Tue, 31 Mar 2020 00:08:52 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 6587
Connection: keep-alive
last-modified: Fri, 13 Mar 2020 09:52:05 GMT
etag: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
vary: origin,accept-encoding
access-control-allow-origin: http://example.com:80
access-control-expose-headers: x-auth-token
cache-control: no-cache
accept-ranges: bytes
strict-transport-security: max-age=15768000
x-content-type-options: nosniff
x-download-options: noopen
x-xss-protection: 1; mode=block

I'm at a loss to get anything from this, likely it is clearer to you. :D Thanks for looking at this.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

Replies
3
Views
245
  • Question
If your NAS indeed is a DS416j, then I am afraid your memory is playing a trick on you. The cpu of the...
Replies
4
Views
827
  • Solved
That is interesting to know. Thank you! Probably nothing. And after some further consideration, I feel...
Replies
4
Views
323
  • Question
I haven't thought about it as a file system level cache. If it is, it would make sense that both benefit...
Replies
8
Views
310
I am struggling with that since I am only a copy & paste hacker. I have installed netdata on my Synology...
Replies
0
Views
155
OK, I have done those mappings (see screenshots). The status still shows the same error. File downloads...
Replies
3
Views
395
VPN, Tor, Tailscale, proxy, cell phone data... Not worth risking NAS and your network security IMO...
Replies
4
Views
323

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Top