My Mythic C2 not connecting after installation

[maxwellgolden]

HELLO,

I've been having constant issues connecting with Mythic c2.

please how can i fix it

[its-a-feature]

can you share a bit more of what's happening at the top of that output? It looks as though there's an issue with docker on your Kali instance.

[maxwellgolden]

here it is.

[maxwellgolden]

tried fixing it for the past two days but to no avail.

[its-a-feature]

so right at the top it says compose is not a docker command, which means you don't have docker compose installed on the system. It seems like Kali did something recently that broke their installation of Docker and Docker compose (I've seen a bunch of errors with docker-compose and a bunch of people unable to to install the compose plugin on Kali. Somebody from the bloodhound slack suggested this worked for them:

curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
chmod a+x /usr/local/bin/docker-compose
apt-get install docker.io

So you can give that a try?

[maxwellgolden]

Alright thanks.

[maxwellgolden]

Hello, the issue still persist

[adityabaronia]

Give more than 1 core to your VM. This will remove the error for Creating mythic_graphql mythic_postgres, mythic_server and mythiv_rabbitmq.

[maxwellgolden]

Ok

[its-a-feature]

in your Mythic/.env file you'll see a lot of options to configure how Mythic runs. By default, Mythic (using docker compose) allocates 1VCPU to installed services (agents, c2 profiles, etc) and 2VCPU to Mythic's core functionality. This is configurable in the .env file though if you look for the settings with _cpus. You can set all the 2s to 1s and then run sudo ./mythic-cli start again. The performance might just be a bit worse as you only have one cpu to share for everything.

[maxwellgolden]

rabbitmq isnt connecting.

[its-a-feature]

can you share the output of sudo ./mythic-cli logs mythic_server and sudo ./mythic-cli status?

[its-a-feature]

If you're still having this issue, we can reopen and see what's going on, but since I haven't heard from you in a while I'm going to close this one