Update BrinxAI Team has resolved the issue where the 1194/UDP Port was being reported by nmap as "open/filtered" but still showing as problematic on the Relay Node
1. Stop the current container process and delete:
sudo docker stop brinxai_relay && sudo docker rm brinxai_relay && sudo docker pull admier/brinxai_nodes-relay:latest
2. Check your CPU Architecture:
uname -m
➖ If the output is x86_64, your architecture is AMD64.
➖ If the output is aarch64 or arm64, your architecture is ARM64 (for Raspberry Pi or similar devices).
3. Once you know your architecture, use the appropriate command to run relay node:
➖ For AMD64:
sudo docker run -d --name brinxai_relay --cap-add=NET_ADMIN -p 1194:1194/udp admier/brinxai_nodes-relay:latest
➖For ARM64 (Raspberry Pi):
sudo docker run -d --name brinxai_relay --cap-add=NET_ADMIN -p 1194:1194/udp admier/brinxai_nodes-relay:arm64
If your Worker Node went down, restart the container:
docker restart brinxai_relay
1. Stop the current container process and delete:
sudo docker stop brinxai_relay && sudo docker rm brinxai_relay && sudo docker pull admier/brinxai_nodes-relay:latest
2. Check your CPU Architecture:
uname -m
➖ If the output is x86_64, your architecture is AMD64.
➖ If the output is aarch64 or arm64, your architecture is ARM64 (for Raspberry Pi or similar devices).
3. Once you know your architecture, use the appropriate command to run relay node:
➖ For AMD64:
sudo docker run -d --name brinxai_relay --cap-add=NET_ADMIN -p 1194:1194/udp admier/brinxai_nodes-relay:latest
➖For ARM64 (Raspberry Pi):
sudo docker run -d --name brinxai_relay --cap-add=NET_ADMIN -p 1194:1194/udp admier/brinxai_nodes-relay:arm64
If your Worker Node went down, restart the container:
docker restart brinxai_relay