Unknown shorthand flag: 'u'

[PiCarODD]

Hello, i got this error for a long time gobuster -u https://target.com -w wordlist.txt Error: unknown shorthand flag: 'u' in -u

[firefart]

Which version of gobuster are you using? The CLI Interface changed a lot with v3 so there is a new syntax. If you are still on v2, please upgrade to v3

[PiCarODD]

apt-get install gobuster Reading package lists... Done Building dependency tree
Reading state information... Done gobuster is already the newest version (3.0.1-0kali1). 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.

[firefart]

Then you need to use the new syntax. gobuster dir .....

You can also run gobuster help for help

[EricoCartmanez]

Really bad help. gobuster dir http://10.10.103.219 -w /usr/share/wordlists/dirb/common.txt Error: required flag(s) "url" not set

flag "url" is required but not mentioned anywhere in help.

So after experimenting, found out this is the correct syntax: gobuster dir -u http://x.x.x.x -w /path/to/wordlist

[OJ]

The help is baked in, if you follow the instructions.

C:\Users\oj> gobuster dir http://127.0.0.1
Error: required flag(s) "url", "wordlist" not set
C:\Users\oj> gobuster help
Usage:
  gobuster [command]

Available Commands:
  dir         Uses directory/file brutceforcing mode
  dns         Uses DNS subdomain bruteforcing mode
  help        Help about any command
  vhost       Uses VHOST bruteforcing mode

Flags:
      --delay duration    Time each thread waits between requests (e.g. 1500ms)
  -h, --help              help for gobuster
  -z, --noprogress        Don't display progress
  -o, --output string     Output file to write results to (defaults to stdout)
  -q, --quiet             Don't print the banner and other noise
  -t, --threads int       Number of concurrent threads (default 10)
  -v, --verbose           Verbose output (errors)
  -w, --wordlist string   Path to the wordlist

Use "gobuster [command] --help" for more information about a command.

C:\Users\oj> gobuster dir --help
Uses directory/file brutceforcing mode

Usage:
  gobuster dir [flags]

Flags:
  -f, --addslash                      Append / to each request
  -c, --cookies string                Cookies to use for the requests
  -e, --expanded                      Expanded mode, print full URLs
  -x, --extensions string             File extension(s) to search for
  -r, --followredirect                Follow redirects
  -H, --headers stringArray           Specify HTTP headers, -H 'Header1: val1' -H 'Header2: val2'
  -h, --help                          help for dir
  -l, --includelength                 Include the length of the body in the output
  -k, --insecuressl                   Skip SSL certificate verification
  -n, --nostatus                      Don't print status codes
  -P, --password string               Password for Basic Auth
  -p, --proxy string                  Proxy to use for requests [http(s)://host:port]
  -s, --statuscodes string            Positive status codes (will be overwritten with statuscodesblacklist if set) (default "200,204,301,302,307,401,403")
  -b, --statuscodesblacklist string   Negative status codes (will override statuscodes if set)
      --timeout duration              HTTP Timeout (default 10s)
  -u, --url string                    The target URL            <------------- Right here.
  -a, --useragent string              Set the User-Agent string (default "gobuster/3.0.1")
  -U, --username string               Username for Basic Auth
      --wildcard                      Force continued operation when wildcard found

Global Flags:
      --delay duration    Time each thread waits between requests (e.g. 1500ms)
  -z, --noprogress        Don't display progress
  -o, --output string     Output file to write results to (defaults to stdout)
  -q, --quiet             Don't print the banner and other noise
  -t, --threads int       Number of concurrent threads (default 10)
  -v, --verbose           Verbose output (errors)
  -w, --wordlist string   Path to the wordlist

It's also in the README at the very repository you've submitted this issue to:

I'm sorry, but it's definitely not an issue with the documentation or the built-in help. It's there for anyone who looks.