After uninstalling an own server, the desktop app stays on it and shows Cloudflare's Error 1033 page

Open
#81 0 comments 0 reactions 0 assignees View on GitHub

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
Domain
backend, desktop

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
  1. Link an own server with the --cloudflare install line, and keep it selected in the desktop app.
  2. On the server, run curl -fsSL https://link.dusk.bot/uninstall.sh | sh -s -- --yes.
  3. 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DuskBotAI/duskbot

All issues in DuskBotAI/duskbot

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.