DOCSEARCHbyAlgolia
Submit Docs

AcePanel Documentation

website·Indexed 32 days ago

https://acepanel.net

A server administration and recovery panel featuring a root-only CLI, container management via Docker, SSL/TLS certificate handling with ACME support, and a comprehensive system toolbox for process, disk, and network management. It provides tools for managing native applications, runtime environments, databases (MySQL, PostgreSQL), and static websites, alongside an OpenAPI-compliant management API.

Tokens
189K
Snippets
309
Records
1.5K
Agent score
62%

What's inside AcePanel

  1. Overview of AcePanel FRP Manager

    AcePanel provides a management interface for FRP (Fast Reverse Proxy), a tool for reverse proxying and intranet penetration. It allows simultaneous management of the server component (Frps), which is deployed on a public-facing server to receive tunnel connections, and the client component (Frpc), which is deployed on the server hosting the local services to be exposed. Access the manager via Apps > Installed > FRP > Manage.

  2. Overview of AcePanel Certificate Management

    The Certificate module in AcePanel manages SSL/TLS certificates. It supports automatic issuance of free certificates via the ACME protocol and allows users to upload their own certificates. The module is divided into three main functional areas: Certificate management, ACME Account management, and DNS API configuration.

  3. Overview of AcePanel server management panel

    AcePanel is an open-source server operation and management panel designed for low resource consumption and minimal system impact. It is developed using Go and runs as a single binary file. Key characteristics include support for offline execution (stopping the panel does not affect deployed services), full open-source availability for secondary development, and a commitment to remaining free of charge for the core panel.

  4. Overview of AcePanel Compose

    The Compose feature in AcePanel is based on Docker Compose. It allows developers to define multi-container applications—including services, networks, and volumes—using a single YAML file, enabling the entire application stack to be started or managed with one click. It is particularly useful for microservices architectures, development environments, and applications requiring a web server, database, and cache.

  5. Overview of supported runtime environments in AcePanel

    AcePanel provides runtime environments for various programming languages to support websites and projects. The following languages and versions are supported:

    LanguageAvailable VersionsDescription
    Go1.20 - 1.25High-performance backend services
    JavaJDK 8, 11, 17, 21, 25Uses Amazon Corretto distribution
    Node.js20, 22, 24Frontend builds and Node applications
    PHP7.4 - 8.5Web development
    Python3.10 - 3.14Scripts and Web applications
    .NETLTS / STS versionsCross-platform framework for modern apps

    Multiple versions of the same language can be installed simultaneously to support different projects.

  6. Overview of AcePanel Orchestration (Docker Compose)

    The Orchestration feature is based on Docker Compose and allows users to define and run multi-container applications using a single YAML file. It describes services, networks, and volumes, enabling one-click deployment of entire application stacks. It is ideal for multi-container apps (e.g., Web + DB + Cache), development environments, and microservices architectures.

  7. Overview of AcePanel Certificate Management

    The Certificate module in AcePanel is used to manage SSL/TLS certificates. It supports automatically requesting free certificates via the ACME protocol, uploading existing certificates, and generating self-signed certificates. The module is divided into three main areas: Certificate management, ACME Account management, and DNS API configuration.

  8. Overview of AcePanel Application Management

    The Application module in AcePanel is used to install, configure, and manage software on a server. It categorizes software into three main types: Native Applications (installed directly on the system), Runtime Environments (language-specific environments), and Container Templates (Docker-based one-click deployments).

  9. Overview of Project management in AcePanel

    The Project module manages backend applications as system services. Unlike 'Websites' which depend on a web server, Projects run as independent processes with features like automatic restart, auto-start on boot, and dedicated log management. They are typically used for backend services and APIs and require a reverse proxy for external access.

  10. Overview of AcePanel Database Module

    The Database module allows for the management of various database types, including relational databases (MySQL, MariaDB, PostgreSQL), NoSQL and analytical databases (MongoDB, ClickHouse), search engines (Elasticsearch), key-value stores (Redis), and embedded databases (SQLite). It provides capabilities to create databases, manage users, browse data, and configure database servers.

  11. Overview of AcePanel Compose

    The Compose feature is based on Docker Compose and is used to define and run multi-container applications. It allows users to describe services, networks, and storage volumes via a YAML file to launch an entire application stack with a single action. It is ideal for multi-container apps (e.g., Web + DB + Cache), development environments, and microservices architectures.

  12. Overview of Scan Awareness

    Scan Awareness uses eBPF (TC ingress) to passively detect inbound port scans against a server. It records these attempts and can automatically block offending IP addresses.

    Key Technical Behaviors:

    • Detection Point: Attaches at TC ingress, meaning it detects packets before the system firewall (like firewalld or ufw) drops them. A record in Scan Awareness proves a packet reached the interface, not necessarily that it bypassed the firewall.
    • TCP Logic: Only SYN packets (new connection attempts) are treated as scans.
    • UDP Logic: Ignores response traffic from well-known service source ports (e.g., DNS 53/853, NTP 123, DHCP 67/68/546/547, HTTPS/QUIC 443, mDNS 5353, IKE/IPsec 500/4500).
    • Listening Ports: Connection attempts to ports where a service is actually listening are ignored; only attempts to closed or unused ports are recorded as scans.
    • Requirements: Requires a Linux server with a recent enough kernel to support the eBPF subsystem.