search

nesfit / fitcrack

A hashcat-based distributed password cracking system
https://fitcrack.fit.vutbr.cz/
Other
143 stars 30 forks source link

(Docker) server monitoring not working on port other than default 5000 #111

Open lukaszzyla opened 11 months ago

lukaszzyla commented 11 months ago

I had trials and errors when trying to set up docker. In the beginning of installation trials I did have server monitoring available - I could see nice pie graphs in dashboard and performance graphs in monitoring. I have made some changes during trials but have already came back to almost original github package now (just changed portsto 7000 and 7080). I think it might have something to do with ports - anyone having this issues? edit... I have just double checked with multiple docker compose configs and I have noticed that whenever BACKEND port is being changed from default 5000 - server monitoring is lost...

alpatron commented 11 months ago

I can confirm that when I change the ports in the manual installer, then I can see the graphs just fine.

obrazek obrazek

So it might be some weird Docker thing.

Just to confirm, are you talking about the screens shown? And other than that, is anything else broken? If it's an issue with port configuration, I'd think more stuff would be broken. @lukaszzyla

lukaszzyla commented 11 months ago

yes. I mean exactly those graphs. I just double checked:

  1. stopped stack. removed all volumes. started up stack with BACKEND_PORT changed to 7000 - everything start well but server monitoring is greyed out and not active. image Also the monitoring page shows all services running in green but no graphs.

    image

  2. same case scenario, but this time with default BACKEND_PORT=5000. I did remove volumes and started from scratch with the container. settings:

    image

This time everything works fine:

image

So it seems to be happening on my system which is ubuntu 22.04 LTS up to date with docker/portainer. I can confirm, that the behaviour is caused by changing BACKEND_PORT .env value to other than 5000. webadmin port can be changed and container works as expected.

lukaszzyla commented 11 months ago

and maybe, just maybe - this issue is connected to issue #77 . It has something to do with the way the communication between backend and frontend is done? Sorry I am no coder so can't help much with solving it - this is just something that came to my mind.