pull down to refresh

I went into my Start9 to see if I had Knots installed, and I did. If you have a start9 unit, you will see that Bitcoin Knots will show as Bitcoin Core. Stuart from S9 emailed me this:
"Switching between the two is a little complicated because of the way this is temporarily set up to allow both to exist and share the same blockchain. Because they do share it, definitely don't uninstall anything. The trick is to get access to downgrade and reinstall options, each of which might be relevant depending on what versions and upgrades are available.Basically...Reinstall method In the StartOS System tab, click the “Manage” heading 5+ times to enable developer mode.
Visit the Marketplace, and the version you want to install. Click “Reinstall” on the service, or

If you get a notification claiming the install failed. Don’t worry, it succeeded. You just need to open the config and click “Save”.

Now, I did this and worked perfect. The issue that I am currently having is that today I went to reset to defaults of Bitcoin Knots, then went to go reinstall Knots (following the above guidelines), and now my electrs is having difficulty connecting.
Here is the log that it is putting out:
2025-05-01T16:02:14-04:00 Starting electrs 0.10.9 on x86_64 linux with Config { network: Bitcoin, db_path: "./db/bitcoin", db_log_dir: None, db_parallelism: 1, daemon_auth: UserPass("bitcoin", "<sensitive>"), daemon_rpc_addr: 172.18.0.147:8332, daemon_p2p_addr: 172.18.0.147:8333, electrum_rpc_addr: 0.0.0.0:50001, monitoring_addr: 127.0.0.1:4224, wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: None, reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, skip_block_download_wait: false, disable_electrum_rpc: false, server_banner: "Welcome to electrs 0.10.9 (Electrum Rust Server)!", signet_magic: f9beb4d9 } 2025-05-01T16:02:14-04:00 [2025-05-01T20:02:14.127Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224 2025-05-01T16:02:14-04:00 [2025-05-01T20:02:14.127Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001 2025-05-01T16:02:14-04:00 [2025-05-01T20:02:14.207Z INFO electrs::db] "./db/bitcoin": 222 SST files, 54.086088916 GB, 6.740308364 Grows 2025-05-01T16:02:15-04:00 [2025-05-01T20:02:15.630Z INFO electrs::chain] loading 894769 headers, tip=00000000000000000001066f18a4a5ac9b764f61bf89ef0ba00c0ce04a4278a0 2025-05-01T16:02:16-04:00 [2025-05-01T20:02:16.579Z INFO electrs::chain] chain updated: tip=00000000000000000001066f18a4a5ac9b764f61bf89ef0ba00c0ce04a4278a0, height=894769 2025-05-01T16:02:16-04:00 [2025-05-01T20:02:16.831Z INFO electrs::db] closing DB at ./db/bitcoin 2025-05-01T16:02:16-04:00 Error: electrs failed 2025-05-01T16:02:16-04:00
2025-05-01T16:02:16-04:00 Caused by: 2025-05-01T16:02:16-04:00 0: bitcoind RPC polling failed 2025-05-01T16:02:16-04:00 1: daemon not available 2025-05-01T16:02:16-04:00 2: JSON-RPC error: transport error: unexpected HTTP code: 401
If anyone could please help me, that would be great. Thank you. I have also reached out to the Start 9 team, as they were quite useful before.
Update:
Got an email back from Start9. This is what they had to say:
"In changing Core to Knots you will have changed the RPC credentials. The services that depend on Bitcoin will need to have their configs opened and saved again (nothing more) so they can fetch the new credentials. Afterwards they should restart and work".
I'm not sure how to do this though. I can find the config and RPC settings of Bitcoin Knots, but how to have that communicate with the rest of the services (do I manually do this, or is there something to do with restarting)? I do not see an option in Electrs to input this information. See the photo.
reply
reply
I’m not sure if I understand the resolve or solution here. Can you elaborate a bit on what I should do? I’m not very dev minded so I appreciate the help
reply
1- check Your node is sync ? see last comments of the link , above ...
2nd: check this link may be
i can not really help you on it as i do not use start9
reply