Umbrel 1.0 - Jam app does not open

Achim · March 20, 2024, 11:17pm

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.

Achim · March 21, 2024, 4:33pm

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

smolgrrr · March 22, 2024, 5:28am

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.

Achim · March 22, 2024, 8:06am

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?

Achim · March 22, 2024, 12:43pm

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

Achim · March 24, 2024, 8:36am

Problem is still unsolved…

boroghor · March 31, 2024, 3:35am

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

Achim · April 4, 2024, 2:07am

Problem still unsolved after upgrade to 1.0.4

jz831 · April 17, 2024, 7:50pm

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?

jz831 · April 27, 2024, 5:35pm

is there an easy way to get Jam to run on another port?

Achim · April 30, 2024, 6:30am

Problem is still unsolved.

Scottydog144 · May 2, 2024, 2:04am

I’m having the same exact issue. Any guidance?

nmfretz · May 2, 2024, 3:10am

@Scottydog144 @Achim @jz831 - a Bitcoin Node app update was just released that should fix this issue for you (more info below). Can you please update your Bitcoin Node app and then restart Jam (right click on Jam from homescreen and select “restart”). Let me know if this fixes things for you.

Bitcoin Core v26.0 deprecated the RPC command for a certain type of wallet that JoinMarket uses. The newest Bitcoinn Node app update on Umbrel includes a fix to allow these wallets to be generated while the Jam devs work on supporting a new wallet type.

Achim · May 2, 2024, 3:54am

No. This didn’t help.

The problem is not related to the construction of a wallet that Jam uses.

The problem is related to port 5002!
The port is not reachable. Not even the first screen of the Jam app is shown in the browser.

Please fix the port issue.

Thank you.

nmfretz · May 2, 2024, 4:36am

Ah, sorry about that @Achim. I was just responding to another thread where Jam showed a backend server error (which the Bitcoin update fixes), and mistakenly thought this thread was the exact same issue.

I now see from @jz831’s post that nmap output is showing port 5002 as being already in use for them. To help me figure this out, can you let me know whether you have done anything custom when installing umbrelOS on your RPi5 or whether this is just umbrelOS 1.x flashed to the SD.

Edit: I have quickly tested on my RPi4, Umbrel Home, and custom linux install. In all cases I see an rfe service listed with port 5002 but this does not end up clashing with Jam. I’ve reached out to a team member to test on their RPi5 since from these reports it seems to only occur on the pi5

nmfretz · May 2, 2024, 4:52am

@Achim - As a crude, temporary fix can you try the following to change Jam’s web port and see if 5002 is the culprit:

Change Jam’s app proxy port in its manifest file:

Open a terminal into umbrelOS through the Umbrel dashboard by going to Settings page → Advanced settings → Terminal → umbrelOS
Run the following to open the app manifest in a text editor:

sudo nano ~/umbrel/app-data/jam/umbrel-app.yml
Edit the line that says port: 5002 to port: 5005.

Then press Ctrl+X, then y, then Enter to save and exit.

Restart the Jam app

nmfretz · May 2, 2024, 5:27am

Also, @Achim @boroghor @jz831 @Scottydog144 - all logs that have been posted so far in this thread have the following error in the jam web container:

jam_web_1        | dinit: Service nginx process terminated with exit code 1
jam_web_1        | [STOPPD] nginx

But the app proxy is actually running fine on port 5002 without clashing, it is just waiting for the web container to be up and running, which it isn’t for some reason because services in the web container are erroring out. With nginx down in the web container it would make sense that you aren’t seeing anything when accessing port 5002.

jam_app_proxy_1  | Waiting for jam_web_1:80 to open...

If the app proxy on port 5002 was clashing with another service, then the app proxy container would not even be able to start up and instead you’d see an error like this in your logs and the Jam app would be stuck in a restart loop (you’d see it continually restarting on the home screen):

Error response from daemon: driver failed programming external connectivity on endpoint jam_app_proxy_1 (1a3ca0c84d2df9eb662614a1f04b2074fec990e961293d5a2ca37d2522c7945b): Bind for 0.0.0.0:2100 failed: port is already allocated

@Scottydog144 if you aren’t on a RPi5 can you please try this fix ( Umbrel 1.0 - Jam app does not open - #13 by nmfretz) in case you are having the other Jam issue cited above

Scottydog144 · May 2, 2024, 2:30pm

My bitcoin node app was updated and I restarted Jam, still got the 5002 error.

I’m currently downloading umbrel 1.1 to see if that changes anything.

I have a standard RPi4, umbrel home, not linux install.

Scottydog144 · May 2, 2024, 9:31pm

Correction: The issue may be that version 27.0 of the bitcoin node app is not available in the umbrel app store.
Atleast for me, I am running 24.0.1 and there is no optionto upgrade. I can only download 27.0 to my computer directly.

smolgrrr · May 3, 2024, 3:09am

Just to confirm, are you still running 0.5.4 now, or have you updated? I can give you some steps to fetch the latest update.

Topic		Replies	Views
Umbrel very slow and apps won't open Support and Troubleshooting	2	171	June 4, 2024
Can't log into JAM Support and Troubleshooting	0	17	August 2, 2024
Umbrel OS 1.1 is installing on my pi 5 Support and Troubleshooting	1	395	April 17, 2024
Apps not starting after upgrade to 1.0 Support and Troubleshooting	5	847	September 5, 2024
Update Umbrel 1.0 Support and Troubleshooting	4	361	April 13, 2024

Umbrel 1.0 - Jam app does not open

Related Topics