Skip to main content

Documentation Index

Fetch the complete documentation index at: https://wiki.daki.cc/llms.txt

Use this file to discover all available pages before exploring further.

Network access works differently depending on whether you are on the Free Tier or a paid plan. This page explains how ports and allocations work and what you can expect in each case.

What you’ll learn

  • The difference in network access between Free Tier and paid plans
  • What an allocation is
  • How to view your hostname and port
  • How to add allocations on paid plans

Free Tier: No Public Ports

Free Tier servers do not have publicly accessible ports. Inbound connections from outside the server are not supported on the Free Tier. This means:
  • Your application cannot receive external HTTP requests or WebSocket connections.
  • Web servers, APIs, and webhook endpoints will not be reachable from the internet.
  • Discord bots are not affected — they connect outbound to Discord and do not need an inbound port.
If your application needs to be reachable from outside (e.g., a web API, a game server, or a bot with webhook-based interactions), you will need a paid plan.
All paid plans (Bronze, Silver, Gold, and game server plans) include at least one publicly accessible port allocation. This allows your application to accept inbound connections from anywhere. Each paid server is assigned a hostname and a port, both visible in the Network tab of the Portal. Example:
  • Hostname: eu-node1.daki.cc
  • Port: 25565
  • Full address: eu-node1.daki.cc:25565
Your application must listen on the assigned port to be reachable from outside.

What Is an Allocation?

An allocation is a hostname + port pair assigned to your server. It represents one publicly accessible network endpoint. Paid servers start with one allocation by default.

Adding Allocations (Paid Plans Only)

On paid plans, you can add additional port allocations from the Network tab in the Portal. This is useful when your application needs to listen on more than one port at the same time — for example, a game server with a query port alongside its main port.

Frequently Asked Questions

Your application must listen on the exact port shown in the Network tab. Listening on any other port will make your application unreachable from outside. Some eggs provide this value as an environment variable (e.g., PORT or SERVER_PORT) that you can read in your code.
Discord bots establish an outbound connection to Discord’s servers (via WebSocket). They do not need an inbound port to function, which is why they work on the Free Tier. If your bot also runs an HTTP server (e.g., for slash command interactions or a web dashboard), you will need a paid plan for that component to be accessible.
Daki uses shared IPs across its nodes. For static IP or custom domain options, contact support via the Billing Panel or Discord.
Verify that your application is listening on the correct port (check the Network tab). Also confirm the server is running and the application has fully started. If the issue persists, contact support.

Next Steps