Umbrel 1.0 - Jam app does not open

I’ve installed the Jam app on my new Rpi 5 running Umbrel 1.0 (clean install) but notice that the app does not start. Port :5002 seems to be right as it is similar to my Umbrel 0.5.4 installation on my old Rpi 4. What is the problem here? Btw: I have already uninstalled and reinstalled the Jam app and rebooted my node too. Also my other installed apps (e.g. electrs, mempool…) open up well.

Anybody an idea? Anybody experiencing the same? Maybe somebody with a RPi 5 can install the Jam app and try to open?

1 Like

Hi @Achim sorry to see your issue here, can you please try restarting the Jam app by right clicking it and then pressing restart. After that, can you please navigate to the settings dashboard on umbrel.local, select START under troubleshooting and share the resultant logs here.

Hi @smolgrrr

here’s the log file

jam_app_proxy_1 | yarn run v1.22.19
jam_app_proxy_1 | $ node ./bin/www
jam_app_proxy_1 | [HPM] Proxy created: / → http://jam_web_1:80
jam_app_proxy_1 | Waiting for jam_web_1:80 to open…
jam_web_1 | [WARN tini (7)] Tini is not running as PID 1 and isn’t registered as a child subreaper.
jam_web_1 | Zombie processes will not be re-parented to Tini, so zombie reaping won’t work.
jam_web_1 | 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.
jam_web_1 | Remove leftover wallet lockfiles before startup…
jam_web_1 | Waiting for bitcoind to accept RPC requests…
jam_web_1 | Successfully waited for bitcoind to accept RPC requests.
jam_web_1 | Creating wallet jam_default if missing…
jam_web_1 | Loading wallet jam_default…
jam_web_1 | [ OK ] nginx
jam_web_1 | [ OK ] tor
jam_web_1 | [ OK ] jmwalletd
jam_web_1 | dinit: Service nginx process terminated with exit code 1
jam_web_1 | [STOPPD] nginx
jam_web_1 | [ OK ] ob-watcher
jam_web_1 | [ OK ] boot
jam_web_1 | [ OK ] nginx
jam_web_1 | dinit: Service nginx process terminated with exit code 1
jam_web_1 | [STOPPD] nginx
jam_web_1 | [ OK ] nginx
jam_web_1 | dinit: Service nginx process terminated with exit code 1
jam_web_1 | [STOPPD] nginx
jam_web_1 | [ OK ] nginx
jam_web_1 | dinit: Service nginx process terminated with exit code 1
jam_web_1 | dinit: Service nginx restarting too quickly; stopping.
jam_web_1 | [STOPPD] nginx

Hope that helps?

1 Like

I have now formatted my microSD card, flashed it new and also formatted my SSD.
Basically a clean new installation.

Still the same. Jam app does not open. All other apps (Bitcoin Node, Electrs, Mempool, Tailscale etc.) open up as expected.
Can’t be that I am the only one where it doesn’t work?

The must be some issue with Port :5002

Problem is still unsolved…

having the same issue. here are my logs. 1.0.4 rpi5. dont want to uninstall since i have two wallets in there but have restarted the app multiple times.

tor_server-1  | Mar 31 03:30:53.453 [notice] Tor 0.4.7.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.31 as libc.
tor_server-1  | Mar 31 03:30:53.453 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
tor_server-1  | Mar 31 03:30:53.453 [notice] Read configuration file "/tmp/torrc".
tor_server-1  | Mar 31 03:30:53.465 [notice] Opening Socks listener on 127.0.0.1:9050
tor_server-1  | Mar 31 03:30:53.465 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
tor_server-1  | Mar 31 03:30:53.000 [notice] Bootstrapped 0% (starting): Starting
tor_server-1  | Mar 31 03:30:53.000 [notice] Starting with guard context "default"
tor_server-1  | Mar 31 03:30:54.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
tor_server-1  | Mar 31 03:30:54.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
tor_server-1  | Mar 31 03:30:54.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
tor_server-1  | Mar 31 03:30:55.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
tor_server-1  | Mar 31 03:30:55.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
tor_server-1  | Mar 31 03:30:55.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
tor_server-1  | Mar 31 03:30:55.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
tor_server-1  | Mar 31 03:30:56.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
tor_server-1  | Mar 31 03:30:56.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
tor_server-1  | Mar 31 03:30:56.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
tor_server-1  | Mar 31 03:30:56.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
tor_server-1  | Mar 31 03:30:56.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7526, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
tor_server-1  | Mar 31 03:30:57.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
tor_server-1  | Mar 31 03:30:58.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
tor_server-1  | Mar 31 03:31:00.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
tor_server-1  | Mar 31 03:31:03.000 [notice] Bootstrapped 62% (loading_descriptors): Loading relay descriptors
tor_server-1  | Mar 31 03:31:03.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptors
tor_server-1  | Mar 31 03:31:03.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_server-1  | Mar 31 03:31:03.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_server-1  | Mar 31 03:31:03.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_server-1  | Mar 31 03:31:03.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_server-1  | Mar 31 03:31:04.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_server-1  | Mar 31 03:31:04.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_server-1  | Mar 31 03:31:04.000 [notice] Bootstrapped 100% (done): Done
jam_web_1     | [WARN  tini (6)] Tini is not running as PID 1 and isn't registered as a child subreaper.
jam_web_1        | Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
jam_web_1        | 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.
jam_web_1        | Remove leftover wallet lockfiles before startup...
jam_web_1        | Waiting for bitcoind to accept RPC requests...
jam_web_1        | Successfully waited for bitcoind to accept RPC requests.
jam_app_proxy_1  | yarn run v1.22.19
jam_app_proxy_1  | $ node ./bin/www
jam_app_proxy_1  | [HPM] Proxy created: /  -> http://jam_web_1:80
jam_app_proxy_1  | Waiting for jam_web_1:80 to open...
jam_web_1        | Creating wallet jam_default if missing...
jam_web_1        | Loading wallet jam_default...
jam_web_1        | [  OK  ] tor
jam_web_1        | [  OK  ] ob-watcher
jam_web_1        | [  OK  ] jmwalletd
jam_web_1        | [  OK  ] nginx
jam_web_1        | [  OK  ] boot
jam_web_1        | dinit: Service nginx process terminated with exit code 1
jam_web_1        | [STOPPD] nginx
jam_web_1        | [  OK  ] nginx
jam_web_1        | dinit: Service nginx process terminated with exit code 1
jam_web_1        | [STOPPD] nginx
jam_web_1        | [  OK  ] nginx
jam_web_1        | dinit: Service nginx process terminated with exit code 1
jam_web_1        | [STOPPD] nginx
jam_web_1        | [  OK  ] nginx
jam_web_1        | dinit: Service nginx process terminated with exit code 1
jam_web_1        | dinit: Service nginx restarting too quickly; stopping.
jam_web_1        | [STOPPD] nginx
1 Like

Problem still unsolved after upgrade to 1.0.4

2 Likes

Updated my RPi5 to umbrelOS 1.1 this AM (from 1.0.4) running Jam 0.2.0, still have no connection when trying to open Jamwallet. When i try telnet’ing on localhost to port 5002, it connects briefly and then drops:

Trying 127.0.0.1…
Connected to localhost.
Escape character is ‘^]’.
Connection closed by foreign host.

here’s the log from it: jamwallet won't start on umbrel 1.1 RPi5 - Pastebin.com

more info: $sudo nmap -n -PN -sT -sU -p5002 localhost yields:

PORT STATE SERVICE
5002/tcp open rfe
5002/udp closed rfe

so, radio free ethernet conflict?