# JAM - does it work for you? **URL:** \ **Category:** Support and Troubleshooting\ **Created:** [April 24, 2024, 11:38pm UTC](https://community.umbrel.com/t/jam-does-it-work-for-you/16586 "2024-04-24T23:38:50Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![hzrng](https://avatars.discourse-cdn.com/v4/letter/h/f6c823/32.png) [@hzrng](https://community.umbrel.com/u/hzrng)\ **Post date:** [April 25, 2024, 7:10pm UTC](https://community.umbrel.com/t/jam-does-it-work-for-you/16586/2 "2024-04-25T19:10:41Z")
I get the same error message. Others seem to have some conflicts with port 5002, see here: [Umbrel 1.0 - Jam app does not open](https://community.umbrel.com/t/umbrel-1-0-jam-app-does-not-open/15700) However, my issue seems to be not related to port 5002, so let’s provide more details: I run Umbrel 0.5.4 on a Windows PC with WSL2 Ubuntu and Docker Desktop. I had to tweak the default setup a little bit to get the Bitcoin, Electrs, and Mempool apps running: - due to some other app listening to port 80 on my Windows system, I start Umbrel with NGINX\_PORT=8080 - the authentication forwarding to port 2000 does not work, so I deactivated this for the apps individually, by setting PROXY\_AUTH\_ADD: “false” in the docker.compose.yml files. I tried this for JAM as well, but it did not help. Here is the log of my jam\_web\_1 container: ```auto 2024-04-25 21:01:44 Remove leftover wallet lockfiles before startup... 2024-04-25 21:01:44 Waiting for bitcoind to accept RPC requests... 2024-04-25 21:01:51 Successfully waited for bitcoind to accept RPC requests. 2024-04-25 21:01:51 Creating wallet jam_default if missing... 2024-04-25 21:01:51 Loading wallet jam_default... 2024-04-25 21:01:51 dinit: In multiple cgroups, cannot determine cgroup root path 2024-04-25 21:01:51 [OK] nginx 2024-04-25 21:01:51 [OK] tor 2024-04-25 21:01:51 [OK] ob-watcher 2024-04-25 21:01:51 [OK] jmwalletd 2024-04-25 21:01:51 [OK] boot 2024-04-25 21:01:52 dinit: Service jmwalletd process terminated with exit code 1 2024-04-25 21:01:52 dinit: Service ob-watcher process terminated with exit code 1 2024-04-25 21:01:52 dinit: Service jmwalletd process terminated with exit code 1 2024-04-25 21:01:52 dinit: Service ob-watcher process terminated with exit code 1 2024-04-25 21:01:52 dinit: Service ob-watcher process terminated with exit code 1 2024-04-25 21:01:52 dinit: Service jmwalletd process terminated with exit code 1 2024-04-25 21:01:53 dinit: Service jmwalletd process terminated with exit code 1 2024-04-25 21:01:53 dinit: Service jmwalletd restarting too quickly; stopping. 2024-04-25 21:01:44 [WARN tini (7)] Tini is not running as PID 1 and isn't registered as a child subreaper. 2024-04-25 21:01:44 Zombie processes will not be re-parented to Tini, so zombie reaping won't work. 2024-04-25 21:01:44 To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1. 2024-04-25 21:01:53 dinit: Service jmwalletd restarting too quickly; stopping. 2024-04-25 21:01:53 [STOPPD] jmwalletd 2024-04-25 21:01:53 dinit: Service ob-watcher process terminated with exit code 1 2024-04-25 21:01:53 dinit: Service ob-watcher restarting too quickly; stopping. 2024-04-25 21:01:53 dinit: Service ob-watcher restarting too quickly; stopping. 2024-04-25 21:01:53 [STOPPD] ob-watcher ``` jmwalletd and ob-watcher seem to have a problem, but I don’t know how to proceed from here. Any ideas would be appreciated. --- _[View the full topic](https://community.umbrel.com/t/jam-does-it-work-for-you/16586)._