The Startup page allows you to configure how your server starts, including Java arguments, memory allocation, and game-specific launch parameters.
Understanding Startup Variables
Server Variables
Docker Image
View Current Variables
Navigate to the Startup tab to see all configured variables
Common Variables
SERVER_JARFILE
string
default:"server.jar"
The server executable file name
Minecraft version to use (for vanilla servers)
Complete startup command with all arguments
Maximum memory allocation in MB
Modify Variables
Click on any variable field to edit its valueChanges to startup variables require a server restart to take effect
Check Current Image
View the Docker image and version your server is using
Available Images
Common images include:
minecraft/java - Standard Java Minecraftminecraft/bedrock - Bedrock Editionsource/srcds - Source gamesnodejs - Node.js applications
Update Image
Contact support if you need to change the base Docker imageChanging Docker images may require server reconfiguration
Memory Configuration
Determine Memory Needs
Calculate memory requirements based on:Player Count
- 1-10 players: 1-2GB
- 10-50 players: 2-4GB
- 50+ players: 4GB+
Modifications
- Vanilla: Base memory
- Light mods: +25%
- Heavy modpacks: +50-100%
Set Memory Allocation
Update the memory variables: Verify Allocation
Check the startup command includes correct memory flags:java -Xms128M -Xmx{{MEMORY_LIMIT}}M -jar {{SERVER_JARFILE}}
Java Arguments Optimization
Basic Arguments
Performance Tuning
Game-Specific
-Xms128M -Xmx{{MEMORY_LIMIT}}M
-XX:+UseG1GC
-XX:+ParallelRefProcEnabled
-XX:MaxGCPauseMillis=200
-XX:+UseG1GC
-XX:G1HeapRegionSize=8M
-XX:MaxGCPauseMillis=200
-XX:+AlwaysPreTouch
-XX:+DisableExplicitGC
-XX:G1NewSizePercent=30
-XX:+UseG1GC
-XX:+ParallelRefProcEnabled
-XX:MaxGCPauseMillis=200
-XX:+UnlockExperimentalVMOptions
-XX:G1NewSizePercent=20
-XX:G1ReservePercent=20
-XX:MaxDirectMemorySize=1G
Game-Specific Startup Options
Minecraft Java
Minecraft Bedrock
Other Games
Server Type Configuration
SERVER_JARFILE: server.jar
VANILLA_VERSION: 1.20.4
Additional Arguments
-Dfile.encoding=UTF-8
-Djline.terminal=jline.UnsupportedTerminal
-Dlog4j2.formatMsgNoLookups=true
Server Configuration
BEDROCK_VERSION: latest
LD_LIBRARY_PATH: .
Permission Level
PERMISSION: member
# Options: visitor, member, operator
PLAYERS: 32
PORT: 8211
QUERY_PORT: 27015
COMMUNITY: false
SERVER_NAME: My Valheim Server
WORLD_NAME: Dedicated
PASSWORD: mypassword
HOSTNAME: My Rust Server
SEED: 12345
WORLDSIZE: 3000
MAXPLAYERS: 100
Advanced Configuration
Environment Variables
Add Custom Variables
You can add custom environment variables for specific needs:TZ=America/New_York (Set timezone)
LANG=en_US.UTF-8 (Set language)
JAVA_TOOL_OPTIONS=-Duser.timezone=UTC
Reference Variables
Use variables in your startup command:java -Xmx{{MEMORY_LIMIT}}M -jar {{SERVER_JARFILE}} --port {{SERVER_PORT}}
Startup Command Customization
Command Structure
Custom Commands
java [JVM_ARGS] -jar [SERVER_JAR] [GAME_ARGS]
Java Virtual Machine arguments (memory, garbage collection)
Path to the server executable file
Game-specific startup arguments
Backup Original
Always save the original startup command before modifications
Test Changes
Start your server after changes to ensure it boots correctly
Monitor Performance
Watch server performance after startup modifications
Troubleshooting Startup Issues
Common Causes:
- Invalid Java arguments
- Insufficient memory allocation
- Missing or corrupted server files
- Port conflicts
Solutions:
- Reset to default startup command
- Check server logs for error messages
- Verify file permissions
- Contact support if issues persist
Error Messages:
- OutOfMemoryError
- GC overhead limit exceeded
Solutions:
- Increase
MEMORY_LIMIT variable
- Optimize server plugins/mods
- Use memory-efficient Java flags
- Consider upgrading server plan
Best Practices
Regular Testing
Test startup changes on a quiet server first
Backup Configuration
Document working configurations before changes
Monitor Resources
Watch CPU and memory usage after modifications
Stay Updated
Keep Java arguments current with best practices
Need help optimizing your startup configuration? Our support team can help you choose the best settings for your specific use case.
