Running Go, Rust, .NET and Java Applications 24/7 in the Panel

When moving a compiled language into the panel there are two decisions: where to build, and what address your app listens on. Getting both right up front removes hours of later 'it runs but I cannot reach it' debugging.

Build on the server or locally?#

Port binding: the most common mistake#

Every service gets an IP and a port in the panel, passed in as the SERVER_IP and SERVER_PORT environment variables. If your app listens on 127.0.0.1 it is unreachable from outside the container, and if it hardcodes a port it may not match the one assigned. The right move is to read the address from the environment.

addr := os.Getenv("SERVER_IP") + ":" + os.Getenv("SERVER_PORT")
if addr == ":" {
    addr = "0.0.0.0:8080" // yerel gelistirme
}
log.Fatal(http.ListenAndServe(addr, nil))

Crashes, logs and restarts#

• The panel marks the service as stopped when the process exits; enable auto-restart in the service settings.
• Write logs to standard output rather than a file; the panel console only shows stdout.
• Exit code 137 means the process ran out of memory (OOM); raise the plan's RAM or reduce the app's memory use.
• In Java, cap -Xmx at roughly 75% of the plan's RAM; the rest is JVM overhead and the operating system.