Network limitations
To ensure the security and stability of the infrastructure, we have implemented network‑level restrictions to prevent abuse.
We have defined a whitelist of ports and protocols that you can contact from your container. This allows us to block the use of KataBump for malicious purposes.
80
TCP
HTTP
✅
443
TCP
HTTPS
✅
8080
TCP
HTTP
✅
8443
TCP
HTTPS
✅
2333
TCP
Lavalink
✅
3306
TCP
MySQL/MariaDB
✅
27017:27020
TCP
MongoDB
✅
587
TCP
SMTP Relay
✅
5432
TCP
PostgreSQL
✅
6379
TCP
Redis
✅
9418
TCP
Git
✅
1935
TCP
RTMP
✅
465
TCP
SMTP Relay
✅
53
TCP+UDP
DNS
✅
3000
TCP
Lavalink Alt
❌
8999
TCP
Lavalink Alt
❌
5000
TCP
Lavalink Alt
❌
13592
TCP
Lavalink Alt
❌
4006
TCP
Lavalink Alt
❌
8893
TCP
Lavalink Alt
❌
2334
TCP
Lavalink Alt
❌
24597
TCP
Lavalink Alt
❌
1026
TCP
Lavalink Alt
❌
7106
TCP
Lavalink Alt
❌
*If the node switches to reinforced network mode, ports marked with ✅ will still be reachable, while those marked with ❌ will temporarily become unreachable. This happens, for example, in the event of a network flood coming from outside.
The internal IP addresses on the KataBump network can be contacted on all of their ports to enable inter‑container communication.
Last updated