ERROR 006 (Application Error): error running wizard: workspace not found.

Describe the bug
Slackdump crashes with "ERROR 006 (Application Error): error running wizard: workspace not found." error when attempting to access specific Slack workspace (non-enterprise, but Business+ paid plan). Crash / error happens when I attempt to login.

Authentication type (please read)
Google

To Reproduce
Steps to reproduce the behavior:

Added new Slack workspace (correctly) as socratik and as socratik.slack.com - both cases, same result.
Selected User Browser, selected Edge (also tried Chrome - same result).

Expected behavior
A clear and concise description of what you expected to happen.

Output
If applicable, add output to help explain your problem.

Desktop (please complete the following information):

OS: Windows
OS Version: 11
Slackdump Version: [e.g. 2.4.2]

Additional context
Add any other context about the problem here.

Could you run:

slackdump workspace list

and see if it is displayed, and has => pointer on it, i.e.

[7:29:14] 0:wp/_github/slackdump (master)> slackdump workspace list
Workspaces in "/Users/rustam/Library/Caches/slackdump":

   xxxx (file: xxxx.bin, last modified: 2026-06-24 22:22:57)
=> ora600 (file: ora600.bin, last modified: 2026-07-19 21:48:15)

Current workspace is marked with ' => '.

If it is in the list, try rerunning

slackdump workspace select socratik

and try to run slackdump wiz again.

If it is not displayed, could you please repeat the login process, but this time starting the login wizard with trace:

slackdump.exe workspace wiz -v -trace=trace.out -log-json -log=login.log.json

then run:

slackdump tools encrypt trace.out
slackdump tools encrypt login.log.json

and upload it to this issue?

The files will be encrypted by my GPG key.

C:\Users\silic\Downloads\slackdump_Windows_x86_64-3>slackdump.exe socratik wiz -v -trace=trace.out -log-json -log=login.log.json
slackdump socratik: unknown command
Run 'slackdump help' for usage.

C:\Users\silic\Downloads\slackdump_Windows_x86_64-3>slackdump.exe workspace wiz -v -trace=trace.out -log-json -log=login.log.json
slackdump workspace wiz: unknown command
Run 'slackdump help workspace' for usage.

Am I using an old version?

C:\Users\silic\Downloads\slackdump_Windows_x86_64-3>slackdump.exe

Slackdump 3.0.5 (commit: 6e6287d) built on: 2025-01-31T23:47:34Z

Yes, that's an old one, I wish it was still 2025-01-31.

v4.4.3 is the current version. Hopefully it will work straight away:
https://github.com/rusq/slackdump/releases/download/v4.4.3/slackdump_Windows_x86_64.zip

Here's all the rest of the release files:
https://github.com/rusq/slackdump/releases/tag/v4.4.3

I put this in a new folder (but left the settings file in C:\Users\silic\AppData\Local\slackdump there

C:\Users\silic\Downloads\slackdump_Windows_x86_64-4>slackdump.exe workspace wiz -v -trace=trace.out -log-json -log=login.log.json
2026-08-18 21:35:01 INFO trace will be written to filename: trace.out
{"time":"2026-08-18T21:35:01.7392328+05:30","level":"DEBUG","msg":"log messages will be written to file","filename":"login.log.json"}

C:\Users\silic\Downloads\slackdump_Windows_x86_64-4>slackdump encrypt trace.out
slackdump encrypt: unknown command
Run 'slackdump help' for usage.

C:\Users\silic\Downloads\slackdump_Windows_x86_64-4>slackdump.exe encrypt trace.out
slackdump encrypt: unknown command
Run 'slackdump help' for usage.

C:\Users\silic\Downloads\slackdump_Windows_x86_64-4>

Then I removed all settings files - and it stopped working for known workspaces as well (where the 2025 version was working fine!)

C:\Users\silic\Downloads\slackdump_Windows_x86_64-4>slackdump.exe
2026-08-18 21:38:20 ERROR 006 (Application Error): error running wizard:
│ workspace not found.

C:\Users\silic\Downloads\slackdump_Windows_x86_64-4>slackdump.exe
2026-08-18 21:38:45 INFO using system browser for interactive login (workaround
│ for slackdump#675)
└ path: C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
2026-08-18 21:38:45 ERROR 006 (Application Error): error running wizard:
│ workspace not found.

C:\Users\silic\Downloads\slackdump_Windows_x86_64-4>slackdump.exe
2026-08-18 21:39:02 ERROR 006 (Application Error): error running wizard:
│ workspace not found.

C:\Users\silic\Downloads\slackdump_Windows_x86_64-4>

Thanks for checking. Sorry it's slackdump tools encrypt, missed the "tools" part. I will update instructions in the earlier message.

I'll see if I can reproduce this on a windows machine when I get to it.

Meanwhile, if you could upload those encrypted files, it'd be helpful. Thanks for your help on resolving this.

I encountered this when using the tool for the first time yesterday. slackdump wiz, Google Auth, Brave/Google Chrome browsers, etc.

Full disclosure, I used Claude Sonnet to help troubleshoot. What it found appears to be valid, however.

Bare requests to the workspace URL return a 403, rather than a 200/404. In rusq/slackauth the checkWorkspaceURL function expects a 200 and treats all other codes as "Not Found".

Example request:

curl -s -o /dev/null -w "%{http_code}\n" "https://gophers.slack.com/"

Agent Output

Good news: this isn't something wrong with your setup (Brave vs. Chrome, Google SSO, or a typo in the workspace name). I found the root cause.

What's happening

Before slackdump wiz ever opens a browser, it runs a preflight check in the underlying rusq/slackauth library (checkWorkspaceURL):

// checkWorkspaceURL checks if the workspace exists. Slack returns 200 on
// existing workspaces and 404 on non-existing ones.
func checkWorkspaceURL(uri string) error {
if resp, err := http.Head(uri); err != nil {
return ErrWorkspaceNotFound
} else if resp.StatusCode != http.StatusOK {
return ErrWorkspaceNotFound
}
return nil
}

It sends a plain, non-browser HTTP request to https://.slack.com/ and treats any non-200 response as "the workspace doesn't exist," aborting before the browser even opens.

I tested this directly: sourceallies.slack.com returns HTTP 403, not 200, to a bare request, even though the TLS certificate and response headers (x-slack-unique-id, via: slack-prod.tinyspeck.com, full Slack app HTML) confirm it's a real, live workspace. I checked two other unrelated Slack workspaces (slackhq.slack.com, gophers.slack.com) and they also return 403. So Slack appears to have recently changed their edge/bot-protection behavior to reject these bare, non-browser requests, which breaks slackdump's naive existence check across the board, it's not specific to your workspace name, network, or browser choice.

This matches an open GitHub issue filed today with the exact same "workspace not found" error, still unresolved, with the maintainer actively investigating.

Attaching files corresponding to latest version and settings file back in AppData folder

trace.out.encrypted.txt

login.log.json.encrypted.txt

@UnstoppableMango

@UnstoppableMango thanks for diagnostics, have implemented this in slackauth. Tried also with custom utls, suspecting that they did not like the standard Go HTTP client, but that wasn't a case, so treating 403 as "workspace exists"

@siliconpi thanks for the bug report, once the linked PR is merged, it should start working. Will release the patch version shortly. Traces basically confirmed what @UnstoppableMango wrote (thanks for the traces)

Fixed in v4.4.4, (it's currently building) please update/download from releases once it's published.

Sorry - I dont think it worked. I tried it first when no MS Edge was visible, but apparently the processes were running. Then I killed them and tried again. Same error:

Then tried it again - this time selecting Chrome - a different set of errors:

Sorry - I posted under a different account accidentally.

@siliconpi

Hey @siliconpi, That is a different error, and it's related to the browser on your system. I'll try to reproduce it on windows and see if I get the same

Ok, was able to reproduce it. Seems that edge took the same path as Chrome in a sense that it now requires the non-default user directory to work with automation, which renders it useless as a "User Browser" as it won't be accessing user data.

In the long term I think the cookie extraction should be implemented.

As a workaround please use QR Code login ("Sign in on Mobile")

Navigation Menu

Repository navigation

ERROR 006 (Application Error): error running wizard: workspace not found. #725

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

ERROR 006 (Application Error): error running wizard: workspace not found. #725

Description

Activity

rusq commented on Aug 18, 2026

siliconpi commented on Aug 18, 2026

rusq commented on Aug 18, 2026

siliconpi commented on Aug 18, 2026

rusq commented on Aug 18, 2026

UnstoppableMango commented on Aug 18, 2026

siliconpi commented on Aug 19, 2026

rusq commented on Aug 19, 2026

rusq commented on Aug 19, 2026

sidholler commented on Aug 21, 2026

siliconpi commented on Aug 21, 2026

rusq commented on Aug 21, 2026

rusq commented on Aug 21, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions