Use this page for a normal Linux VPS deployment. You can start an automatic browser deployment or run the official installer yourself over SSH. Both paths use the same MuchoCore release and production checks.
The standard MuchoCore VPS deployment expects a VPS with its own public IPv4 that accepts inbound TCP 80 and 443. Point your GDPS domain directly to that IPv4. NAT/CGNAT VPS products without public inbound 80/443 are not suitable for the normal direct-HTTPS path; use the documented Cloudflare Tunnel mode instead.
Port 80 is intentionally kept enabled for legacy Geometry Dash clients and normal HTTP requests. Port 443 provides HTTPS. HTTP is not globally redirected to HTTPS; only protected browser areas such as the Admin Panel require HTTPS.
Create an A record for the hostname you want to use for the GDPS.
gdps.example.com → YOUR_DEDICATED_VPS_IPV4
Wait for DNS to resolve before starting the installer. Caddy serves both HTTP on port 80 and HTTPS on port 443, with managed TLS certificates on the HTTPS endpoint.
Automatic deployment connects to the VPS from MuchoGDPS and shows live installer output. Manual installation runs the same official release bootstrap directly inside your VPS over SSH.
Connect to the VPS as root or as a sudo-capable user, then run:
curl -fsSL https://raw.githubusercontent.com/IZKGMD/GMDmucho-core/main/install-remote.sh | sudo bash
The installer asks for the GDPS domain and initial administrator password, installs Docker and the production stack when needed, applies migrations, configures Caddy and verifies the public health endpoint.
After the installer finishes, open the public health endpoint:
http://gdps.example.com/health
HTTP is expected to respond with:
1
HTTPS should respond with the same health result:
https://gdps.example.com/health
Expected response:
1
Then open the Admin Panel:
https://gdps.example.com/admin/
Open the Admin Panel client patcher and generate the client patch for your supported Geometry Dash version. Then test account login, level search, level upload and Cloud Save from a real client.
Install MuchoCore against a fresh target database first. Then use Admin → Tools → Migration Center or the Migration Kit. Do not use your legacy GDPS database as the initial MuchoCore target.
Production updates use published stable GitHub releases. The usual operator command is sudo /opt/mucho-core/update.sh.
If your provider does not give the VPS a dedicated public IPv4 or does not pass inbound 80/443, the normal direct path cannot receive public traffic. MuchoCore supports an explicit Cloudflare Tunnel transport for that infrastructure.
This page documents the standard VPS deployment. Shared hosting does not require a dedicated public IPv4: use /install/shared/ instead. Full operator documentation is maintained in the MuchoCore repository.