cryptoadvance / cryptoadvance/specter-desktop

(RPC connect) 404 Not Found: The requested URL was not found on the server. (RPC connect)

Open
#2,701 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
847
Forks
259
Avg merge
6d 18h
Merged PRs (30d)
2

Description

Server error
Exception
404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
[Back to the main page](http://192.168.100.3:25441/welcome/)
Details
version: v2.1.11

1. Go to '... connections'
2. Click on ' engine icon.'
3. Scroll down to 'Name
Edit name
Configuration
umbrel
••••••••••••••••••••••••••••••••••••••••••••
http://192.168.100.3
8332
press Connect'
4.
Is this not a fresh wallet? Did you expect transactions here? Then click 👇 to find themGo to blockchain press rescan
--

5. See error
Is this not a fresh wallet? Did you expect transactions here? Then click 👇 to find them
[Go to blockchain rescan](http://192.168.100.3:25441/wallets/wallet//settings/clearcache?rescan_blockchain=True)

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
- Where is your node running: umbrel,
- Where is your specter running: umbrel, binary]
- If you're running a binary, which OS: umbrel os (Linux)
- Browser chrome, safari
- Specter Version [[e.g. 1.9.4]](version: v2.1.11)

**Additional context**

bitcoin.conf and umbrel-bitcoin.conf below

# Load additional configuration file, relative to the data directory.
includeconf=umbrel-bitcoin.conf

rpcbind=127.0.0.1:8332
rpcallowip=10.21.0.0/16
server=1
rpcuser=umbrel
rpcpassword=******************************
disablewallet=0

____

Contributor guide

Open the contributing guide

Research direction

Reproduce the failure from Connections by configuring the Umbrel node at the reported address and port, then pressing Connect. Inspect the RPC connection request and the returned 404 alongside the provided Bitcoin configuration; done means the connection succeeds without the error and the rescan path remains usable.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.