Readeck Integration not working
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39k
- Forks
- 2.1k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Platform
Desktop - Windows
Describe the bug
Configured Readeck Base URL and API key. Get "Failed to save to Readeck." message when attempting to save any article.
Entry ID
No response
Relevant Information
Self hosting Readeck on Synology NAS via Portainer with Synology Reverse Proxy configured with Websocket enabled.
Reproduction Video
No response
Environment
Environment
App Version: 0.7.0
OS: Windows
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Folo/0.7.0 Chrome/138.0.7204.97 Electron/37.2.0 Safari/537.36
Env: electron
Browser: Chrome
Session Trace Id: hjDjX3kO80Cz3XVXUPryr
Mode: production
Renderer: 0.7.0
Validations
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- This issue is valid
Contributions
- I am willing to submit a PR to fix this issue
- I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure in the Windows Electron environment using the configured Readeck base URL and API key, then trace the save-to-Readeck request and its error handling. Check the reverse-proxy and WebSocket setup described in the report. Done means articles save successfully and the failure path has coverage or a clearly verified fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100