Network
Network Overview
Understanding network configuration and the layered entry architecture for your Cafora Minecraft server.
Network configuration is essential for making your Minecraft server accessible to players. Cafora handles the infrastructure layer, but you control how players connect.
Key Concepts
| Concept | Description |
|---|---|
| Server IP | The address players use to connect |
| Port | The network port your server listens on |
| DNS | Domain name resolution for custom domains |
| Ping | Network latency measurement |
| DDoS Protection | Entry-point scrubbing layer provided by TCPShield Sentry |
Layered Entry Points
Cafora splits entry points by traffic plane, so different types of connections take different paths:
| Traffic plane | Entry point | Address |
|---|---|---|
| Minecraft game | TCPShield Sentry | <server-type>.play.caforahost.com, ports 25565–25577 |
| SFTP file transfer | TCPShield Sentry | sftp.caforahost.com:2022 |
| Panel / API | Cloudflare Tunnel | panel.caforahost.com, node.caforahost.com |
This means:
- Players connect with the standard hostname and never need to care which entry point is behind it
- File transfers use a dedicated SFTP hostname
- The origin IP does not serve Minecraft or SFTP directly
You do not need to configure anything for these layered entry points — Cafora handles it at the infrastructure layer. See DDoS Protection.
In This Section
- Server IP — the difference between the entry IP and the origin IP
- Ports — the protected port range
- DNS — custom domains and SRV records
- Ping — latency measurement and tuning
- Connection Troubleshooting