Forum

Same question, this variable is very strange:

It is auto-generated—implying that:

1. WEB_PORT is a system-generated value
2. It should not be modified

However:

1. WEB_PORT cannot be found among any of the auto-generated variables
2. It can clearly be modified manually

Conclusion: 100% contradictory in every way.

I hope the official team can provide an explanation! Thank you.

Hello, that's a great question. Let me explain the actual mechanism of WEB_PORT:

WEB_PORT is a "System Variable," not an "Auto-generated value" — these are two different concepts:

So, it is correct that you see "WEB_PORT is not in the auto-generated variable list" — it does not belong to that category; it belongs to "System Variables," and the relationship is as follows:

${WEB_PORT} = The actual port number of the web port in your service's Networking page

For example, if you set a port ID as web and a port number as 8080 on the Networking page, then ${WEB_PORT} will be expanded to 8080. If you change it to 3000, ${WEB_PORT} will become 3000.

Why does it say "Auto-generated, should not be modified"?

This prompt is indeed a bit ambiguous. What it intends to convey is: "This value is derived from your Networking settings. Please go to the Networking page to change the port number, do not modify the value of this variable directly." Although the UI allows you to change WEB_PORT=xxxx directly in the variable field:

• ✅ It will override the system-derived value (it can indeed be modified).
• ❌ However, Zeabur's ingress routing will still point to the port set in your Networking configuration. Therefore, if your application is actually listening on the port you manually changed, but the ingress is still routing to the port set in Networking, it will not be reachable.

Correct approach:

1. Use process.env.PORT (or the equivalent env reading method for your language) in your application code, and inject the system's WEB_PORT using PORT=${WEB_PORT} (many official templates are written this way).
2. If you want to change the port number, please go to the Networking page to change the port settings, rather than modifying the WEB_PORT variable itself.

For more system variables, please refer to the official documentation: Environment Variables — Special Variables

I hope this clarifies the confusion! If you have any further questions, feel free to reply.

Hello! You don't need to set it manually; the "system-generated port" you see is the web port — ${WEB_PORT} will automatically map to it. Let me explain why:

Zeabur's Automatic Port Naming Rules

According to Zeabur's official documentation:

For services deployed from Git repositories, the PORTNAME is always web.

In other words, for services deployed from Git (GitHub / GitLab, etc.), the automatically generated port has a fixed internal ID of web. Even if the UI doesn't explicitly display "ID: web", it is called web at the underlying level.

Therefore:

• ${WEB_PORT} → Expands to "the port number of that automatically generated port" (e.g., 8080, 3000, etc.)
• ${ZEABUR_WEB_URL} → Maps to the public URL of this port
• ${ZEABUR_WEB_DOMAIN} → Maps to the domain of this port

You absolutely do not need to add an extra "ID=web" port on the Networking page — it already exists; the UI just doesn't explicitly show the ID field.

When would there be ports with different IDs?

Only when you manually add multiple ports (e.g., opening a TCP port for PostgreSQL 5432 or Redis 6379 in addition to web), or when using Marketplace templates (e.g., the PostgreSQL template has multiple built-in ports), will the UI show multiple items, each with its own ID:

For your scenario of a single Git web service, the system only generates one port, and the ID is web, so there is no ambiguity.

Verification Method

If you want to be 100% sure, you can add a test variable on the Variables page of your service:

TEST_WEB_PORT=${WEB_PORT}

Then restart the service and run echo $TEST_WEB_PORT inside the container. You will see it expand to the specific port number (e.g., 8080), confirming that ${WEB_PORT} is correctly mapped to that automatic port in Networking.

Summary

• ✅ No manual configuration needed — the system-generated port is web
• ✅ ${WEB_PORT} will automatically expand to that port number
• ✅ The UI not showing the ID is just a presentation issue, not a lack of ID

I hope this clears up your concerns! If you actually encounter a situation where ${WEB_PORT} is not expanding to the expected value (e.g., you cannot connect), please reply and let me know the specific situation so we can investigate further.