cryptoadvance / cryptoadvance/specter-desktop
Getting timeout error when creating hotwallet ...
- Dominant language
- Python
- Stars
- 847
- Forks
- 259
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 2
Description
**Describe the bug**
when creating a hotwallet on my fullnode i get the error below ... directory is created with various files but the process doesn't successfully complete
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
2024-01-22T20:05:47.215Z [info] : stderr-SPECTERD: ERROR in rpc: HTTPConnectionPool(host='192.168.3.7', port=8332): Read timed out. (read timeout=60.0)
Traceback (most recent call last):
File "urllib3/connectionpool.py", line 466, in _make_request
File "", line 3, in raise_from
File "urllib3/connectionpool.py", line 461, in _make_request
File "http/client.py", line 1368, in getresponse
File "http/client.py", line 317, in begin
File "http/client.py", line 278, in _read_status
File "socket.py", line 705, in readinto
TimeoutError: timed out
**Desktop (please complete the following information):**
- Where is your node running: [e.g. raspiblitz, MyNode, umbrel, local(internal), local(external)] remove intel NUC with ubuntu
- Where is your specter running: [e.g. Raspiblitz, Node, umbrel, binary] binary
- If you're running a binary, which OS: [e.g. Linux, MacOs, Windows] MacOs
- Browser [e.g. chrome, safari] firefox
- Specter Version [e.g. 1.9.4] 2.0.2
**Additional context**
Add any other context about the problem here.
Contributor guide
Research direction
Start by reproducing hotwallet creation with Specter 2.0.2 on the listed MacOS and Ubuntu fullnode setup, then inspect the RPC request that times out at 192.168.3.7:8332. Confirm whether the process can complete successfully or report a clearly diagnosed failure and reproduction path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100