#Troubleshooting

Common issues and solutions for Palworld server management.

#Server Won't Start

#Check Server Status

1. Go to control panel overview
2. Check current server state
3. Review recent logs

#Common Causes

Insufficient Resources

• Symptom: Server starts but crashes immediately
• Solution: Upgrade RAM or reduce max players

Port Conflicts

• Symptom: Error about ports already in use
• Solution: Check if another service is using ports 8211, 27015, 25575, or 8212

Corrupted Configuration

• Symptom: Server fails to start with config errors
• Solution: Reset to default configuration in Settings tab

Disk Space Full

• Symptom: Cannot write files, crashes on start
• Solution: Delete old backups or upgrade storage

#Solution Steps

1. Check Logs: View server logs in control panel
2. Verify Resources: Ensure adequate RAM/CPU available
3. Reset Config: Try "Reset to Defaults" in Settings
4. Restart Server: Stop completely, wait 30s, start again
5. Contact Support: If issue persists, open a ticket

#Players Cannot Connect

#Verify Server is Running

Check: Server status shows "Active" in control panel

If not running:

1. Start the server
2. Wait for startup to complete (1-2 minutes)
3. Verify status changes to "Active"

#Check Server Address

Players need the correct connection information:

Required:

• Server IP address (shown in control panel)
• Port: 8211 (default)

Format: 123.45.67.89:8211

#Password Issues

Server Password Enabled?

• Check Settings → Server Password field
• If set, players must enter this password to join
• Share password securely with players

Wrong Password:

• Players must enter exact password (case-sensitive)
• Verify password is communicated correctly

#Firewall or Network Issues

Server-side:

• Firewall rules are managed automatically
• Ports should be open by default
• If issues persist, contact support

Player-side:

• Player's firewall may block connection
• Router port forwarding not needed for players
• Try different network (mobile hotspot test)

#Server Full

• Check current player count vs. max players
• Increase max players in Settings if needed
• Ask players to wait for slot to open

#Performance Issues

#Server Lag or Low FPS

High Player Count

• Reduce max players
• Upgrade to higher RAM plan
• Optimize gameplay settings

Too Many Active Bases

• Reduce max bases per player
• Reduce max workers per base
• Ask players to consolidate builds

Resource-Intensive Settings

• Lower Pal spawn rate
• Reduce collection object count
• Disable or reduce invasions

#Memory Issues

Symptoms:

• Server crashes after running for hours
• Gradual performance degradation
• Out of memory errors

Solutions:

1. Enable automatic reboots (every 12-24 hours)
2. Upgrade RAM plan
3. Reduce max players
4. Monitor memory usage in control panel

#Disk Space Issues

Check disk usage:

1. Go to control panel
2. Check storage meter
3. Review backup retention

Solutions:

1. Reduce backup retention period
2. Enable "Delete Old Backups"
3. Reduce backup frequency
4. Upgrade storage plan
5. Download and delete old backups

#Configuration Problems

#Settings Not Applying

After Save:

• Changes saved but not applied to running server
• Server must restart to apply settings

Solution:

1. Use "Save & Apply Now" button
2. Confirm restart in popup
3. Wait for server to restart (1-2 minutes)

Alternative:

1. Save configuration
2. Manually stop server
3. Wait 30 seconds
4. Start server again

#Lost Custom Configuration

Symptom: Manual ini file changes overwritten

Cause: Auto-generate settings is enabled

Solution:

1. Disable "Disable Auto-Generate PalWorldSettings.ini" in Settings
2. Manually edit config files via file manager
3. Restart server

Warning: Control panel changes won't apply when auto-generate is disabled.

#Cannot Find Setting

Some advanced settings are not available in the control panel.

For advanced settings:

1. Disable auto-generate for the relevant ini file
2. Access files via control panel file manager
3. Edit PalWorldSettings.ini or Engine.ini manually
4. Restart server

Configuration files:

• /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini
• /palworld/Pal/Saved/Config/LinuxServer/Engine.ini

#Backup & Recovery

#Backup Failed

Check:

1. Disk space available
2. Backup schedule is correctly formatted
3. Server has write permissions

Solutions:

1. Free up disk space
2. Verify cron syntax
3. Check server logs for errors
4. Contact support if persists

#Restore from Backup

Warning: This will overwrite current world data!

Steps:

1. Stop the server
2. Access file manager in control panel
3. Navigate to backup directory
4. Download current save as extra backup
5. Copy backup files to save directory
6. Start server

Manual restore:

1. Download backup via SFTP
2. Extract backup files
3. Upload to /palworld/Pal/Saved/SaveGames/
4. Restart server

#World Corruption

Symptoms:

• Server crashes on startup
• Players cannot load their characters
• Error messages about corrupted save data

Solutions:

1. Stop server immediately
2. Restore from most recent backup:
   • Find latest working backup
   • Restore backup files
   • Restart server
3. If no backup available:
   • Contact support immediately
   • Do not restart server multiple times
   • Provide error logs

#Update Issues

#Update Failed

Symptoms:

• Auto-update runs but server still shows old version
• Update errors in logs

Solutions:

1. Manually stop server
2. Wait 2 minutes
3. Start server (will check for updates)
4. Check version in logs

If still failing:

1. Disable auto-update temporarily
2. Contact support for manual update
3. Provide error logs from update attempt

#Server Broke After Update

Symptom: Server worked fine, broke after Palworld update

Immediate action:

1. Check Palworld official channels for known issues
2. Review update changelog
3. Check compatibility notes

Solutions:

1. Restore previous version (if available)
   • Contact support for version rollback
2. Restore from backup before update
   • Use backup from before update
   • May lose recent progress
3. Wait for hotfix
   • Palworld developers often release quick fixes
   • Enable auto-update for automatic patching

#RCON / Remote Access

#Cannot Connect via RCON

Verify:

1. RCON is enabled in settings
2. Using correct port (25575)
3. Using correct admin password
4. Server is running

Test connection:

mcrcon -H 123.45.67.89 -P 25575 -p YourAdminPassword "Info"

Common issues:

• Wrong admin password (check Settings)
• Firewall blocking RCON port
• RCON not enabled

#REST API Not Working

Check:

1. REST API enabled in settings
2. Correct port (8212)
3. Server is running and active

Test API:

curl http://123.45.67.89:8212/v1/api/info

Troubleshooting:

• Verify API is enabled in Settings
• Check API port configuration
• Review firewall rules
• Consult Palworld API documentation

#Discord Integration

#Webhook Not Posting

Verify:

1. Webhook URL is complete and correct
2. Webhook still exists in Discord
3. Channel still exists
4. Bot has permissions

Test webhook:

1. Copy webhook URL from Discord
2. Paste into control panel exactly
3. Enable at least one notification type
4. Trigger event (restart server)
5. Check Discord channel

Common mistakes:

• Incomplete webhook URL
• Deleted webhook in Discord
• Wrong channel permissions
• Typo in URL

#Too Many Notifications

Solutions:

1. Disable player join/leave notifications
2. Enable "Suppress @everyone Pings"
3. Increase player logging poll period
4. Use separate muted channel

#Player & Gameplay Issues

#Player Lost Items/Progress

Common causes:

• Server crash before auto-save
• Rollback after restore
• Corruption

Solutions:

1. Check if recent backup available
2. Restore from backup (may help if recent)
3. Inform player about auto-save interval
4. Reduce auto-save interval to 15 minutes

Prevention:

• Frequent auto-saves (15-30 min)
• Regular backups
• Graceful shutdowns (no force kills)

#Pals Disappeared

Possible causes:

• Despawn due to settings
• Death while player offline
• World corruption

Check settings:

• Pal hunger rate (starved?)
• Death penalty settings
• Base worker limits

#Base Disappeared/Damaged

Causes:

• Decay enabled and active
• Raid/invasion damage
• Corruption

Solutions:

1. Check building deterioration rate (set to 0 to disable)
2. Restore from backup if necessary
3. Adjust invasion settings

#Emergency Procedures

#Server Completely Broken

If nothing works:

1. Stop server
2. Create emergency backup
   • Download all save files
   • Download configuration files
3. Reset to defaults
   • Use "Reset to Defaults" in Settings
4. Restore backups
   • Start with configuration backup
   • Restore world save backup
5. Contact support
   • Provide all error logs
   • Describe steps taken
   • Include backup information

#Urgent Recovery

For critical issues during peak hours:

1. Contact support immediately via priority ticket
2. Document the issue:
   • What happened
   • When it started
   • What changed recently
   • Error messages
3. Preserve logs:
   • Don't restart server multiple times
   • Download current logs
4. Communicate with players:
   • Post in Discord about downtime
   • Provide estimated resolution time
   • Keep community updated

#Getting Help

#Before Contacting Support

Gather information:

1. Server ID/name
2. Description of issue
3. Steps to reproduce
4. Error messages or logs
5. Recent changes made
6. Screenshots if applicable

#Support Channels

Ticket System (Recommended)

• Open ticket in control panel
• Fastest response time
• Direct access to server details

Discord Community

• Community support
• Quick tips and tricks
• Known issue discussions

Documentation

• Check all relevant guides
• Search for similar issues
• Review changelogs

#Log Files

Most useful logs:

• Server logs (in control panel)
• Error logs (if available)
• Update logs
• Backup logs

How to provide logs:

1. Copy relevant log sections
2. Use pastebin for long logs
3. Include timestamps
4. Note any errors or warnings

#Preventive Maintenance

#Weekly Checklist

• [ ] Check disk space usage
• [ ] Verify backups are running
• [ ] Review server performance metrics
• [ ] Check for pending updates
• [ ] Test backup restoration (monthly)

#Monthly Checklist

• [ ] Review and clean old backups
• [ ] Update player documentation
• [ ] Check community feedback
• [ ] Test emergency procedures
• [ ] Review configuration settings

#Best Practices

Do:

• Keep regular backups
• Test restores periodically
• Monitor resource usage
• Schedule maintenance windows
• Communicate with players
• Keep documentation updated

Don't:

• Make configuration changes during peak hours
• Delete all backups to save space
• Ignore warning signs (high memory, etc.)
• Force kill server processes
• Skip testing after major changes

#Next Steps

• Overview - Back to getting started
• Configuration - Server settings reference
• Management - Automation and maintenance