cant access crm page about docker-unms HOT 16 OPEN

Hi, can you give some more details about the issue? Like what error is shown when you try to open the CRM page? What device / architecture / linux kernel version / docker version are you using to run the container? Can you take a look into the ucrm.log file (your UNMS directory/unms/logs/ucrm.log) and see if there is any obvious error or repeating pattern? If so, please paste the last part of the log here.

from docker-unms.

Same issue. It gives a 404 "Lost in space" page. I scoured through all 25 config files and it seems that /crm might have in the past been proxy_passed to port 9081 as all the UCRM stuff seems to live in /etc/nginx/ucrm/ucrm.conf... where it looks like it should be redirected from snippets/ucrm-locations.conf but it references a $ucrm_upstream variable which I can't find where it's defined... I guess I can check the startup scripts. Opening port 9081 directly doesn't work as it redirects to :443/ucrm which shows the 404.

from docker-unms.

This was of course an upgrade

from docker-unms.

Can't find any errors or anything that stands out in any logs... will diff the configs with an older version if I can't find anything in the startup scripts.

from docker-unms.

Does the same on a clean install on x86.

Also need to do this to get it up:

chmod 600 /usr/lib/sudo/sudoers.so
chmod 600 /etc/sudo.conf
chmod 600 /etc/sudoers

from docker-unms.

That was all on 1.3.11.
Same on 1.3.9

from docker-unms.

I started 1.3.9 with 1.3.11's config. With a clean config, I get this in a loop. Until I log in and fix it...

sudo: /etc/sudo.conf is world writable
sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy"
sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner
sudo: fatal error, unable to load plugins
nginx: [emerg] open() "/etc/nginx/ip-whitelist.conf" failed (2: No such file or directory) in /etc/nginx/conf.d/unms-https+wss.conf:36

from docker-unms.

1.3.9 gives 404 for /crm and 403 forbidden for /nms

from docker-unms.

On restart 403 goes away and nms works but crm still 404

from docker-unms.

Went back to 1.2.7... no problems. Now working my way up...

from docker-unms.

This problem starts with 1.3.7. Although... it did work on one of the 1.3 lines...

from docker-unms.

@dagelf Which OS, Kernel and Docker version are you using? Is there anything else noteworthy about your setup? I'll try to reproduce this.

This does indeed sound like an issue with the nginx configuration, which is set up by the /refresh-configuration.sh script. Try executing it and see if you still get that 404 or if it outputs any errors.

from docker-unms.

I just tried it on another machine, where it works! So this ... surprise... Docker choking up. Docker is almost 10 years old and it still can't do its job properly. 🤦

Also I wish UBNT CEO would wake up to how the software world works. Vanilla UISP installation has been unstable - crashed docker on all the machines I've tried it on over the last year, which is how I ended up with your excellent package - which hasn't given any problems until now.

Anyways, thanks for maintaining this, I'm going to be monitoring it so I can help out.

For interest sake:

Problem machine: Ubuntu 18.04.5 LTS

Server: Docker Engine - Community
 Engine:
  Version:          20.10.6
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       8728dd2
  Built:            Fri Apr  9 22:44:13 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.4
  GitCommit:        05f951a3781f4f2c1911b05e61c160e9c30eaa8e
 runc:
  Version:          1.0.0-rc93
  GitCommit:        12644e614e25b05da6fd08a38ffa0cfe1903fdec
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Busy updating it so I can't run docker info now...
...after update, will test again shortly

docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.6.1-docker)
  scan: Docker Scan (Docker Inc., v0.8.0)

Server:
 Server Version: 20.10.8
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runtime.v1.linux runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: e25210fe30a0a703442421b0f60afac609f950a3
 runc version: v1.0.1-0-g4144b63
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 4.xxx-generic
 Operating System: Ubuntu 18.04.5 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 32
 Total Memory: 31.4GiB
 Name: s3
 ID: xxx
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No swap limit support

Working machine: Ubuntu 18.04.5 LTS

Server: Docker Engine - Community
 Engine:
  Version:          19.03.12
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       48a66213fe
  Built:            Mon Jun 22 15:44:07 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683


Client:
 Debug Mode: false

Server:
 Server Version: 19.03.12
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
 init version: fec3683
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 5.xxx-generic
 Operating System: Ubuntu 18.04.5 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.53GiB
 Name: xxx
 ID: xxx
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 71
  Goroutines: 71
  System Time: 2021-08-15T19:36:35.300571361+02:00
  EventsListeners: 0
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No swap limit support

from docker-unms.

☝️ Just updating docker fixed it. 😕

Close this!

I'll carry on digging into how UISP fits together to see if I can come up with a way to get more useful error messages than just a 404.

from docker-unms.

@dagelf i've update the docker
but same error

from docker-unms.

from docker-unms.