kgretzky/evilginx2 · error

get-url: no export path specified

Error message

get-url: no export path specified

What it means

In 'lures get-url <id> import <file> export', an export destination file path is required but was not supplied (only 5 args). Argument-count validation guard in handleLures before exportPhishUrls runs.

Source

Thrown at core/terminal.go:787

				var out string

				params := url.Values{}
				if pn > 2 {
					if args[2] == "import" {
						if pn < 4 {
							return fmt.Errorf("get-url: no import path specified")
						}
						params_file := args[3]

						phish_urls, phish_params, err = t.importParamsFromFile(base_url, params_file)
						if err != nil {
							return fmt.Errorf("get_url: %v", err)
						}

						if pn >= 5 {
							if args[4] == "export" {
								if pn == 5 {
									return fmt.Errorf("get-url: no export path specified")
								}
								export_path := args[5]

								format := "text"
								if pn == 7 {
									format = args[6]
								}

								err = t.exportPhishUrls(export_path, phish_urls, phish_params, format)
								if err != nil {
									return fmt.Errorf("get-url: %v", err)
								}
								out = hiblue.Sprintf("exported %d phishing urls to file: %s\n", len(phish_urls), export_path)
								phish_urls = []string{}
							} else {
								return fmt.Errorf("get-url: expected 'export': %s", args[4])
							}
						}

View on GitHub (pinned to 4c0988a1d9)

Solutions

1. Re-run with an output path: lures get-url <id> import <params_file> export <output_file>.
2. Optionally append a format argument (e.g. text or json) as the last token.
3. Check 'help lures' for the full get-url syntax.

When it happens

Trigger: Thrown at core/terminal.go:787 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of kgretzky/evilginx2@4c0988a1d9 (2026-09-05). Data as JSON: /api/errors/bae27f42db091f8f. Report an issue: GitHub.