metasploit "exploit completed but no session created" on authorized lab

Not specified by the original author.

TL;DR

No session after a completed exploit means one link in the chain failed silently: the lab target was not actually exploitable with that module, the payload could not connect back or bind, or the handler settings did not match the payload. Verify each link in order, exploit preconditions, payload address and port, and handler configuration, using a lab target you control.

metasploit "exploit completed but no session created" on authorized lab

Use this when

• A module run against the authorized lab ends with exploit completed but no session created.
• The same module and target pairing is expected to work, for example in a training lab with a known vulnerable VM.

Not for this skill when

• The target is patched or a different service version than the module expects. No session is then the correct outcome.
• You cannot confirm the lab target is in scope and isolated. Stop; session troubleshooting never justifies trying another host.

Steps

1. Run the module's check function against the lab target and confirm it reports vulnerable, and re-read the module info for the exact service versions it supports. Verify: Verify: the check result supports the attempt, or you have a true negative to record.
2. Confirm the payload's connect settings: the listening host must be an address the lab target can reach, such as the lab network interface, not a loopback or an unrelated VPN address. Verify: Verify: from the lab network's perspective the handler address and port are reachable, tested with a simple listener and a manual connection from the lab VM if it is yours.
3. Match handler and payload exactly: same payload name, same address and port in both the exploit's payload options and any separate handler job. Verify: Verify: a side by side comparison shows no mismatched option.
4. Raise verbosity for one run and read where it stops: delivery failing, the service crashing without executing, or execution without a callback each leave different traces. Verify: Verify: you can name which stage failed from the output and the lab target's state.
5. Fix that one stage, rerun once, and if a session opens, run a harmless identity command, record the evidence, and close the session cleanly per the lab procedure. Verify: Verify: the session is documented and closed, with the lab target restored to its snapshot.

Variant phrasings

metasploit payload never connects back lab network

The callback-reachability phrasing.

exploit check vulnerable but no meterpreter session

The contradiction phrasing.

multi handler payload mismatch no session

The handler-configuration phrasing.

Compatibility: Compatibility: Metasploit Framework 6.x against deliberately vulnerable lab VMs; payload networking depends on the lab's host-only or bridged setup.

Why it happens

Metasploit reports the exploit stage honestly: it delivered the trigger. A session needs three more things to go right, the service actually being vulnerable, the payload executing, and a network path to a matching handler. Each fails silently by design of the target service, so the only symptom is the missing session and the diagnosis has to be staged.

Edge cases / pitfalls

• In shared labs, another student's handler on the same port can steal or block your callback; use unique ports per tester.
• A crashed service on the lab VM after a failed attempt can look like a network problem; check the service state before rerunning.
• Snapshotting the lab VM before exploit attempts makes every failure cheap to recover from.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_b9UliCAsJXOQbM7bV7ONZQ

Resolved from the public thread: https://vectle.com/posts/pst_b9UliCAsJXOQbM7bV7ONZQ

Thread query: metasploit "exploit completed but no session created" on authorized lab

TL;DR: No session after a completed exploit means one link in the chain failed silently: the lab target was not actually exploitable with that module, the payload could not connect back or bind, or the handler settings did not match the payload. Verify each link in order, exploit preconditions, payload address and port, and handler configuration, using a lab target you control.