oznu / docker-unms Goto Github PK

When validating the host, letsencrypt uses a challenge key over http/80. That port is already occupied by fluentd so the auth fails with

The client lacks sufficient authorization :: Invalid response from

I only need this ones until I setup the certificate. Renewal doesn't need this afterwards. Any idea how to temporary move fluentd on another port?

Thanks for putting this package together. My first attempt at running this docker image in a container on my Synology NAS resulted in this error message:

UNMS backup failed to release sources { Error: ELOOP: too many symbolic links encountered, unlink 'data/unms-backups/restore/download'

Any ideas as to what could cause that with a vanilla install? (Thanks BTW if you choose to help)

My config is here:

   "cap_add" : null,
   "cap_drop" : null,
   "cmd" : "",
   "cpu_priority" : 50,
   "devices" : null,
   "enable_publish_all_ports" : false,
   "enable_restart_policy" : true,
   "enabled" : false,
   "entrypoint_default" : "/init",
   "env_variables" : [
      {
         "key" : "PATH",
         "value" : "/home/app/unms/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
      },
      {
         "key" : "QEMU_ARCH",
         "value" : "x86_64"
      },
      {
         "key" : "S6_KEEP_ENV",
         "value" : "1"
      },
      {
         "key" : "NODE_VERSION",
         "value" : "8.11.3"
      },
      {
         "key" : "YARN_VERSION",
         "value" : "1.6.0"
      },
      {
         "key" : "NGINX_UID",
         "value" : "1000"
      },
      {
         "key" : "NGINX_VERSION",
         "value" : "nginx-1.12.2"
      },
      {
         "key" : "LUAJIT_VERSION",
         "value" : "2.1.0-beta3"
      },
      {
         "key" : "PGDATA",
         "value" : "/config/postgres"
      },
      {
         "key" : "POSTGRES_DB",
         "value" : "unms"
      },
      {
         "key" : "QUIET_MODE",
         "value" : "0"
      },
      {
         "key" : "WS_PORT",
         "value" : "443"
      },
      {
         "key" : "PUBLIC_HTTPS_PORT",
         "value" : "8443"
      },
      {
         "key" : "PUBLIC_WS_PORT",
         "value" : "8443"
      },
      {
         "key" : "SECURE_LINK_SECRET",
         "value" : "ObviouslyNotThisValue"
      },
      {
         "key" : "SSL_CERT",
         "value" : ""
      }
   ],
   "exporting" : false,
   "id" : "Some_Hex_Number",
   "image" : "oznu/unms:latest",
   "is_ddsm" : false,
   "is_package" : false,
   "links" : [],
   "memory_limit" : 0,
   "name" : "oznu-unms-1",
   "network" : [
      {
         "driver" : "bridge",
         "name" : "bridge"
      }
   ],
   "network_mode" : "bridge",
   "port_bindings" : [
      {
         "container_port" : 443,
         "host_port" : 8443,
         "type" : "tcp"
      }
   ],
   "privileged" : false,
   "shortcut" : {
      "enable_shortcut" : false
   },
   "ulimits" : null,
   "use_host_network" : false,
   "volume_bindings" : [
      {
         "host_volume_file" : "/docker/UNMS",
         "mount_point" : "/config",
         "type" : "rw"
      }
   ],
   "volumes_from" : null
}

Thank you for your perfect job.
It's working fine on my synology DS1515+ nas in doker.
Only 1 issue I found is a friquent logging. I seem it set debug mode. Any chance to edit it to lower?

Hello

do you plan to make docker image for unms 0.14.x on armhf ?

thanks

Hi There

I believe that UNMS 0.13 now supports netflow, and by default it should run on port 2055. However, this port does not appear to be getting exposed by Docker? I have tried to manually expose the port, but still no luck getting UNMS to see the netflow packets. Does anything else need to change in the core of UNMS to allow it to accept the incoming netflow packets that 0.13 support?

When installing Docker Compose using the following line

sudo apt-get -y install python-setuptools && sudo easy_install pip && sudo pip install docker-compose

and also using other install methods I get the following error.

Command "/usr/bin/python /usr/local/lib/python2.7/dist-packages/pip-19.0.3-py2.7.egg/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-rdnEhr/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple --extra-index-url https://www.piwheels.org/simple -- setuptools wheel "cffi>=1.4.1; python_implementation != 'PyPy'"" failed with error code 1 in None

Not sure where to go from here. Everything goes well up to this point. Clean install of Raspbian Stretch Lite.

My unms.log is huge - 11 GB.

Is it possible to:

1. manually clear log
2. automatically compress (or clear) log as it is in official installation? (https://community.ubnt.com/t5/UNMS-Beta/Manually-Clear-Logs-in-UNMS/td-p/2713276)

Otherwise project works fantastic - thank you!

Hey guys,

the container and UNMS running fine for me but my disk is running out of space ? How could i save disk space or delete the data after 14 or 28 days ?

Snot

Hi,

Thanks for the instructions. I've just got a Raspberry Pi 4 and I'm going to try to run UNMS on it. First challenge was to install it.

On the wiki 2. Install Docker Compose this step worked for me with just:
sudo apt-get install docker-compose

I'm new to this game so unit wants to get a clear explanation on updating docker-unms.

I did the following: docker-compose pull unms
And got the following: Done

but no update still on 0.12.1

also restored, stop and installed it and then restarted it

Anything I'm missing or is there still no update from 0.12.1?

When I launch the container, I get the following error in the docker logs

nc: bad address 'unms-postgres'
nc: bad address 'unms-postgres'
nc: bad address 'unms-postgres'
nc: bad address 'unms-postgres'
...

Docker image docker.io/oznu/unms download has failed. Please visit Docker Log for more information.

I'm using certbot on my host system to renew/update my (wildcard) certificates from Let's Encrypt.

1. How do I use these certificates with this UNMS container?

2. When the certificates expire and are renewed, how do I update the UNMS container?

The oznu/unms Docker image will no longer be receiving updates.

While this image has been reasonably popular, with over 5 million pulls on Docker Hub, keeping up with the updates and changes being made to UNMS by Ubiquiti is beyond my current capacity.

For the Synology and ARM users, I would suggest raising a feature request on the UNMS forums for offical support to be added: https://community.ui.com/tags/unms/questions.

UNMS version 0.13.3 will still continue to be available via this image.

I have tried install UNMS on Raspberry Pi3 three times already but at the end the result is the same all the time. After installation UNMS works fine (can be configured, can manage devices) but after a few days wed interface dies and it shows only "UNMS is starting... This should not take more than a minute". But it takes forever. Raspberry became hot and it is obviously that it is quite active. Also log show that it's activity.
This command does not help: docker-compose restart unms

How can I start up web interface?

Thank you!

Hi there!

Thanks for making this container, it should make managing the UNMS deployment far easier (once I have got it working!).

I'm seeing internal server error when I try to hit UNMS from my reverse proxy. I wonder if some of the services in your container require ports mapping? I'm running in Docker Swarm mode, with your container attached to an overlay network, which usually means all ports are exposed without mapping anything. Service labels are set for Traefik to read, and configure the FE>BE routing. It's set to map the FE to port 443 on your container, and to use HTTPS.

I've set your container env vars for WS_PORT, PUBLIC_WS_PORT and PUBLIC_HTTPS_PORT all to be 443.

If I map ports to the container host, I'm able to reach the UNMS interface from the LAN.

I added -p 85:85 -p 445:445

and I'm unable to get to the website I get the following errors
[ { "Id": "91de77edd92a3a5cca584e03628e2990e07a67967144a6a7d6248c927dd3b401", "Created": "2019-01-31T19:43:25.644172796Z", "Path": "/init", "Args": [], "State": { "Status": "running", "Running": true, "Paused": false, "Restarting": false, "OOMKilled": false, "Dead": false, "Pid": 23190, "ExitCode": 0, "Error": "", "StartedAt": "2019-01-31T19:43:25.979544077Z", "FinishedAt": "0001-01-01T00:00:00Z" }, "Image": "sha256:838918070999ddf382a2d21b1a13f0c1f48a3f50aa26fb408c9c5fff2b808f42", "ResolvConfPath": "/var/lib/docker/containers/91de77edd92a3a5cca584e03628e2990e07a67967144a6a7d6248c927dd3b401/resolv.conf", "HostnamePath": "/var/lib/docker/containers/91de77edd92a3a5cca584e03628e2990e07a67967144a6a7d6248c927dd3b401/hostname", "HostsPath": "/var/lib/docker/containers/91de77edd92a3a5cca584e03628e2990e07a67967144a6a7d6248c927dd3b401/hosts", "LogPath": "/var/lib/docker/containers/91de77edd92a3a5cca584e03628e2990e07a67967144a6a7d6248c927dd3b401/91de77edd92a3a5cca584e03628e2990e07a67967144a6a7d6248c927dd3b401-json.log", "Name": "/UNMS", "RestartCount": 0, "Driver": "overlay2", "Platform": "linux", "MountLabel": "", "ProcessLabel": "", "AppArmorProfile": "docker-default", "ExecIDs": null, "HostConfig": { "Binds": [ "/etc/localtime:/etc/localtime:ro", "/sharedfolders/appdata/UNMS:/config:rw" ], "ContainerIDFile": "", "LogConfig": { "Type": "json-file", "Config": {} }, "NetworkMode": "host", "PortBindings": { "8082/tcp": [ { "HostIp": "", "HostPort": "8082" } ] }, "RestartPolicy": { "Name": "no", "MaximumRetryCount": 0 }, "AutoRemove": false, "VolumeDriver": "", "VolumesFrom": null, "CapAdd": null, "CapDrop": null, "Dns": [], "DnsOptions": [], "DnsSearch": [], "ExtraHosts": null, "GroupAdd": null, "IpcMode": "shareable", "Cgroup": "", "Links": null, "OomScoreAdj": 0, "PidMode": "", "Privileged": false, "PublishAllPorts": false, "ReadonlyRootfs": false, "SecurityOpt": null, "UTSMode": "", "UsernsMode": "", "ShmSize": 67108864, "Runtime": "runc", "ConsoleSize": [ 0, 0 ], "Isolation": "", "CpuShares": 0, "Memory": 0, "NanoCpus": 0, "CgroupParent": "", "BlkioWeight": 0, "BlkioWeightDevice": [], "BlkioDeviceReadBps": null, "BlkioDeviceWriteBps": null, "BlkioDeviceReadIOps": null, "BlkioDeviceWriteIOps": null, "CpuPeriod": 0, "CpuQuota": 0, "CpuRealtimePeriod": 0, "CpuRealtimeRuntime": 0, "CpusetCpus": "", "CpusetMems": "", "Devices": [], "DeviceCgroupRules": null, "DiskQuota": 0, "KernelMemory": 0, "MemoryReservation": 0, "MemorySwap": 0, "MemorySwappiness": null, "OomKillDisable": false, "PidsLimit": 0, "Ulimits": null, "CpuCount": 0, "CpuPercent": 0, "IOMaximumIOps": 0, "IOMaximumBandwidth": 0, "MaskedPaths": [ "/proc/asound", "/proc/acpi", "/proc/kcore", "/proc/keys", "/proc/latency_stats", "/proc/timer_list", "/proc/timer_stats", "/proc/sched_debug", "/proc/scsi", "/sys/firmware" ], "ReadonlyPaths": [ "/proc/bus", "/proc/fs", "/proc/irq", "/proc/sys", "/proc/sysrq-trigger" ] }, "GraphDriver": { "Data": { "LowerDir": "/var/lib/docker/overlay2/7bfa4839ae827682ec4a810f51ab7ea955d070332d140572e8a1d8fdda321ad8-init/diff:/var/lib/docker/overlay2/4617aecbdd83a8e483c551504e474dd85b5dbc9bdd4a08e5df33ddf5a31eda67/diff:/var/lib/docker/overlay2/c26e5875934b34ec22c49c189cd14b8c1a799577c3ec594f0892f1e697d08a82/diff:/var/lib/docker/overlay2/3258ec4055d88ddcdcd308f6d1ae2e981d385a012d1498d8f016d1f24c381d06/diff:/var/lib/docker/overlay2/c9faf0a9f539ab20fd90a1848554474a6b20cdee2229b2e4f215a5cbf132fdd0/diff:/var/lib/docker/overlay2/1eadf72da200edf2834325ee9c60c04c1c0c02c991df91aa8aa10b70b924f929/diff:/var/lib/docker/overlay2/c6dc158b0338f9bc8643d94de6800ac25a3762243d415265e939cd6fb42e8316/diff:/var/lib/docker/overlay2/f8e26b65369476f25afadeb1702319cf8f8a97edd9d4cffdc0d91140234b80fe/diff:/var/lib/docker/overlay2/86e8bd8af6fabc538dae1cd1e57cc8dbaeff715e9b2aca89eb6df7f70902f9b5/diff:/var/lib/docker/overlay2/268932ed58164e68c489f6d479c2fc7f4c5512a7ac75c86a51b50cb7b78c29ef/diff:/var/lib/docker/overlay2/83fe7dd5d2bc817d32236a2dde8b33adfa57c2afe12cea8a8a96f22a53af43bf/diff:/var/lib/docker/overlay2/cc7a0863b05905502adf7001794ae107196f4bf425d957f33a632f37b291cb32/diff:/var/lib/docker/overlay2/ebfa8f74770dd1eb47579eee9ba1ed22d51b81c0098427f5825bdf41f69caf4f/diff:/var/lib/docker/overlay2/ecb87bd2a673dce9ee286db6331daddf4999341175337770e2858e342a52a29b/diff:/var/lib/docker/overlay2/d2a1a2391c1d8f10d989de56753bb31466738fbedae63039318b7a24300add4b/diff:/var/lib/docker/overlay2/ce96221513a265c980b938e3d70e8231d7ae5f12ad7bc26f9e1d33ea18fc35bd/diff:/var/lib/docker/overlay2/d42f3d4e735fe3377bd3b3686636980feed567738c222f8a9481315d9bc24e27/diff:/var/lib/docker/overlay2/e6cab56dcff9e586b04a66eccae8a703282bceb9c875fb315b40137d3023d30f/diff:/var/lib/docker/overlay2/bc371ed16050f5bc2856f7cd8012380bd3c269339fdcbecfc70ea77729188d11/diff:/var/lib/docker/overlay2/9e7dbda24293fc203def7517a2defe1c19930c59e48fef47be1c3a71591d5d61/diff:/var/lib/docker/overlay2/a6a542856ad33c77f6d05952b1595fa5343ef57b804c24f37f3d88096536b169/diff", "MergedDir": "/var/lib/docker/overlay2/7bfa4839ae827682ec4a810f51ab7ea955d070332d140572e8a1d8fdda321ad8/merged", "UpperDir": "/var/lib/docker/overlay2/7bfa4839ae827682ec4a810f51ab7ea955d070332d140572e8a1d8fdda321ad8/diff", "WorkDir": "/var/lib/docker/overlay2/7bfa4839ae827682ec4a810f51ab7ea955d070332d140572e8a1d8fdda321ad8/work" }, "Name": "overlay2" }, "Mounts": [ { "Type": "bind", "Source": "/etc/localtime", "Destination": "/etc/localtime", "Mode": "ro", "RW": false, "Propagation": "rprivate" }, { "Type": "bind", "Source": "/sharedfolders/appdata/UNMS", "Destination": "/config", "Mode": "rw", "RW": true, "Propagation": "rprivate" } ], "Config": { "Hostname": "Plexserver", "Domainname": "", "User": "", "AttachStdin": false, "AttachStdout": false, "AttachStderr": false, "ExposedPorts": { "2055/udp": {}, "443/tcp": {}, "80/tcp": {}, "8082/tcp": {} }, "Tty": false, "OpenStdin": false, "StdinOnce": false, "Env": [ "SSL_CERT=", "YARN_VERSION=1.12.3", "PATH=/home/app/unms/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/postgresql/9.6/bin", "DEBIAN_FRONTEND=noninteractive", "NGINX_VERSION=nginx-1.12.2", "NGINX_UID=1000", "LUAJIT_VERSION=2.1.0-beta3", "S6_KEEP_ENV=1", "PGID=100", "WS_PORT=443", "QUIET_MODE=0", "PUBLIC_WS_PORT=443", "UNMS_NETFLOW_PORT=2055", "PUID=1000", "QEMU_ARCH=x86_64", "PGDATA=/config/postgres", "NODE_VERSION=10.15.0", "POSTGRES_DB=unms", "LUA_NGINX_VERSION=0.10.13", "PUBLIC_HTTPS_PORT=443", "SECURE_LINK_SECRET=enigma" ], "Cmd": null, "ArgsEscaped": true, "Image": "oznu/unms:latest", "Volumes": { "/config": {} }, "WorkingDir": "/home/app/unms", "Entrypoint": [ "/init" ], "OnBuild": null, "Labels": { "omv_docker_extra_args": "-p 8082:8082" } }, "NetworkSettings": { "Bridge": "", "SandboxID": "e754de17a460d031b36bf13f5969e041ad2b9af528c4b8e1cb0706f67a179636", "HairpinMode": false, "LinkLocalIPv6Address": "", "LinkLocalIPv6PrefixLen": 0, "Ports": {}, "SandboxKey": "/var/run/docker/netns/default", "SecondaryIPAddresses": null, "SecondaryIPv6Addresses": null, "EndpointID": "", "Gateway": "", "GlobalIPv6Address": "", "GlobalIPv6PrefixLen": 0, "IPAddress": "", "IPPrefixLen": 0, "IPv6Gateway": "", "MacAddress": "", "Networks": { "host": { "IPAMConfig": null, "Links": null, "Aliases": null, "NetworkID": "250fcf67cdc993b4b3cc0956251c751a1b7435f1b50b79622348861fe6259a70", "EndpointID": "ff6ec9854a6c8f925d08c440e7c04c6ec369425c7750ad966bfe60cf3495e052", "Gateway": "", "IPAddress": "", "IPPrefixLen": 0, "IPv6Gateway": "", "GlobalIPv6Address": "", "GlobalIPv6PrefixLen": 0, "MacAddress": "", "DriverOpts": null } } } } ]

I just install (Clean not a update) the latest release, but at boot, I get this error:

here are my logs

2019/07/18 01:52:09 [error] 370#370: *2382 no live upstreams while connecting to upstream, client: 172.16.0.11, server: , request: "GET // HTTP/1.1", upstream: "http://websocket//", host: "172.16.0.2" 2019/07/18 01:52:10 [error] 369#369: *2383 connect() failed (111: Connection refused) while connecting to upstream, client: 172.16.0.24, server: , request: "GET // HTTP/1.1", upstream: "http://127.0.0.1:8082//", host: "172.16.0.2" 2019/07/18 01:52:10 [error] 369#369: *2383 connect() failed (111: Connection refused) while connecting to upstream, client: 172.16.0.24, server: , request: "GET // HTTP/1.1", upstream: "http://127.0.0.1:8082//", host: "172.16.0.2" 2019/07/18 01:52:10 [error] 369#369: *2384 no live upstreams while connecting to upstream, client: 172.16.0.13, server: , request: "GET // HTTP/1.1", upstream: "http://websocket//", host: "172.16.0.2" 2019/07/18 01:52:10 [error] 371#371: *2385 no live upstreams while connecting to upstream, client: 172.16.0.19, server: , request: "GET // HTTP/1.1", upstream: "http://websocket//", host: "172.16.0.2" 2019/07/18 01:52:11 [error] 368#368: *2388 no live upstreams while connecting to upstream, client: 172.16.0.27, server: , request: "GET // HTTP/1.1", upstream: "http://websocket//", host: "172.16.0.2" 2019/07/18 01:52:11 [error] 371#371: *2389 no live upstreams while connecting to upstream, client: 172.16.0.3, server: , request: "GET // HTTP/1.1"

UNMS is starting this should not take more than a minute
its 1 hr now
Am getting this error

I'm running your awesome image on a Synology Disk Station. So far, everything went beautiful. I'm just having difficulties to upgrade.

docker-compose pull oznu/unms:latest

yields a

Can't find a suitable configuration file in this directory or any
parent. Are you in the right directory?
Supported filenames: docker-compose.yml, docker-compose.yaml

error. I'm root and in /. Any idea what I've got to do to make it work?

Morning,

UNMS 0.13.3 exposes extra ports in the Docker config which aren't mentioned in https://github.com/oznu/docker-unms/wiki/UNMS-on-Synology-DSM

The WS_PORT environment must be left at 443 for UNMS to be able to communicate with devices.

Only PUBLIC_HTTPS and PUBLIC_WS environment variables should be updated to match the port assignments.

Hope this helps - took me ages to figure this out!

Thanks,
Jonathon

Any plans to support future releases for arm64? With the launch of the Raspberry Pi 4 having more RAM and lots of other sub $50 boards.

Or will the armhf version still work on most 64-bit implementations?

Hello,

Im having an issue with unms just giving me a generic failure when setting up the smtp feature in the UNMS contoller. Has anyone else had this issue?

Thanks,
Peppernip

There seem to be no openssl-* packages but only openssl1.0-* as reported by the build. I haven't investigated further but here is the error:

[unms]      ERROR: unsatisfiable constraints:
[unms]      
[unms]        openssl-dev (virtual):
[unms]          provided by: openssl1.0-dev
[unms]          required by: world[openssl-dev]

I'm running my image on an ASUS TinkerBoard. I'm running Pi-Hole and Unifi Controller on this same board which is why I chose a weird port.

Ports:
80/443 for lighttpd
8080/8443 for Unifi Controller
9080/9443 for UNMS

I do not believe I'm having an issue with firewalls/routing as I can get connection and view real-time information if I manually input the UNMS Key to the node.

Using this command to instantiate,

sudo docker run -d --name unms --restart unless-stopped -p 9443:443 -e PUBLIC_HTTPS_PORT=9443 -e PUBLIC_WS_PORT=9443 -v /etc/UNMS/config:/config oznu/unms:armhf

or this docker compose

version: '2' services: unms: image: oznu/unms:armhf restart: unless-stopped ports: - 9080:80 - 9443:443 volumes: - /etc/UNMS/config:/config environment: - TZ=America/Phoenix - PUBLIC_HTTPS_PORT=9443 - PUBLIC_WS_PORT=9443

Both methods of creating the image lead me to this same problem. Discovery Manager appears to be unable to find any host/node although I can manually add keys and communicate that way. Firmware Manager fails EVERY update to any node (Error: Device Upgrade has failed). When connecting to a device that I attempted to update the device says that something was uploaded but the image was blank (Firmware image check failed). So communication is happening but something is seriously borked.

Posting on your thread at https://community.ubnt.com/t5/UNMS-Beta/UNMS-in-Raspberry-Pi-3/m-p/2275583#M4959 yielded me another person who has the same issue.

Edit: Forgot to mention OS on the tinkerboard... Armbian 5.38 stable (Ubuntu 16.04.4 LTS 4.14.14-rockchip)

I installed UNMS container on a PI ZERO (ARMV6) . Installation was smooth. No errors of any kind. However when I tried to connect through a browser I got nothing. Both on HTTP and also HTTPS.
Connecting with curl I got Connection reset by peer. Is this image suppose to work on ARMV6 ?

Not sure why, but I haven't been able to connect my Edgerouter ER-X to UNMS. I am running this container on docker on Synology NAS.

ER-X is on latest firmware 1.10.5, private lan side IP = 192.168.1.1
Docker host IP = 192.168.1.200
UNMS latest, 0.12.2 beta
Running in bridged mode with ports remapped.

I can: login to UNMS from lan connected PC, inside UNMS I can discover my ER-X, it successfully logs in to the router and adds the wss connection string to ER-X. The ER-X does not connect back so in UNMS it times out and displays: "Connection attempt has failed". I have followed https://help.ubnt.com/hc/en-us/articles/115015690147-UNMS-Device-Discovery and it seems both devices can see each other.

Hi,

Since 0.13.0 (where it worked fine) Lets encrypt certificates no longer works on this build (as of 0.13.1).
Error message is: "Error: Let's Encrypt can only be used for fully qualified domain names. Please check setting/UNMS and the nginx*.log file for error messages. "

My domain name is FQDN. It works for other docker packages.

Port forwarding is working correctly and I can connect to port 80 from the internet.
UNMS developers stated that there was a script fix in release 0.13.3 that you could leverage on, that could fix the problem.

Hi,

I was trying to get UNMS behind the Synology reverse proxy so the Synology can handle the ssl certificate. This did not work out of the box with the config page on the Synology.
I have more services running through this and reusing the certificate for that was preferred.
You'll need a domain name you own to do this.
I use different hostnames for different services.

I installed the Docker container as described on the wiki. (https://github.com/oznu/docker-unms/wiki/UNMS-on-Synology-DSM) But i left the environment values on 443 not 8443. Since the UNMS will be on port 443 for clients connecting on the external hostname.

Make sure you request a certificate from Lets Encrypt on the Synology and mark it as the default certificate.
Use the Subject Alternate Names field to add additional host names to you certificate.
All host names in the certificate need top point to the Synology for validation.
I use a php file in webstation to redirect from http to https

Instead of configuring the reverse proxy in the control panel of the Synology you'll have to open the console of the Synology.

Log in with an admin user on ssh console and switch to root user (sudo su -)
Go to folder /usr/local/etc/nginx/sites-enabled/
Create a file there eg unms.conf
Config is:

map $http_upgrade $connection_upgrade {
  default upgrade;
  ''      close;
}


server {
        listen 443 ssl http2;
        server_name <hostname eg unms.example.com>;

        ssl_certificate     /usr/syno/etc/certificate/system/default/fullchain.pem;
        ssl_certificate_key /usr/syno/etc/certificate/system/default/privkey.pem;

        ssl on;

        set $upstream <synology ip>:8443;

        location / {
                proxy_pass     https://$upstream;
                proxy_redirect https://$upstream https://$server_name;

                proxy_cache off;
                proxy_store off;
                proxy_buffering off;
                proxy_http_version 1.1;
                proxy_read_timeout 36000s;

                proxy_set_header Host $http_host;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection $connection_upgrade;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header Referer "";

                client_max_body_size 0;
        }
}

Restart nginx on the Synology (not in the docker container) (synoservice --restart nginx)
The file will survive a reboot of the Synology. If it will survive a DSM upgrade i don't know.
To be safe save a copy of unms.conf on /volume1

Please test and reply if things are not clear.

@oznu
I am testing unms:armhf and everyday at 5:00 I have in logs this kind of message

UNMS works well, Is it important for me?
thank you Majo

According to Managing the SSL certificate for access via HTTPS, you can use a few parameters when using your own certificate.

Is it possible to add these as parameters for the docker container? Or maybe something similar to easily manage the certificate?

I am running this on a DSM Following your steps on setup, It was working, The only thing I have changed recently is my DHCP range and set my DSM to a Link aggregation setup. All my other packages are still working(unifi). It now seems to stuck on Exporting , telling me when I try to login that its starting up , but never does.


I checked the logs and its says this "[error] 463#463: *43 connect() failed (111: Connection refused) while connecting to upstream, client: 172.17.0.1, server: , request: "GET // HTTP/1.1", upstream: "http://127.0.0.1:8082// ... "My server"" Not sure what the means.
Any help with this issue would be greatly appreciated.

I would like to update UNMS through command line. But whenever I try to update I get message "unms_unms_1 is up-to-date". But it is not because web interface still shows old version. Is there any solution to update UNMS?

Hi, one quick change to the "Updating UNMS" section of the Wiki for Synology DSM. I'm running DSM 6.2. Prior to starting the new container, I had to change the old container's local port to something other than 8443, then point the new container's local port (which it had auto set) to 8443.

Hey guys,

i installed like in the description but the load is incredebelly high direct aber starting the container ...

%Cpu(s): 1,6 us, 0,6 sy, 0,0 ni, 30,0 id, 67,7 wa, 0,0 hi, 0,1 si, 0,0 st

14:30:55 up 7:43, 1 user, load average: 2,18, 1,59, 1,51

... dont know why ... bot postgres seems to write on disc all the time. Nothing is configured so far ...
but this is seen in iotop:
19301 be/4 systemd- 0.00 B/s 6.50 K/s 0.00 % 99.99 % postgres: postgres unms 127.0.0.1(33310) SELECT

Snot

I created a Docker Compose App on a QNAP NAS in Container Station.

Here is my yml file:

version: '3'
services:
unms:
image: oznu/unms:latest
restart: always
ports:

• 3080:80
• 3443:443
• 2055:2055/udp
  environment:
• TZ=America/New_York
  volumes:
• /DataVol1/Container/container-station-data/application/config:/config

When I start the app, I can login https with 3443 but all I see is a splash screen with UNMS is starting/this will only take a minute.....which never happens.

under the terminal I see the following errors---see attached screenshot.

Any help/advice would be appreciated. Thanks!

Hi, is it just me or is there something not forwarded correctly on port 80?
I have tried on my computer and my server to run the image and none of them accesses the exposed port.

When I try the HTTPS port I get an error 400 Bad Request The plain HTTP request was sent to HTTPS port
Is this the intended behaviour, because if I use 8081 it works like a charm 🙂

Hello,

I installed it as described on your wiki page for Synology DSM6, but when i do that i keep getting this when starting the docker:

nc: bad address 'unms-postgres' | stdout

I've set HTTP and WS port to 7443. Any idea?

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: npm run backup:apply && npm run migrate && node --max_old_space_size=2048 index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

The updated image wont build a working container ...

Looking through your files, I do not see how/if unms-fluentd is used?

does it support aarch64?
my rpi runs aarch64 variant OS.

@oznu
There is unable to DOWNLOAD BACKUP and DOWNLOAD SUPPORT INFO.

Is this only my issue or is it issue in general?

Majo

Hi,

I've got a problem running 0.13.2 and got issue with postgres:

s6-setuidgid postgres postgres                                                                                              
s6-applyuidgid: fatal: unable to exec postgres: No such file or directory

I could make it running with a dirty hack:

ln -s /usr/lib/postgresql/9.6/bin/postgres /usr/bin/

But it would be better to fix it properly by adding the bin path in the PATH.

Thanks

Created the container, set the config dir to an empty dir, and on startup I get

Starting postgres...
/var/run/postgresql:5432 - no response
Waiting for postgres to come up...
FATAL:  data directory "/config/postgres" has wrong ownership
HINT:  The server must be started by the user that owns the data directory.

files do get created.

On Docker for windows 2.0.0.0-win81 on Server 2016 w/ kitematic

Not sure if this is an issue or not. This is what I use to start oznu/docker-unms:

docker run -p 80:80 -p 443:443 -e TZ=America/Pacific -e PUID=$uUID -e PGID=$uGID
-v $PWD/config:/config:Z --name unms oznu/unms:latest

where
uUID=$(id -u)
uGID=$(id -g)

when I look in the config directory I see:
[bgsmith@pico config]$ ll
total 16
drwxr-xr-x. 5 nobody nobody 4096 Mar 23 09:38 logs
drwx------. 19 avahi avahi 4096 Mar 23 09:38 postgres
drwxr-xr-x. 2 bgsmith bgsmith 4096 Mar 23 09:38 redis
drwxr-xr-x. 10 bgsmith bgsmith 4096 Mar 23 09:38 unms

Should logs be set to user nobody and postgres to avahi?

thanks

brad

Hi !
Great work on this ! It is working perfectly on my infrastructure.
Do you know if it is possible to trigger a build for the 0.13.3 version of unms and push it to docker hub ?

Thanks !

Hey, I could use some help with reverse proxy and unms if you have the chance.

I have set it up behind a nginx proxy and connecting fine on the unms webpage.
But I am having some troubles connecting my edgemax devices to unms behind the reverse proxy.

Could you be so kind to share your nginx site config, your port forwards on the router and your docker run command to help me out?