-
Hi *, When I type on UTMStackServer: "ss -ltn" it is shown that on ports 9000 and 50051 is "LISTEN" :
Is there any problem with default installation or with 10.0.0.x address ranges (or internal routing in Ubuntu)? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
Here is output of lsof -nP -i:
and iptables -L :
and nmap -p- 10.0.0.21 (from Ubuntu console):
|
Beta Was this translation helpful? Give feedback.
-
I can confirm findings from #370 that docker uses networks 10.0.0.0/24 (ingress) and 10.0.1.0/24 (utmstack_default) Does that means, that I can not use UTMStack in our network where we use these address ranges? Does is it somewhere documented? |
Beta Was this translation helpful? Give feedback.
-
Im also having the same issue. Confirmed ports 9000, 50051 and 5044 are open for TCP and UDP on my windows machine and linux, but still receive the same error as above. I was able to install the linux agent on the UTMStack server without issue. I have no weird rules or network setup either. I have a Windows Server 2019 and Wazuh server running without issue and didnt have to open any ports. UTMstack server IP is 10.0.0.14, and have all ports open and specific IPs whitelisted as well all using ufw. The product seems very well done and thorough, but these silly networking issues are a real down fall. It took us hours just to get networking fixed after setting it up on a clean ubuntu image, with the premade iso not working correctly either. :/ |
Beta Was this translation helpful? Give feedback.
-
This is the sequence of steps (for changing IP addresses of docker networks) that solved the problem for me: 1.) sudo su 2.) docker stack ls (outputs: utmstack 17 services) 3.) docker stack rm utmstack (outputs: "Removing service ..." + "Removing network utmstack_default") 4.) nano /etc/docker/daemon.json with content: 5.) service docker restart 7.) nano /etc/netplan/99-vlan.yaml change "addresses" to [172.16.254.33/24] 9.) sudo su 11.) docker swarm leave --force (outputs: "Node left the swarm.") 14.) docker network rm ingress 17.) docker stack deploy -c compose.yml utmstack (outputs: "Creating network utmstack_default" + "Creating service ...") |
Beta Was this translation helpful? Give feedback.
-
I could not get this solution to work. I suspect the issue was related to the network the server was installed on is using vlan id 10. Changing the vlan id from step 7 to something else and re-running through the rest of the steps did not correct the issue. Port 9000 was still not showing as listening when running "ss -ltn". I performed a clean re-install of ubuntu 24.04 and performed the install using the latest release and following the rest of the official documentation. I used the following to get the latest installer: I was able to add the Windows agents without any issue with this latest release. |
Beta Was this translation helpful? Give feedback.
This is the sequence of steps (for changing IP addresses of docker networks) that solved the problem for me:
(type in terminal on UTMStackServer)
1.) sudo su
2.) docker stack ls (outputs: utmstack 17 services)
3.) docker stack rm utmstack (outputs: "Removing service ..." + "Removing network utmstack_default")
4.) nano /etc/docker/daemon.json with content:
{
"default-address-pools": [
{"base":"172.17.0.0/16","size":16}
]
}
5.) service docker restart
6.) docker info (check "Default Address Pools: Base: 172.17.0.0/16, Size: 16")
7.) nano /etc/netplan/99-vlan.yaml change "addresses" to [172.16.254.33/24]
8.) reboot
9.) sudo su
10.) ip a show (check "docker0": inet 172.17.0.1/16 and "vlan10@en…