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

[amtexugo]

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
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'

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

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

---

[al-munazzim]

Thanks for the detailed report. From the configuration shown, Specter is reaching an HTTP endpoint that returns a web 404 instead of a Bitcoin Core JSON-RPC response, so this is most likely a connection/host/port mismatch rather than a wallet problem.

A few safe checks/remediation steps:

1. In Specter’s node connection settings, make sure the RPC URL points to the Bitcoin Core RPC service, not the Umbrel web UI or proxy. If Specter and Bitcoin Core are both running inside Umbrel/Docker, the LAN IP may not be the right hostname from inside the container; Umbrel app networking usually requires the internal service/hostname and port rather than 192.168.100.3:8332.
2. Your bitcoin.conf shows rpcbind=127.0.0.1:8332 and rpcallowip=10.21.0.0/16. Binding only to 127.0.0.1 means Bitcoin Core may not accept RPC from another container/LAN address. On Umbrel, prefer the supported Umbrel app connection details if available; otherwise confirm Bitcoin Core is listening on the interface Specter can actually reach.
3. Please do not paste the RPC password/token publicly. If the password in the issue is real or was copied directly from Umbrel, rotate/regenerate it.
4. Please attach the relevant Specter log lines from the failed connection attempt, and if possible the exact Host/Port fields shown in Specter after redacting the password. Also let us know whether Specter was installed as the Umbrel app, as a binary, or in Docker.

As a quick diagnostic, from the machine/container where Specter runs, the Bitcoin RPC endpoint should answer JSON-RPC requests; a browser-style 404 page means the request is hitting the wrong HTTP service/path.