Discussions

Ask a Question

Attack box error

~/cobaltstrike> sudo ./teamserver 10.10.5.50 Passw0rd! c2-profiles/normal/webbug.profile I get error message stating user has no access.

Payloads are not generating

I have repeated the same steps well enough that they haunt my sleep. At this point I am almost quite literally repeating the instructional material in my sleep. I've revisited the payload generation step where all stageless payloads are generated, yet REGARDLESS OF WHAT DIRECTORY I select ... nothing seems to work. The Cobalt Strike application is perfectly happy LYING TO ME about it's successful action. I've repeated these steps, rebooted the VMs, reverted back to snapshot and yet it still haunts like a RAVEN....EVERMORE. Please help, my poor lab hours have suffered enough.

unauthorized error message - cannot control my lab

taking my exam now and cannot continue.

not authorized error message

When I attempt to start my labs, I get a "not authorized" pop-up message. Has anyone encountered this problem before?

WiFi problem

Can I use internet in Kali Linux computer No in virtual box please tell me

Lab limit

Why is the lab limit set to 2 ranges?

Cannot create Macros or access Word > Options

I can't create Macros ( previously I was able to) and can't access the Word/Excel Options tab as it is all greyed out. I believe it might be something to do with the application not being registered or out of its trial period. How do I fix that please?

We couldn't power off those instances right now because some are already busy.

Hi, One of the systems in my lab is tuck on "storing" and can't be completely shutdown, reverted or re-started. It just gives the following error: `We couldn't power off those instances right now because some are already busy.` Any ideas on how to resolve?

How to change registered E-mail ID?

Kindly guide how to change the registered E-mail ID of the Cyber Ranges account. This is so as the currently registered E-mail does not exist any further.

Starting Lab is stuck at: "We couldn't power on those instances right now because some are already busy."

After a few days away from the lab, it won't start anymore. It always failing with: `We couldn't power on those instances right now because some are already busy.` This comes from a single machine in the Lab, starting the others one by one does work. Also reverting the complete lab or the single machine does not work, failing with a similiar message. `We couldn't revert those instances right now because some are already busy.`