VNC Failing to Start

[Davo1624]

Using the :latest image I am running into a problem with VNC starting

Error message in my web browser is:

https://soulseek.mydomain.tld/app/webutil.js:9:9

Below is my compose:

    soulseek:
    container_name: soulseek
    depends_on:
      - qbittorrent
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
    image: realies/soulseek:latest
    network_mode: service:qbittorrent
    restart: unless-stopped
    volumes:
      - ${CONF_PATH}/soulseek:/data/.SoulseekQt
      - ${CONF_PATH}/soulseek/logs:/data/Soulseek Chat Logs
      - ${DATA_PATH}/soulseek:/data/Soulseek Downloads
      - ${MEDIA_PATH}:/data/Soulseek Shared Folder

Below is the output of docker logs soulseek:

2022-03-08 13:53:14,188 INFO Set uid to user 99 succeeded
2022-03-08 13:53:14,190 INFO supervisord started with pid 30
2022-03-08 13:53:15,192 INFO spawned: 'tigervnc' with pid 32
2022-03-08 13:53:15,193 INFO spawned: 'openbox' with pid 33
2022-03-08 13:53:15,194 INFO spawned: 'novnc' with pid 34
2022-03-08 13:53:15,195 INFO spawned: 'soulseek' with pid 35
2022-03-08 13:53:16,250 INFO success: tigervnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-08 13:53:16,250 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-08 13:53:16,250 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-08 13:53:16,250 INFO success: soulseek entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

I am routing soulseek through a vpn container but this was not an issue with the previous image. There is no log file being generated in the soulseek log folder either.

Besides updating the image and adjusting the env vars for PUID, PGID and TZ nothing else has changed on my end.

[realies]

@Davo1624, any chance of browser cache?

[Davo1624]

Ugh that was it, I will go stand in the corner now :)

But while I have your attention, when I try to change the default listening ports they just revert back to the original settings:

Any ideas?

Edit - larger issue is appdata does not seem to be saving so each time the container is restarted my persistent data is erased. Appdata is mapped to /mnt/user/appdata/soulseek:/data/.SoulseekQt and the appdata/soulseek folder is empty. Folder permissions are uid 99 and gid 100 which matches the uid and gid specified in the compose.

For some odd reason the log folder is generated but nothing is being saved

[realies]

@Davo1624, glad it worked. Most likely Soulseek hasn't saved its appdata before you restart it. Check the closed issues on this.

[Davo1624]

Appreciate the patience and the assistance, amazing the things you forget after you last set something up months ago.

All appears to be working now :)