Payload container, X, of version Y is not supported

Payload container version not supported
mythic_container
PyPi package or the github.com/MythicMeta/MythicContainer
golang package. These packages keeps track of a version that syncs up with Mythic when the container starts. As Mythic gains new functionality or changes how things are done, these containers might not be supported anymore. At any given time, Mythic could support only a single version or a range of versions. A list of all PyPi reported versions and their corresponding Mythic version/DockerImage versions can be found here.
How do I fix this?
The agent in question needs to have its container updated or downgraded to be within the range specified by your version of Mythic. If you’re using a Dockerimage fromitsafeaturemythic
(i.e. in your Mythic/Payload_Types/[agent name]/Dockerfile
it says FROM itsafeaturemythic/something
) then you can look here to see which version you should change to.
C2 Profile’s internal server stopped

http's internal server stopped

mythic_admin stopped the c2 profile container
How do I fix this?
Go to the C2 Profiles page and click to “Start Internal Server”. If the container went down and is still down, then you won’t be able to start it from the UI and you’ll see a different button that you “Can’t Start Server”. If that’s the case, you need to track down why that container stopped on the host.Failed to correlate UUID, X, to something Mythic knows

Failed to correlate UUID
mythic: c2profile_name
. So, in this case we see 'mythic': 'http'
which means that the http
profile is forwarding this message along to the Mythic server.
How do I fix this?
First check if you have any agents that you forgot about from other engagements, tests, or deployments. The error message should tell you where they’re connecting from. If the UUID that Mythic shows isn’t actually a UUID format, then that means that some other data made its way to Mythic through a C2 profile. In that case, check your Firewall rules to see if there’s something getting through that shouldn’t be getting through. This kind of error does not impact the ability for your other agents to work (if they’re working successfully), but does naturally take resources away from the Mythic server (especially if you’re getting a lot of these).Exec user process caused: no such file or directory
If you are going back-and-forth between windows and linux doing edits on files, then you might accidentally end up with mixed line endings in your files. This typically manifests after an edit and when you restart the container, it goes into a reboot loop. The above error can be seen by usingsudo ./mythic-cli logs [agent name]
.
How do I fix this?
Runsudo ./mythic-cli logs [agent name]
to look at the output of the container. Usually you’ll see some sort of error here about why things aren’t working. This is typically the result of an agent/c2 profile being too far out of date from the rest of the Mythic instance that it can’t properly sync up anymore.