Change-detection: Stuck on deploying, but app runs

MarkHoltz · May 12, 2025, 12:45pm

I installed the change-detection app yesterday, and it seems to work great. I’m currently on the App Version: v0.46.16 / Version: v1.0.0 . The only problem is that the app is stuck on “Deploying”, but the app is accessible, and I’ve even set up a reverse proxy for remote access along with a long password. Any ideas on which values to check?

neofusion · May 12, 2025, 4:49pm

What does sudo docker ps show?
Specifically the STATUS column for the app in question.

MarkHoltz · May 12, 2025, 5:19pm

“Up 5 minutes (unhealthy)”. I just downloaded App Version: v0.49.17 / Version: v1.0.1 just now too.

CONTAINER ID   IMAGE                                                 COMMAND                  CREATED         STATUS                     PORTS                                                                                                                               NAMES
4543f238b218   ghcr.io/dgtlmoon/changedetection.io:0.49.17           "python ./changedete…"   5 minutes ago   Up 5 minutes (unhealthy)   5000/tcp, 192.168.1.2:30159->30159/tcp                                                                                              ix-change-detection-change-detection-1

I have a feeling that TrueNAS is attempting to verify using https and this is a http application.

neofusion · May 12, 2025, 5:37pm

Looking at what I understand to be the code regulating this, it doesn’t look like that is the case:

github.com/truenas/apps

ix-dev/community/change-detection/templates/docker-compose.yaml

f20a6518e


      
          {% set tpl = ix_lib.base.render.Render(values) %}
          
          {% set c1 = tpl.add_container(values.consts.change_detection_container_name, "image") %}
          {% set perm_container = tpl.deps.perms(values.consts.perms_container_name) %}
          {% set perms_config = {"uid": values.run_as.user, "gid": values.run_as.group, "mode": "check"} %}
          
          {% do c1.set_user(values.run_as.user, values.run_as.group) %}
          {% do c1.healthcheck.set_test("http", {"port": values.network.web_port.port_number}) %}
          
          {% do c1.environment.add_env("PORT", values.network.web_port.port_number) %}
          {% do c1.environment.add_user_envs(values.change_detection.additional_envs) %}
          
          {% do c1.add_port(values.network.web_port) %}
          
          {% do c1.add_storage("/datastore", values.storage.datastore) %}
          {% do perm_container.add_or_skip_action("datastore", values.storage.datastore, perms_config) %}
          
          {% for store in values.storage.additional_storage %}

Still, something about that healthcheck is apparently not working as it should…

neofusion · May 12, 2025, 5:45pm

What is port 30159 for?
5000 is mentioned on the official github but 30159 is not.
When you say you can visit the page, are you visiting it on #.#.#.#:5000 or #.#.#.#:30159?

MarkHoltz · May 12, 2025, 6:02pm

Port 30159 was part of the TrueNAS Apps configuration. And I agree that the TrueNAS health detection isn’t working as expected as the app works as expected.