UI reachable directly after compose up -d but stops working fast

[YumYumTuete]

Hello,

i am using docker compose to run rigour on a pretty beefy local machine (Ryzen 7600x, 32GB DDR5-6000) on CachyOS. This is meant to be only testing on my machine and will move to another host later on maybe. Everything is up to date, i cloned the latest github main branch code and edited the .env file to include my MaxMind Account.

As soon as i start the stack using docker compose up -d i am able to visit the web interface and i do have scanned entries in the database. But only a moment later the webui is no longer reachable and stops working. At the same time i do have some major internet problems with massive slow downs and timeouts on the host machine itself. sometimes i do get a fetch error on the web interface, sometimes it just completely stops working.

do you have any idea what causes this issue? for me it looks like a major issue with the scan rate of the crawler maybe and my host network is just completely ddosing itself. But tbh it could be everything as i dont exactly understand every bit of the microservice chain that is done here.

EDIT:
It ssems to be a network capacity problem as the running container is producing massive high pings on the host machine.
Here is an output of a ping test to 8.8.8.8 while stopping the stack in the middle:
64 Bytes von 8.8.8.8: icmp_seq=12 ttl=119 Zeit=380 ms
64 Bytes von 8.8.8.8: icmp_seq=18 ttl=119 Zeit=456 ms
64 Bytes von 8.8.8.8: icmp_seq=20 ttl=119 Zeit=385 ms
64 Bytes von 8.8.8.8: icmp_seq=21 ttl=119 Zeit=344 ms
64 Bytes von 8.8.8.8: icmp_seq=27 ttl=119 Zeit=462 ms
64 Bytes von 8.8.8.8: icmp_seq=29 ttl=119 Zeit=340 ms
64 Bytes von 8.8.8.8: icmp_seq=30 ttl=119 Zeit=346 ms
64 Bytes von 8.8.8.8: icmp_seq=31 ttl=119 Zeit=337 ms
64 Bytes von 8.8.8.8: icmp_seq=32 ttl=119 Zeit=383 ms
64 Bytes von 8.8.8.8: icmp_seq=35 ttl=119 Zeit=325 ms
64 Bytes von 8.8.8.8: icmp_seq=36 ttl=119 Zeit=356 ms
64 Bytes von 8.8.8.8: icmp_seq=37 ttl=119 Zeit=10.9 ms
64 Bytes von 8.8.8.8: icmp_seq=38 ttl=119 Zeit=11.1 ms
64 Bytes von 8.8.8.8: icmp_seq=39 ttl=119 Zeit=10.9 ms
64 Bytes von 8.8.8.8: icmp_seq=40 ttl=119 Zeit=11.0 ms
64 Bytes von 8.8.8.8: icmp_seq=41 ttl=119 Zeit=11.2 ms
64 Bytes von 8.8.8.8: icmp_seq=42 ttl=119 Zeit=10.7 ms
64 Bytes von 8.8.8.8: icmp_seq=43 ttl=119 Zeit=11.0 ms
64 Bytes von 8.8.8.8: icmp_seq=44 ttl=119 Zeit=11.0 ms
64 Bytes von 8.8.8.8: icmp_seq=45 ttl=119 Zeit=11.0 ms
64 Bytes von 8.8.8.8: icmp_seq=46 ttl=119 Zeit=11.1 ms

[YumYumTuete]

Problem found!
Connstack is filling up fast and fills completely, so my network capacity simply cant hold the scan rate.
is there an option to limit the scan rate?

cat /proc/sys/net/netfilter/nf_conntrack_count
262143
cat /proc/sys/net/netfilter/nf_conntrack_max
262144

[YumYumTuete]

I now changed the network completely and switched every microservice to its own ip address in a special macvlan for rigour (and added my host to that network too to reach the webui) to reduce the traffic through the docker host bridge. Logs look good, everything is communicating and the web ui loads fine ... for a few seconds and then stops working again.