Public Networking

“Public Networking” enables you to expose your service to the Internet.

Zeabur offers two methods for accessing your service:

• HTTP Services: Access your service using the domain name provided by Zeabur or your custom domain.
• Non-HTTP Services: Access your service using the assigned hostname and port.

Binding Your Domains

A domain is a unique identifier for your service, allowing it to be accessed from the Internet. For instance, the domain name of this website is zeabur.com.

To bind a domain to your service, navigate to your service in the Zeabur Dashboard and expand the Domains tab. You’ll have two options for creating a domain for your service.

Generate Domain

The “Generate Domain” option allows you to create a domain name with the zeabur.app suffix, such as your-service.zeabur.app, provided it is available. This is the simplest way to make your service publicly accessible.

Once your zeabur.app domain is set up, you can access your service using the domain name provided by Zeabur.

Custom Domain

To use your own domain name, select the “Custom Domain” option.

First, enter your domain name in the input box and click the “Create Domain” button.

After adding your domain name, you’ll see the DNS information for your domain.

You’ll need to manually configure the DNS records for your domain. For example, if you’re using Cloudflare, you can add the required record in the “DNS” → “Record” section using the configuration provided by Zeabur. If you use a different DNS provider, refer to their documentation for instructions on adding a CNAME record.

You can use Cloudflare’s CDN (orange cloud enabled) to reduce traffic costs and improve browsing speed. However, for Cloudflare SSL/TLS encryption mode, you cannot select Full (Strict), as it may cause connection failures due to self-signed certificates. Additionally, Cloudflare does not support SSL certificate issuance for custom domains beyond 3rd-level domains (i.e., *.example.com is supported, but *.sub.example.com is not). In this case, you can switch back to direct connection to Zeabur servers (orange cloud disabled).

After configuring the DNS record, it may take a few minutes for the changes to propagate. Once complete, you can access your service using your custom domain.

Root Domain DNS Settings

If you want to use a root domain (example.com) instead of a subdomain (www.example.com), also known as a Zone apex record, you may need to modify the DNS records provided by Zeabur.

If you’re using Cloudflare, you can skip this section since Cloudflare has built-in CNAME Flattening functionality that automatically converts CNAME records to A records that work with root domains.

If you’re using other DNS providers and Zeabur provides you with a CNAME record, you may need to convert the CNAME record provided by Zeabur to an A record.

1. When you bind your domain, Zeabur will give you a CNAME pointing to a hostname like hkg1.clusters.zeabur.com.

2. Then, open Google Admin Toolbox - Dig and enter this hostname.

   

   
   

3. You’ll see an IP address for an A record. Enter this IP address in your corresponding DNS field.

Please note that Zeabur may update the A record address that the CNAME points to. If you choose this setup method, you may need to help update this DNS record when we notify you of upcoming IP address changes or if the IP address changes for any reason.

Setting Up Redirections

To redirect your domain to another URL, use the “Redirect to another domain” feature. This will temporarily (307) redirect your domain to the specified target domain.

Deleting Domains

To delete a domain, click the trash bin icon next to the domain name.

Then, enter your domain name in the input box and click the “Delete” button to confirm.

Using the Assigned Hostname and Port

For non-HTTP services, you can access them via the assigned hostname and port, commonly referred to as “port forwarding.” For instance, if you have a Minecraft server running on port 25565, it can be accessed using the assigned hostname and port, such as hkg1.clusters.zeabur.com:34567.

While the hostname and port are generally consistent, there may be rare instances where they change. It’s advisable not to assume they are permanently fixed. You can also configure custom port forwarding within your service.

Port configuration

Git service

Git service only allows 1 port, which is the port you defined in the Dockerfile or 8080 if you does not specify it or are not deploying with Dockerfile. It is not recommended to write 8080 directly in your code, as the port may change in the future. Instead, you should use the $PORT environment variable.

Some code examples of using the $PORT environment variable:

const port = process.env.PORT || 8080;
 
app.listen(port, () => {
  console.log(`Server is running on port ${port}`);
});

package main
 
import (
    "fmt"
    "net/http"
    "os"
)
 
func main() {
    port := os.Getenv("PORT")
    if port == "" {
        port = "8080"
    }
 
    http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
        fmt.Fprintf(w, "Hello, World!")
    })
 
    http.ListenAndServe(":"+port, nil)
}

Docker services

You can set up the ports during the configuration of Docker service. Check the “Ports” section in the Docker configuration docs for details.