You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tried running jam in docker with different credentials first, had problems starting the service (maybe conflict with port because of local mempool.space inside docker), tried with different port - didnt work, tried after shutting down mempool. at this point i got the webservice running but encontered some kind of error after clicking through the starting we gui.
Tried again with different credentials:
A clear and concise description of what you expected to happen.
Remove leftover wallet lockfiles before startup...
~/.joinmarket/ssl /src/scripts
Generating a RSA private key
.......++++
.......................................................................................................................................................................................................................................................................................................................................................................++++
writing new private key to 'key.pem'
/src/scripts
Waiting for bitcoind to accept RPC requests...
Successfully waited for bitcoind to accept RPC requests.
Creating wallet jm_webui_default if missing...
Loading wallet jm_webui_default...
[ OK ] nginx
[ OK ] tor
[ OK ] jmwalletd
[ OK ] ob-watcher
[ OK ] boot
dinit: Service jmwalletd process terminated with exit code 1
dinit: Service ob-watcher process terminated with exit code 1
dinit: Service jmwalletd process terminated with exit code 1
dinit: Service ob-watcher process terminated with exit code 1
dinit: Service jmwalletd process terminated with exit code 1
dinit: Service ob-watcher process terminated with exit code 1
dinit: Service jmwalletd process terminated with exit code 1
dinit: Service jmwalletd restarting too quickly; stopping.
dinit: Service jmwalletd restarting too quickly; stopping.
[STOPPD] jmwalletd
dinit: Service ob-watcher process terminated with exit code 1
dinit: Service ob-watcher restarting too quickly; stopping.
dinit: Service ob-watcher restarting too quickly; stopping.
[STOPPD] ob-watcher
^C[STOPPD] boot
[STOPPD] tor
[STOPPD] nginx
A clear and concise description of what the bug is and what actually happens.
Steps to reproduce the problem
tried to remove all docker files / image, rebooting, restart from scratch
-> still the same problem
maybe there is some kind of data left on my local storage that i cant find and thats messing with the installation?
Platform: Running kubuntu 22.04 with bitcoin core 26.0
Browser: Firefox (but problem lies within starting the program)
Additional context
Add any other context about the problem here to help explain your problem.
e.g. error logs or screenshots if applicable. Make sure to remove any confidential information before sharing screenshots or logs.
The text was updated successfully, but these errors were encountered:
The logs of service jmwalletd would hopefully give more insight of what might the culprit here.
Can take a look into log file jmwalletd_stdout.log (e.g. by mapping the directory /var/log/jam)?
Running kubuntu 22.04 with bitcoin core 26.0
tried running jam in docker with different credentials first, had problems starting the service (maybe conflict with port because of local mempool.space inside docker), tried with different port - didnt work, tried after shutting down mempool. at this point i got the webservice running but encontered some kind of error after clicking through the starting we gui.
Tried again with different credentials:
bash:
sudo docker run --rm -it --add-host=host.docker.internal:host-gateway --env JM_RPC_HOST="host.docker.internal" --env JM_RPC_PORT="8332" --env JM_RPC_USER="RPCUSER" --env JM_RPC_PASSWORD="RPCPWD" --env APP_USER="JAM" --env APP_PASSWORD="JAMPWD" --env ENSURE_WALLET="true" --env REMOVE_LOCK_FILES="true" --env RESTORE_DEFAULT_CONFIG="true" --volume jmdatadir:/root/.joinmarket --publish "8080:80" ghcr.io/joinmarket-webui/jam-standalone:v0.2.0-clientserver-v0.9.11
A clear and concise description of what you expected to happen.
Remove leftover wallet lockfiles before startup...
~/.joinmarket/ssl /src/scripts
Generating a RSA private key
.......++++
.......................................................................................................................................................................................................................................................................................................................................................................++++
writing new private key to 'key.pem'
/src/scripts
Waiting for bitcoind to accept RPC requests...
Successfully waited for bitcoind to accept RPC requests.
Creating wallet jm_webui_default if missing...
Loading wallet jm_webui_default...
[ OK ] nginx
[ OK ] tor
[ OK ] jmwalletd
[ OK ] ob-watcher
[ OK ] boot
dinit: Service jmwalletd process terminated with exit code 1
dinit: Service ob-watcher process terminated with exit code 1
dinit: Service jmwalletd process terminated with exit code 1
dinit: Service ob-watcher process terminated with exit code 1
dinit: Service jmwalletd process terminated with exit code 1
dinit: Service ob-watcher process terminated with exit code 1
dinit: Service jmwalletd process terminated with exit code 1
dinit: Service jmwalletd restarting too quickly; stopping.
dinit: Service jmwalletd restarting too quickly; stopping.
[STOPPD] jmwalletd
dinit: Service ob-watcher process terminated with exit code 1
dinit: Service ob-watcher restarting too quickly; stopping.
dinit: Service ob-watcher restarting too quickly; stopping.
[STOPPD] ob-watcher
^C[STOPPD] boot
[STOPPD] tor
[STOPPD] nginx
A clear and concise description of what the bug is and what actually happens.
Steps to reproduce the problem
tried to remove all docker files / image, rebooting, restart from scratch
-> still the same problem
maybe there is some kind of data left on my local storage that i cant find and thats messing with the installation?
Specifications
Additional context
Add any other context about the problem here to help explain your problem.
e.g. error logs or screenshots if applicable. Make sure to remove any confidential information before sharing screenshots or logs.
The text was updated successfully, but these errors were encountered: