Unmanic wont connect after todays upgrade

AngusMcKinnon commented 3 months ago

Using Unraid 6.12.13

Upgraded to latest version of Unmanic (today - Aug 29 release). Has been previously working well for 3 months or more.

Looks like it is started okay (eg green arrow in unraid), but when I try and open the GUI for Unmanic I get

This site can’t be reached 192.168.0.143 refused to connect.

When I look in logs I see:

s6-supervise unmanic: warning: unable to spawn ./run (waiting 60 seconds): Permission denied /package/admin/s6-overlay-3.1.6.2/etc/s6-rc/scripts/cont-init: 20: /etc/cont-init.d/20-config: Permission denied /package/admin/s6-overlay-3.1.6.2/etc/s6-rc/scripts/cont-init: 20: /etc/cont-init.d/30-patch-nvidia: Permission denied /package/admin/s6-overlay-3.1.6.2/etc/s6-rc/scripts/cont-init: 20: /etc/cont-init.d/60-custom-setup-script: Permission denied s6-supervise unmanic: warning: unable to spawn ./run (waiting 60 seconds): Permission denied s6-supervise unmanic: warning: unable to spawn ./run (waiting 60 seconds): Permission denied s6-supervise unmanic: warning: unable to spawn ./run (waiting 60 seconds): Permission denied

Is this a problem at my end the upgrade has uncovered? or is it something with the upgrade that isnt right?

Ive googled and couldnt see any similar issues.

Zulcon commented 3 months ago

I rolled back to 0.2.7 in Docker and everything is working as normal for me, not sure what that link above is supposed to accomplish.

AngusMcKinnon commented 3 months ago

I rolled back to 0.2.7 in Docker and everything is working as normal for me, not sure what that link above is supposed to accomplish.

Can I confirm you had same issue? If so, good news, means I dont have to fix anything my end.

I assume link above was spam or virus. Seemed to be pasted as soon as I hit the comment button so I ignored it.

IOwnCalculus commented 3 months ago

I just encountered the same issue, and rolled it back to 0.2.7 with success as well. Definitely something went wrong with the 0.2.8 update.

iloveteaandcoffee commented 2 months ago

Same as being reported. No longer starts on the latest version

shanelord01 commented 2 months ago

Same issue. Edited unmanic in unraid, changed "Repository" to "josh5/unmanic:0.2.7" and rollback complete. Now working again.

iloveteaandcoffee commented 2 months ago

Same issue. Edited unmanic in unraid, changed "Repository" to "josh5/unmanic:0.2.7" and rollback complete. Now working again.

Replace the below in the repository and it will roll back to the previous version once you've clicked apply

josh5/unmanic:0.2.7

maxvaneck commented 2 months ago

same here. something definitely went wrong somewhere

Josh5 commented 2 months ago

Should now be resolved

AngusMcKinnon commented 2 months ago

Should now be resolved

Thanks @Josh5 You have an awesome product. Very much appreciated.

shanelord01 commented 2 months ago

Sorry to comment on a closed thread, but I reverted to the latest branch from forced 0.2.7, and the issue still exists for me.

UPDATE: Chose "Force Update" in unraid and this seems to have resolved it.

lfilho commented 6 days ago

I just pulled the latest image from today (2024-11-20) and i can't connect as well.

Using docker 20.10.23 on a Synology D220+ box (not the built-in container manager but docker CLI via SSH).

Docker compose:

  unmanic:
    container_name: unmanic
    image: josh5/unmanic:latest
    restart: unless-stopped
    network_mode: host
    security_opt:
      - no-new-privileges:true
    logging:
      driver: json-file
    ports:
      - 8889:8889
    environment:
      - PUID=$PUID
      - PGID=$PGID
      - UMASK=$UMASK
      - TZ=$TZ
    volumes:
      - $VOLUME_PREFIX/docker/unmanic:/config
      - $VOLUME_PREFIX/data/media:/library
      - $VOLUME_PREFIX/docker/tmp:/tmp/unmanic
    devices:
      - /dev/dri:/dev/dri

Container log:

  unmanic:
    container_name: unmanic
    image: josh5/unmanic:latest
    restart: unless-stopped
    network_mode: host
    security_opt:
      - no-new-privileges:true
    logging:
      driver: json-file
    ports:
      - 8889:8889
    environment:
      - PUID=$PUID
      - PGID=$PGID
      - UMASK=$UMASK
      - TZ=$TZ
    volumes:
      - $VOLUME_PREFIX/docker/unmanic:/config
      - $VOLUME_PREFIX/data/media:/library
      - $VOLUME_PREFIX/docker/tmp:/tmp/unmanic
    devices:
      - /dev/dri:/dev/dri [migrations] started
[migrations] no migrations found
**** (permissions_config) Setting run user uid=100(abc) gid=1027(abc)  ****
**** (permissions_config) Setting permissions ****
**** (permissions_config) Adding run user to video group ****
───────────────────────────────────────
  _____ __ __ _____ _____ _____ _____
 |     |  |  |   __|_   _|     |     |
 |   --|  |  |__   | | | |  |  | | | |
 |_____|_____|_____| |_| |_____|_|_|_|
       _____ __ __ _ __    ____
      | __  |  |  | |  |  |    \
      | __ -|  |  | |  |__|  |  |
      |_____|_____|_|_____|____/

  Based on images from linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1027
User GID:    100
───────────────────────────────────────

[custom-init] No custom files found, skipping...
[ls.io-init] done.
2024-11-20T13:58:35:INFO:Unmanic.UnmanicLogger - Initialising file logger. All further logs should output to the 'unmanic.log' file

lfilho commented 6 days ago

I think I found the problem: even though i was changing the port in the my configuration file, looks like unmanic wasn't respecting and it was still trying to use 8888 and failing, since another container was already using that one. I changed the other container's port to something and reverted unmanic back to 8888 and it worked. It would be nice to have the port passed via docker-compose.yml to be respected 😊

Thank you for your work, @Josh5

Unmanic / unmanic

Unmanic wont connect after todays upgrade #498