Help

GoPanel Quick Guide

A practical quick start for real scenarios: install, access, websites and certificates, containers and databases, pipelines and collaboration, the AI assistant and troubleshooting.

Quick Start

Goal: from a fresh machine to an open GoPanel in a few minutes.

Prepare the server

A server or VM with public access is recommended. Open the panel port (see the install output) and have a login-capable system account ready (on Linux usually root or a user with sudo).

Run the install command

Run the following command in the server terminal to install and initialize:

bash

$ curl -sSL https://gopanel.run | bash

The install prints the access URL and initial account info. Keep the log or take a screenshot.

Open the panel

Open the printed address in your browser and, after the first login, start managing websites, certificates, containers, databases and pipelines.

First login & security tips

Lay the security groundwork first and you will save a lot of troubleshooting later.

Change the initial password

Change the admin password immediately after the first login, using a strong one (length, complexity, uniqueness).

Enable HTTPS

Bind a domain to the panel entry and enable HTTPS to avoid plaintext login and session hijacking.

Least-privilege collaboration

When several people use the panel, create a separate account for each member with least privilege instead of sharing the admin account.

Set a backup strategy

Set up periodic backups and retention for key configuration and databases, and take a manual snapshot before major changes.

Common tasks (how to do them smoothly)

The most typical paths below are good to follow step by step the first time.

Website & domain: from zero to live

1) Add a site: choose a domain and site directory or app deployment method.

2) Configure a reverse proxy: point the domain at your app port or container service.

3) Enable HTTPS: request a certificate and configure auto-renewal.

4) Verify the launch: check DNS, ports, certificate chain and access log.

SSL certificates: issue & auto-renew

Before requesting a certificate, make sure DNS resolution is effective and the validation method (HTTP/DNS) can pass.

Tip: enable auto-renewal for key business domains and watch for renewal-failure notifications.

Containers & apps: deploy common services

Prefer the "app store / template" to deploy databases, caches, message queues and other common components.

After deploying, check: port mapping, data volume mounts, environment variables, health checks and logs.

Databases: create, grant & back up

For production: a dedicated account, least privilege, periodic backups and availability monitoring.

For changes: back up before changing the schema, and keep audit records for key operations.

Pipelines (CI/CD): lock down the release flow

Recommended flow: pull code → build → test → package → deploy → health check → optional rollback.

Manage environment variables, secrets and credentials in secure config, never in the repository.

AI assistant: how to ask effectively

The value of AI is not just answering questions, but chaining "troubleshooting reasoning + executable actions" together.

How to ask well

State three things clearly: the goal, the current symptom and the key logs:

"I am deploying an Nginx reverse proxy to port 3000 and get a 502; please give me a troubleshooting order based on the logs and tell me what to look at in each step."

Turn actions into templates

Turn common flows into team templates:

For example: cert-renewal failure triage, container upgrade rollback, database backup/restore drills.

Team collaboration: the minimal loop

The difference between "one person can use it" and "the team uses it reliably" is standards and permissions.

Permissions & audit

Admins only do "authorization and policy"; daily operations should be done with each member's own account so every key action is traceable.

Release discipline

Release through pipelines instead of logging into servers by hand; for production changes follow "backup → change → verify → rollback plan".

FAQ (check here first)

When something goes wrong, troubleshoot in the order "network → port → service state → logs".

Cannot open the panel (timeout / connection refused)

1) Check whether the server security group/firewall allows the port.

2) Check whether the panel service is running, and restart it if needed.

3) If you use a reverse proxy, confirm the upstream port and health are normal.

Certificate issuance failed

Common causes: DNS not effective, 80/443 not open, validation path blocked, proxy rule conflicts.

Tip: first open the validation path in a browser to confirm it is reachable, then retry.

502/404 after deploy

502: the upstream service is not started / the port is unreachable / the container health check failed.

404: the routing rule does not match or the site root is set incorrectly.