After uninstalling an own server, the desktop app stays on it and shows Cloudflare's Error 1033 page
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start by tracing how the desktop app learns that an own server has been unlinked and how it chooses the current environment; the issue does not name files or tests. Reproduce by selecting a Cloudflare-linked server, running the uninstall command from the issue, and checking the app window. Done when unlinking returns the app to this computer or shows a removed-server state with Forget and Connect to a server actions.
Written by the indexing model from the issue text.
Description
What happened
I removed an own server with uninstall.sh (it reported "Unlinking from your app... done, the app sees it as unlinked"). The desktop app kept that server selected as the current environment and showed Cloudflare's raw error page for the old quick-tunnel address:
Error 1033 - Cloudflare Tunnel error
... is configured as a Cloudflare Tunnel, and Cloudflare is currently unable to resolve it.
There was no message saying the server was gone and no way back from that page. I had to find Server > This computer / Forget in the menu bar.
Expected: once the server is unlinked, the app switches back to this computer, or shows a "this server was removed" state with Forget and Connect to a server actions, instead of the tunnel provider's error page.
Steps to reproduce
- Link an own server with the
--cloudflareinstall line, and keep it selected in the desktop app. - On the server, run
curl -fsSL https://link.dusk.bot/uninstall.sh | sh -s -- --yes. - Look at the desktop app window.
Version
desktop 0.2.18
Platform
macOS + Own server (VPS)
- Dominant language
- TypeScript
- Stars
- 277
- Forks
- 27
- Avg merge
- 2h 47m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from DuskBotAI/duskbot
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
install.sh --tailscale replaces whatever the host already serves on tailnet port 443Possibly taken @viniciusbregoli claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 43/100
Maintainers usually reply within 1 day
All issues in DuskBotAI/duskbot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
outline/outline#14638 · 1 comment ·
Maintainers usually reply within 1 day
-
wayfinder:grilling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patricktree/cup#484 ·
-
bot:ai-assisted component:platform-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
midnightntwrk/platform-js#69 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day