Engines added in cli not visible in UI #302
Comments
|
@kenanfarukcakir @kursataktas can you pls take a look, I am also facing this issue |
|
Hi, it looks like the hammer version shown in the UI is outdated. We will fix it in the next release. For now, you can use version |
|
Used hammer 2.0.0 only. But still added engines not visible in UI. |
|
@Allaps, can you send the logs for the new hammer? docker logs anteon_hammer_1 |
FATA[0058] joblistener_init_failed app=hammer ddosifyenv=onprem error_reason="dial tcp: lookup rabbitmq-job on 127.0.0.11:53: server misbehaving" id=36307023-3973-46c6-9548-3d063747545c ip=127.0.0.1 |
|
It looks like you use the old version of the Anteon Platform. Can you install it again with the new version? https://github.com/getanteon/anteon/tree/master/selfhosted#%EF%B8%8F-quick-start-docker-compose |
Installed new version. But UI not loading and throws error.
|
|
@fatihbaltaci For me, the dashboard page it self not loading |
|
Can you send the logs of Anteon? cd $HOME/.anteon/selfhosted
docker compose logs |
|
Attached Anteon docker compose logs. |
|
Could you try with these commands? It will remove the old Anteon Platform and install the new one. cd $HOME/.anteon/selfhosted
docker compose down --volumes
curl -sSL https://raw.githubusercontent.com/getanteon/anteon/master/selfhosted/install.sh | bash |
Hi @fatihbaltaci |
|
Glad to hear that. Please let me know if you need assistance |
Describe the bug
Engines added in cli not visible in UI. Added 2 engines from cli, but not visible in UI.
To Reproduce
Steps to reproduce the behavior:
NAME=anteon_hammer_1 docker run --name $NAME -dit --network anteon --restart always ddosify/selfhosted_hammer:1.4.3
Expected behavior
Added anteon_hammer_2, anteon_hammer_3 should be seen in UI, but not visible.
Screenshots
Screenshots attached.
System (please complete the following information):
Additional context
Anteon Community edition.
The text was updated successfully, but these errors were encountered: