search

raspiblitz / raspiblitz

Get your own Bitcoin & Lightning Node running - on a RaspberryPi with a nice LCD
MIT License
2.45k stars 520 forks source link

Apps tab won't load on WebUI (#3608) #4012

Closed BlueberryGH closed 7 months ago

BlueberryGH commented 1 year ago

I am having the same issue with Apps not showing on the Apps tab. Running on v 1.9.0 Would appreciate any idea how to fix this other than waiting for the next update to be installed.

Many thanks!

rootzoll commented 1 year ago

Is this still happening?

BlueberryGH commented 1 year ago

Yes, still happening.Am 29.07.2023 um 13:41 schrieb rootzoll @.***>: Is this still happening?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

rootzoll commented 1 year ago

Can you go to "Settings" in the WebUI and "Generate Debug Report" & paste here?

cstenglein commented 1 year ago

@fusion44 could it be a problem with the API? Usually the webui waits for the installed app message, which doesn't seem to arrive here.

fusion44 commented 1 year ago

It is possible, will check on my node later today.

BlueberryGH commented 1 year ago

Here comes the debug report:

[stdout]

SETUPPHASE / BOOTSTRAP see logs: cat /home/admin/raspiblitz.log setupPhase--> done state--> ready

BACKGROUNDSERVICE to monitor Background service call: sudo journalctl -f -u background

BLOCKCHAIN (MAINNET) SYSTEMD STATUS ● bitcoind.service - Bitcoin daemon Loaded: loaded (/etc/systemd/system/bitcoind.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2023-07-13 11:03:18 BST; 2 weeks 4 days ago Process: 6111 ExecStartPre=/home/admin/config.scripts/blitz.systemd.sh log blockchain STARTED (code=exited, status=0/SUCCESS) Process: 6137 ExecStartPre=/bin/chgrp bitcoin /mnt/hdd/bitcoin (code=exited, status=0/SUCCESS) Process: 6142 ExecStart=/usr/local/bin/bitcoind -daemonwait -conf=/mnt/hdd/bitcoin/bitcoin.conf -datadir=/mnt/hdd/bitcoin -debuglogfile=/mnt/hdd/bitcoin/debug.log (code=exited, status=0/SUCCESS) Main PID: 6205 (bitcoind) Tasks: 18 (limit: 9352) CPU: 1w 3d 17h 46min 53.536s CGroup: /system.slice/bitcoind.service └─6205 /usr/local/bin/bitcoind -daemonwait -conf=/mnt/hdd/bitcoin/bitcoin.conf -datadir=/mnt/hdd/bitcoin -debuglogfile=/mnt/hdd/bitcoin/debug.log

Warning: journal has been rotated since unit was started, output may be incomplete.

LAST BLOCKCHAIN (MAINNET) ERROR LOGS sudo journalctl -u bitcoind -b --no-pager -n20 -- Journal begins at Sun 2023-07-30 07:28:54 BST, ends at Mon 2023-07-31 14:19:20 BST. -- -- No entries --

LAST BLOCKCHAIN (MAINNET) INFO LOGS sudo tail -n 50 /mnt/hdd/bitcoin/debug.log 2023-07-31T11:28:20Z UpdateTip: new best=000000000000000000038cb8836602604dcadf838df4d0e2eac6d1a6361227a3 height=801062 version=0x28796000 log2_work=94.332020 tx=872507067 date='2023-07-31T11:27:53Z' progress=1.000000 cache=30.5MiB(151146txo) 2023-07-31T11:28:20Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T11:28:20Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T11:28:20Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T11:28:20Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T11:40:08Z UpdateTip: new best=00000000000000000002015a2714b19cccf1bf1cdafd18aa2b1a43c9b9ae2144 height=801063 version=0x22000000 log2_work=94.332033 tx=872510809 date='2023-07-31T11:39:51Z' progress=1.000000 cache=32.3MiB(164375txo) 2023-07-31T11:41:49Z UpdateTip: new best=00000000000000000002dc8e2ccb02e847b5589897a0e95afcb074e2ddc2263a height=801064 version=0x20006000 log2_work=94.332046 tx=872515388 date='2023-07-31T11:41:38Z' progress=1.000000 cache=33.7MiB(174083txo) 2023-07-31T11:41:49Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T11:44:43Z UpdateTip: new best=00000000000000000003767af0e795e3d7b0d1a89704bab49f8fdcbc03d214e7 height=801065 version=0x20342000 log2_work=94.332059 tx=872521494 date='2023-07-31T11:44:09Z' progress=1.000000 cache=34.5MiB(181735txo) 2023-07-31T11:44:51Z New outbound peer connected: version: 70016, blocks=801065, peer=21987 (outbound-full-relay) 2023-07-31T11:50:11Z Socks5() connect to xzwbohlaf4wazh2rjbd3rc5lmwgp5lxn67dpppbqq5hcanqvympvw2yd.onion:8333 failed: host unreachable 2023-07-31T11:53:45Z New outbound peer connected: version: 70016, blocks=801065, peer=21992 (block-relay-only) 2023-07-31T11:58:28Z Socks5() connect to m6neeyo23eqim6zk4orda54bl7vw7umpscwceg54llmzk5t2wdt3ebyd.onion:8333 failed: host unreachable 2023-07-31T11:59:16Z Socks5() connect to bt3gwklouhhsxmby6m5e7sd5yb47zst6feklics6ancigcfocwrrbqad.onion:8333 failed: host unreachable 2023-07-31T12:03:04Z UpdateTip: new best=00000000000000000002375bdaff6d517ef40275ba9a2b212bceba9b76d242f0 height=801066 version=0x20200004 log2_work=94.332072 tx=872524314 date='2023-07-31T12:02:50Z' progress=1.000000 cache=37.7MiB(206779txo) 2023-07-31T12:03:04Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T12:03:04Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T12:03:04Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T12:03:04Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T12:17:17Z UpdateTip: new best=000000000000000000041394182f95f4eaf0e61196d203da50615e1dda27e165 height=801067 version=0x2001c000 log2_work=94.332085 tx=872526871 date='2023-07-31T12:16:39Z' progress=1.000000 cache=39.8MiB(223707txo) 2023-07-31T12:17:17Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T12:17:17Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T12:17:17Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T12:17:17Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T12:17:59Z UpdateTip: new best=0000000000000000000477aae925a24f795fa63b4c95dc6c528b28f57a4b80c7 height=801068 version=0x299ce000 log2_work=94.332098 tx=872531679 date='2023-07-31T12:17:45Z' progress=1.000000 cache=40.4MiB(227904txo) 2023-07-31T12:17:59Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T12:27:31Z Socks5() connect to u2ifpgtstzxui6jwvdadrhf35rstfdb5a6gwfaui4w6s6wtfuylvnnqd.onion:8333 failed: host unreachable 2023-07-31T12:36:41Z New outbound peer connected: version: 70016, blocks=801068, peer=22023 (block-relay-only) 2023-07-31T12:38:20Z Socks5() connect to 3kpyb6ibnqixlgr4c2rcxmcwlmqnnvklbdo2abyk2jf4vxq4ktuv77qd.onion:8333 failed: host unreachable 2023-07-31T12:38:28Z New outbound peer connected: version: 70016, blocks=801068, peer=22028 (block-relay-only) 2023-07-31T12:39:44Z Socks5() connect to waytry4dhnv6zdnjql776acjgbus76qpxgxbbp5q6ykljz2wbwfjcqid.onion:8333 failed: host unreachable 2023-07-31T12:41:41Z Socks5() connect to xirof6gzput4tw7wsovhvut7ews7cjxtikowdqxb4xbs4kh4in6otaid.onion:8333 failed: host unreachable 2023-07-31T12:46:59Z UpdateTip: new best=00000000000000000002703a21117ae3cada56d1030f5b87dadce7e1208f5d04 height=801069 version=0x2efc0000 log2_work=94.332111 tx=872535105 date='2023-07-31T12:46:24Z' progress=1.000000 cache=44.8MiB(263774txo) 2023-07-31T12:50:49Z New outbound peer connected: version: 70016, blocks=801069, peer=22040 (block-relay-only) 2023-07-31T12:54:19Z UpdateTip: new best=00000000000000000001eda0a0e82a16431d786ec6f4c55d013d6cea36219543 height=801070 version=0x2000e000 log2_work=94.332124 tx=872537237 date='2023-07-31T12:53:59Z' progress=1.000000 cache=46.4MiB(276061txo) 2023-07-31T13:00:49Z UpdateTip: new best=00000000000000000001d3b3b6d9bc3a0f1245836503e0a567c149d2a7ad1e24 height=801071 version=0x325e0000 log2_work=94.332137 tx=872540291 date='2023-07-31T13:00:19Z' progress=1.000000 cache=48.0MiB(289161txo) 2023-07-31T13:00:49Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T13:01:57Z New outbound peer connected: version: 70016, blocks=801071, peer=22045 (block-relay-only) 2023-07-31T13:04:17Z New outbound peer connected: version: 70016, blocks=801071, peer=22046 (block-relay-only) 2023-07-31T13:10:37Z New outbound peer connected: version: 70016, blocks=801071, peer=22051 (block-relay-only) 2023-07-31T13:14:35Z UpdateTip: new best=0000000000000000000176fc22a6b8f1c015e5f80ec4c223587409bff4c943d7 height=801072 version=0x242d6000 log2_work=94.332150 tx=872542575 date='2023-07-31T13:14:20Z' progress=1.000000 cache=49.5MiB(300846txo) 2023-07-31T13:14:35Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T13:14:35Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T13:14:35Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T13:18:35Z Socks5() connect to 42qfhqoyebkpddesxi7zbm3ujcfzmattclannvkdp6g57gkbg5l6nuqd.onion:8333 failed: host unreachable 2023-07-31T13:18:39Z UpdateTip: new best=000000000000000000037de2ad93c1f4d128b696fe23fe5ad7b2a6c1f92fb4d3 height=801073 version=0x2715a000 log2_work=94.332163 tx=872544824 date='2023-07-31T13:20:46Z' progress=1.000000 cache=50.1MiB(305630txo) 2023-07-31T13:18:39Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T13:18:39Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T13:18:39Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications 2023-07-31T13:18:39Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications

LND (MAINNET) SYSTEMD STATUS

CORE LIGHTNING (MAINNET) SYSTEMD STATUS

BLOCKCHAIN (TESTNET) SYSTEMD STATUS

CORE LIGHTNING (TESTNET) SYSTEMD STATUS

BLOCKCHAIN (SIGNET) SYSTEMD STATUS

CORE LIGHTNING (SIGNET) SYSTEMD STATUS

NGINX SYSTEMD STATUS ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/nginx.service.d └─raspiblitz.conf Active: active (running) since Thu 2023-07-13 11:03:02 BST; 2 weeks 4 days ago Docs: man:nginx(8) Process: 8103 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS) Process: 8104 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS) Main PID: 8105 (nginx) Tasks: 5 (limit: 9352) CPU: 9.182s CGroup: /system.slice/nginx.service ├─8105 nginx: master process /usr/sbin/nginx -g daemon on; master_process on; ├─8106 nginx: worker process ├─8107 nginx: worker process ├─8108 nginx: worker process └─8109 nginx: worker process

Warning: journal has been rotated since unit was started, output may be incomplete.

LAST NGINX LOGS sudo journalctl -u nginx -b --no-pager -n20 -- Journal begins at Sun 2023-07-30 07:28:54 BST, ends at Mon 2023-07-31 14:19:21 BST. -- -- No entries -- --> CHECK CONFIG: sudo nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful

BLITZAPI STATUS installed=1 repo='https://github.com/fusion44/blitz_api.git' branch='blitz-v1.9' commit='9255a513cdf64fdc6a060a4fa67a8d9121e6474f' ● blitzapi.service - BlitzBackendAPI Loaded: loaded (/etc/systemd/system/blitzapi.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2023-07-13 11:01:44 BST; 2 weeks 4 days ago Main PID: 794 (python) Tasks: 10 (limit: 9352) CPU: 10h 2min 784ms CGroup: /system.slice/blitzapi.service ├─ 794 /home/blitzapi/blitz_api/venv/bin/python -m uvicorn app.main:app --port 11111 --host=0.0.0.0 --root-path /api ├─261081 /bin/sh -c bash /home/admin/config.scripts/blitz.debug.sh ├─261086 bash /home/admin/config.scripts/blitz.debug.sh ├─261324 sudo systemctl status blitzapi -n2 --no-pager └─261329 systemctl status blitzapi -n2 --no-pager

Jul 31 14:19:22 raspberrypi sudo[261324]: blitzapi : PWD=/home/blitzapi/blitz_api ; USER=root ; COMMAND=/usr/bin/systemctl status blitzapi -n2 --no-pager Jul 31 14:19:22 raspberrypi sudo[261324]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1003)

LAST BLITZAPI LOGS sudo journalctl -u blitzapi -b --no-pager -n20 -- Journal begins at Sun 2023-07-30 07:28:54 BST, ends at Mon 2023-07-31 14:19:22 BST. -- Jul 31 14:19:21 raspberrypi sudo[261160]: blitzapi : PWD=/home/blitzapi/blitz_api ; USER=root ; COMMAND=/usr/sbin/nginx -t Jul 31 14:19:21 raspberrypi sudo[261160]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1003) Jul 31 14:19:21 raspberrypi sudo[261160]: pam_unix(sudo:session): session closed for user root Jul 31 14:19:21 raspberrypi sudo[261247]: blitzapi : PWD=/home/blitzapi/blitz_api ; USER=blitzapi ; COMMAND=/usr/bin/git config --get remote.origin.url Jul 31 14:19:21 raspberrypi sudo[261247]: pam_unix(sudo:session): session opened for user blitzapi(uid=1003) by (uid=1003) Jul 31 14:19:21 raspberrypi sudo[261247]: pam_unix(sudo:session): session closed for user blitzapi Jul 31 14:19:21 raspberrypi sudo[261261]: blitzapi : PWD=/home/blitzapi/blitz_api ; USER=blitzapi ; COMMAND=/usr/bin/git rev-parse --abbrev-ref HEAD Jul 31 14:19:21 raspberrypi sudo[261261]: pam_unix(sudo:session): session opened for user blitzapi(uid=1003) by (uid=1003) Jul 31 14:19:21 raspberrypi sudo[261261]: pam_unix(sudo:session): session closed for user blitzapi Jul 31 14:19:21 raspberrypi sudo[261273]: blitzapi : PWD=/home/blitzapi/blitz_api ; USER=blitzapi ; COMMAND=/usr/bin/git rev-parse HEAD Jul 31 14:19:21 raspberrypi sudo[261273]: pam_unix(sudo:session): session opened for user blitzapi(uid=1003) by (uid=1003) Jul 31 14:19:21 raspberrypi sudo[261273]: pam_unix(sudo:session): session closed for user blitzapi Jul 31 14:19:21 raspberrypi sudo[261284]: blitzapi : PWD=/home/blitzapi/blitz_api ; USER=root ; COMMAND=/usr/bin/systemctl status blitzapi Jul 31 14:19:21 raspberrypi sudo[261284]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1003) Jul 31 14:19:22 raspberrypi sudo[261284]: pam_unix(sudo:session): session closed for user root Jul 31 14:19:22 raspberrypi sudo[261324]: blitzapi : PWD=/home/blitzapi/blitz_api ; USER=root ; COMMAND=/usr/bin/systemctl status blitzapi -n2 --no-pager Jul 31 14:19:22 raspberrypi sudo[261324]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1003) Jul 31 14:19:22 raspberrypi sudo[261324]: pam_unix(sudo:session): session closed for user root Jul 31 14:19:22 raspberrypi sudo[261331]: blitzapi : PWD=/home/blitzapi/blitz_api ; USER=root ; COMMAND=/usr/bin/journalctl -u blitzapi -b --no-pager -n20 Jul 31 14:19:22 raspberrypi sudo[261331]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1003)

BLITZ WebUI STATUS installed=1 repo='https://github.com/cstenglein/raspiblitz-web.git' branch='release/v1.9' commit='7ebb54ee1f89a136cc9e4e558e21b6171438eda4'

LAST 20 ElectRS LOGS sudo journalctl -u electrs -b --no-pager -n20 -- Journal begins at Sun 2023-07-30 07:28:54 BST, ends at Mon 2023-07-31 14:19:22 BST. -- -- No entries --

ElectRS Status

STATUS ELECTRS SERVICE

version='v0.9.11' configured=1 serviceInstalled=1 serviceRunning=1 localIP='192.168.178.191' publicIP='127.0.0.1' portTCP='50001' localTCPPortActive=1 publicTCPPortAnswering=1 portSSL='50002' localHTTPPortActive=1 publicHTTPPortAnswering=1 TorRunning=1 nginxTest=1 serviceRunning=1 electrumResponding=1 initialSynced=1

MOUNTED DRIVES df -T -h Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 29G 18G 9.9G 65% / devtmpfs devtmpfs 3.9G 0 3.9G 0% /dev tmpfs tmpfs 3.9G 16K 3.9G 1% /dev/shm tmpfs tmpfs 1.6G 1.1M 1.6G 1% /run tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 32M 0 32M 0% /var/cache/raspiblitz /dev/mmcblk0p1 vfat 255M 32M 224M 13% /boot /dev/sda1 ext4 916G 621G 250G 72% /mnt/hdd tmpfs tmpfs 787M 16K 787M 1% /run/user/1000

SD CARD HOMES sudo du -ahd1 /home 2.7G /home/bitcoin 813M /home/blitzapi 425M /home/admin 1.2G /home/thunderhub 503M /home/electrs 422M /home/rtl 35M /home/pi 549M /home/jam 546M /home/joinmarket 176M /home/btcrpcexplorer 2.3G /home/btcpay 638M /home/lnbits 1.4G /home/mempool 12G /home

LOGFILES Archived and active journals take up 316.0M in the file system. 1.1G /var/log

DATADRIVE

RASPIBLITZ DATA DRIVE Status

BASICS

isMounted=1 isBTRFS=0 hddRaspiData=1 hddRaspiVersion='1.9.0' isSMART=1 isSSD=1 datadisk='sda' datapartition='sda1' hddCandidate='sda' hddPartitionCandidate='sda1' hddBlocksBitcoin=1 hddBytes=1000203820544 hddGigaBytes=931 hddUsedInfo='621G (72%)' hddDataFreeBytes=267338412032 hddDataFreeKB=261072668 hddDataFreeGB=248 hddAdapterUSB='174c:0825' hddAdapterUSAP=1

RAID

isRaid=0 raidCandidates=0

SWAP

isSwapExternal=1 SwapExternalPath='/mnt/hdd/swapfile'

NETWORK localip=192.168.178.191 localiprange=192.168.178.0/24 dhcp=1 network_device=eth0

HARDWARE TEST RESULTS UndervoltageReports in Logs: 0

SYSTEM CACHE STATUS system_up="1567150" system_count_start_lightning="0" system_cpu_load=" 4.69, 3.90, 3.47" system_ups_status="OFF" system_vm_vagrant="0" system_ram_available_mb="5787" system_count_longscan="0" system_count_undervoltage="0" system_temp_celsius="68" system_temp_fahrenheit="154" system_ram_gb="8" system_ups_battery="" system_init_time="1689242509" system_board="rp4" system_count_start_tui="0" system_count_start_blockchain="1" system_ram_mb="7862" ln_default_sync_initial_done="" btc_default_error_short="" btc_default_blocks_data_kb="554116960" btc_default_error_full="" btc_default_sync_initial_done="1" btc_default_synced="1" btc_default_running="1" btc_default_sync_progress="1" btc_default_port="8333" btc_default_blocks_verified="801073" btc_default_online="1" btc_default_version="v24.0.1" btc_default_activated="1" btc_default_blocks_behind="0" btc_default_ready="1" btc_default_sync_initialblockdownload="0" btc_default_mempool_transactions="126259" btc_default_sync_percentage="100.00" btc_default_blocks_headers="801073" btc_default_peers="21"

OPTION: SHARE THIS DEBUG OUTPUT An easy way to share this debug output on GitHub or on a support chat Use the following command and share the resulting link using termbin.com service and tor proxy: debug -l If tor is failing and you don't mind leaking your ip address to the termbin service, use without tor: debug -l -n

fusion44 commented 1 year ago

It works on my node. I can't see anything suspicious in the logs above either. Maybe the API hangs when it tries to get install info from REDIS.

scubafly commented 1 year ago

I have the same issue on 1.9.0 Also I'm not seeing the installed apps on the left side. Under settings the version number is missing. And on home there is a spinner in the block left to the "Hardware Details"

The last thing I did was install BTCpay. I will disable BTCpay trough ssh when I'm home and let you know if this fixes it for me. Logs are here: https://pastebin.com/QnkT2Xpe

cstenglein commented 1 year ago

@fusion44 I got a similar problem on my testnode as well.

The only messages I get are system_startup_info, ping and btc_info.

Node & blitz api running without issues. Load is at 3.01 so not super busy.

Restart of blitzapi fixed it.

scubafly commented 1 year ago

I removed BTCPay, shutdown, reconnected al the wires. Now It looks like it is stable. uptime: up 11:38, 3 users, load average: 2.01, 2.02, 1.99. Will update if I see this issue again. If not, it will be resolved for me.

BlueberryGH commented 1 year ago

Some additional info:

The Apps menu worked just fine before I have started the Electrum server on the Raspi.

The Activation process did not run through properly, so that I have powered off and restarted the Raspi after several hours of waiting.

Perhaps an open file was damaged at this point?

Is there anything I can do (re-install, update,…)?

Would appreciate any help.

Von: rootzoll @.> Gesendet: Samstag, 29. Juli 2023 15:51 An: raspiblitz/raspiblitz @.> Cc: BlueberryGH @.>; Author @.> Betreff: Re: [raspiblitz/raspiblitz] Apps tab won't load on WebUI (#3608) (Issue #4012)

Can you go to "Settings" in the WebUI and "Generate Debug Report" & paste here?

— Reply to this email directly, view it on GitHub https://github.com/raspiblitz/raspiblitz/issues/4012#issuecomment-1656735896 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BBIAVB6ESU53XT3UILT5LJ3XSUIL5ANCNFSM6AAAAAA2I2YTGM . You are receiving this because you authored the thread. https://github.com/notifications/beacon/BBIAVB5NLSM6P7G2OMVYKWLXSUIL5A5CNFSM6AAAAAA2I2YTGOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTCX7EJQ.gif Message ID: @. @.> >

cstenglein commented 1 year ago

@BlueberryGH is this still an issue with 1.10?

BlueberryGH commented 1 year ago

YesAm 10.10.2023 um 18:39 schrieb Christoph Stenglein @.***>: @BlueberryGH is this still an issue with 1.10?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

scubafly commented 1 year ago

For mee the 1.10 version looks to be more stable. I still have to try if it keeps stable if I instal the BTCPay server.

Radiokot commented 11 months ago

I also have this problem, albeit electrs is still indexing.

rwernerar commented 10 months ago

I'm having the same problem with the latest software version. The Apps tab keeps loading and never finishes! When I initially installed the software, it was working, so it must be some setting that I changed later. I will probably start a new, clean installation and make changes step by step to identify where the problem is coming from!

helishmopter commented 8 months ago

Having the same issue as above in 1.10. Apps tab won't stop loading in webUI. No LN installed, just BTC. Blockchain 100 % synced. No other apps running. Tried re-installing 1.10. with same result (app tab not loading). Also attempted re-activating 'Blitz API + WebUI' in Node Settings & Options, with the result of being completely locked out of the webUI (502 Bad Gateway). Any help is much appreciated!

cstenglein commented 8 months ago

@helishmopter @Radiokot @rwernerar Can you check if the blitzapi is running?

Log in via SSH and type sudo service blitzapi status

If it displays something like EXITED like this:

grafik

Then please post the output of the following command here:

sudo journalctl -fu blitzapi

Thank you!

@fusion44 On installation I get the following error:

Feb 17 09:23:16 raspberrypi blitz.web.api.sh[80768]: # '.env' config updates - blitzapi maybe needs to be restarted
Feb 17 09:23:16 raspberrypi systemd[1]: Started BlitzBackendAPI.
Feb 17 09:23:16 raspberrypi python[80845]: /home/blitzapi/blitz_api/venv/bin/python: No module named uvicorn
helishmopter commented 8 months ago

@cstenglein I get the following: blitzapi

sudo journalctl -fu blitzapi

Feb 16 07:23:46 raspberrypi python[760]: 2024-02-16 07:23:46 | ⚠️ | utils.py:69 | Key 'hdd_capacity_bytes' not found in Redis DB. Feb 16 07:23:46 raspberrypi python[760]: 2024-02-16 07:23:46 | ⚠️ | utils.py:69 | Key 'hdd_free_bytes' not found in Redis DB. Feb 16 07:23:48 raspberrypi python[760]: 2024-02-16 07:23:48 | ⚠️ | utils.py:69 | Key 'hdd_capacity_bytes' not found in Redis DB. Feb 16 07:23:48 raspberrypi python[760]: 2024-02-16 07:23:48 | ⚠️ | utils.py:69 | Key 'hdd_free_bytes' not found in Redis DB. Feb 16 07:24:27 raspberrypi python[760]: 2024-02-16 07:24:27 | ℹ️ | service.py:46 | Bitcoin Core initializing, waiting 10 seconds... Feb 16 07:24:37 raspberrypi python[760]: 2024-02-16 07:24:37 | ℹ️ | service.py:46 | Bitcoin Core initializing, waiting 10 seconds... Feb 16 07:24:47 raspberrypi python[760]: 2024-02-16 07:24:47 | ℹ️ | service.py:46 | Bitcoin Core initializing, waiting 10 seconds... Feb 16 07:24:57 raspberrypi python[760]: 2024-02-16 07:24:57 | ℹ️ | service.py:46 | Bitcoin Core initializing, waiting 10 seconds... Feb 16 07:25:07 raspberrypi python[760]: 2024-02-16 07:25:07 | ℹ️ | service.py:46 | Bitcoin Core initializing, waiting 10 seconds... Feb 16 07:25:17 raspberrypi python[760]: 2024-02-16 07:25:17 | ✔️ | service.py:39 | Bitcoin repository initialized

fusion44 commented 8 months ago

@helishmopter @Radiokot @rwernerar Can you check if the blitzapi is running?

Log in via SSH and type sudo service blitzapi status

If it displays something like EXITED like this:

grafik

Then please post the output of the following command here:

sudo journalctl -fu blitzapi

Thank you!

@fusion44 On installation I get the following error:

Feb 17 09:23:16 raspberrypi blitz.web.api.sh[80768]: # '.env' config updates - blitzapi maybe needs to be restarted
Feb 17 09:23:16 raspberrypi systemd[1]: Started BlitzBackendAPI.
Feb 17 09:23:16 raspberrypi python[80845]: /home/blitzapi/blitz_api/venv/bin/python: No module named uvicorn

Seems like it's not an API error. Something went wrong during install. The unicorn package was not installed properly. Did you try a second time?

rootzoll commented 7 months ago

So far this looks good on my testmachines on RC4. Closing this issue for release. Please comment/reopen when this error happens with v1.11.0rc4 or later.