Control Center SFTP Guide

[- Alex - 36]

Control Center SFTP Guide
Secure Server File Access
This guide may be updated as GGU policies, procedures, platforms, and organizational needs change.

Use SFTP when you need direct file access to a GGU game server through the Control Center.

 

Connection Information

Use the SFTP connection details shown by the GGU Control Center for the specific server. Do not rely on old hard-coded hostnames or usernames copied from another server.

• Host: use the SFTP host displayed in the Control Center.
• Port: use the displayed SFTP port.
• Username: use the server-specific SFTP username shown by the Control Center.
• Password: use your Control Center account password or the current authentication method configured for SFTP.

 

Recommended Clients

• WinSCP
• FileZilla
• Cyberduck
• Any maintained SFTP client that supports host key verification

 

Security

• Verify the host key when connecting to a new endpoint.
• Do not save credentials on shared computers.
• Do not upload unknown binaries or scripts to production servers.
• Back up files before high-impact manual edits.
• Use the Control Center file manager for small changes when SFTP is unnecessary.

 

Change Control

• Know what you are changing and why.
• Back up or ensure a rollback path for high-impact changes.
• Avoid combining unrelated changes.
• Record material production changes.
• Test before production when practical.

 

Validation

• Confirm the service starts successfully.
• Review logs for new errors.
• Test the exact behavior changed.
• Confirm permissions and integrations still work.
• Monitor briefly after deployment for delayed failures.

 

Escalation

If a change affects systems outside your responsibility, creates a security concern, or cannot be safely reversed, stop and escalate rather than continuing to experiment in production.

 

File Transfer Practices

• Upload to a temporary filename when replacing critical files where practical.
• Verify file ownership/permissions after transfer.
• Do not overwrite large directories blindly.
• Use checksums or size comparison for important artifacts.

 

Prerequisites

• Confirm you are authorized to make the change.
• Confirm the target system/server/repository.
• Read current project or service documentation.
• Identify the expected result.
• Identify a rollback or recovery path for high-impact work.

 

Common Mistakes to Avoid

• Copying commands or values from a different server without checking context.
• Making several unrelated changes before testing.
• Ignoring warnings because the service still appears to start.
• Editing production directly when a safer test or review path exists.
• Deleting old files or backups before the replacement is verified.
• Treating permissions errors as a reason to grant broad administrator access.
• Failing to record what changed.

 

Operational Record

For material changes, record enough information for another administrator to understand the target, change, reason, result, and rollback point. This may be a ticket, issue, pull request, deployment note, incident record, or appropriate Leadership message.

 

If Something Goes Wrong

1. Stop making unrelated changes.
2. Preserve the current logs and error output.
3. Determine whether immediate rollback is safer than continued troubleshooting.
4. Restore the last known-good state where practical.
5. Escalate with the exact error, target service, recent changes, and reproduction steps.
6. After recovery, document the cause and any preventative follow-up.

 

Use the connection details shown by the Control Center, not stale copied values.

Edited yesterday at 08:11 AM by - Alex -
Updated Guide