Unable to access WebUI over 8443 #151
Comments
|
I updated through unraid apps this morning and I am also having this issue. I tried changing to running it as privileged and also switched it over to running as a host. I also noticed that it is still using port 8080 even though I set it to use 8081 in the container settings page. I am going to try installing it from scratch this evening to see if it resolves the issue. |
|
The webui does take time to come online (as discussed in other issues here) - also moving it to host networking will ignore any port mappings. |
|
Also having this issue since updating. Set up has been previously working without problem for 2y+. Running in host mode. No access over :8443 |
|
@reubn you need to provide some context of your setup. You also need to check logs of unifi itself as it could be crashing. |
|
Of course. I'm away atm, so I'll add the details when I'm able to access them. UniFi docker container was active, no obvious details in the logs from memory. Updated to latest published version this morning and immediately lost access to UniFi instance. |
|
My root issue was that my entire filesystem had been converted to read-only because one of my cache drives on UnRaid was in an error state. It was in this state before I updated, but the latest version of UnRaid must have this feature enabled by default. I spent a bunch of time going in circles before I figured it out. I shut down the array and unmounted the bad cache drive and it works now. I'm not sure what repercussions unmounting the 2nd cache drive could cause and I have no idea what I'm doing, so make sure you back up anything important and look for an expert's advice before you attempt it, if you find a cache drive in an error state. LOL Hopefully this helps someone else. |
|
Same here. I had to go back to 6.5.55-ls142 to get access back. |
|
Hello! Today I did update my container and it stopped opening on 8443. cont-init: info: /etc/cont-init.d/19-armless exited 0 cont-init: info: running /etc/cont-init.d/20-config cont-init: info: /etc/cont-init.d/20-config exited 0 cont-init: info: running /etc/cont-init.d/30-keygen cont-init: info: /etc/cont-init.d/30-keygen exited 0 cont-init: info: running /etc/cont-init.d/90-custom-folders cont-init: info: /etc/cont-init.d/90-custom-folders exited 0 cont-init: info: running /etc/cont-init.d/99-custom-scripts [custom-init] no custom files found exiting... cont-init: info: /etc/cont-init.d/99-custom-scripts exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun unifi (no readiness notification) s6-rc: info: service legacy-services successfully started s6-rc: info: service 99-ci-service-check: starting [ls.io-init] done. s6-rc: info: service 99-ci-service-check successfully started Can anyone help? |
|
@Vodalex you need to role back to the tag that's mentioned in this post: https://info.linuxserver.io/issues/2022-05-31-unifi-controller/ . Please note that it will no longer receive updates and it is recommended to upgrade to a 64bit OS. |
Thanks for the answer. Can you please tell me how to recreate the container with this tag in the docker? |
|
@Vodalex all depends how you've deployed the container but generally you add the tag onto the end of the image name |
|
You saved my old NAS. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Not stale |
Just use the Image 7.1.68. 32 Bit support was dropped after this version. |
Hi there! Sorry, I'm not sure what you mean? I have this issue on a 64-bit system. |
|
@denizdogan please open a new ticket as this issue is related to a 32bit system. |
|
@j0nnymoe With respect, because maybe I'm misunderstanding, the issue was originally about a macOS system, and several others using UnRAID. As far as I can tell, only one user has been discussing 32-bit systems. |
|
Sure but please open a new issue and provide the information requested in the template. |
|
Based on this you either have init: true in your docker-compose file, or however you are managing the container, or you need to upgrade libseccomp2 or if you can't upgrade libseccomp2 then you need to add the following: security_opt: |
Expected Behavior
Should be able to load web portal on https://ip:8443
Current Behavior
Unable to load the URL on this port, can load on 8080 but get errors when trying to sign in.
Steps to Reproduce
Load https://ip:8443
Environment
**OS: macOS 11.2.3 - Docker installed, Portainer Installed
How docker service was installed:
Installed through brew also have docker desktop
Command used to create docker container (run/create/compose/screenshot)
Steps followed from https://hub.docker.com/r/linuxserver/unifi-controller under docker-control
--- version: "2.1" services: unifi-controller: image: lscr.io/linuxserver/unifi-controller:latest container_name: unifi-controller environment: - PUID=1000 - PGID=1000 - MEM_LIMIT=1024 #optional - MEM_STARTUP=1024 #optional volumes: - <path to data>:/config ports: - 8443:8443 - 3478:3478/udp - 10001:10001/udp - 8080:8080 - 1900:1900/udp #optional - 8843:8843 #optional - 8880:8880 #optional - 6789:6789 #optional - 5514:5514/udp #optional restart: unless-stoppedAlso followed these exact steps in portainer https://www.youtube.com/watch?v=owT2G7ribNE
Docker logs
` || |/ || _/
Brought to you by linuxserver.io
To support LSIO projects visit:
https://www.linuxserver.io/donate/
GID/UID
User uid: 1000
User gid: 1000
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 15-install: executing...
*** installing unifi packages ***
Selecting previously unselected package unifi.
(Reading database ... 8892 files and directories currently installed.)
Preparing to unpack /app/unifi.deb ...
Unpacking unifi (7.1.66-17875-1) ...
Setting up unifi (7.1.66-17875-1) ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
[cont-init.d] 15-install: exited 0.
[cont-init.d] 19-armless: executing...
[cont-init.d] 19-armless: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: destroy called
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 01-migrations: executing...
[migrations] started
[migrations] no migrations found
[cont-init.d] 01-migrations: exited 0.
[cont-init.d] 02-tamper-check: executing...
[cont-init.d] 02-tamper-check: exited 0.
[cont-init.d] 10-adduser: executing...
usermod: no changes
Brought to you by linuxserver.io
To support LSIO projects visit:
https://www.linuxserver.io/donate/
GID/UID
User uid: 1000
User gid: 1000
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 15-install: executing...
[cont-init.d] 15-install: exited 0.
[cont-init.d] 19-armless: executing...
[cont-init.d] 19-armless: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.`
The text was updated successfully, but these errors were encountered: