How to Use FASTPANEL for Everyday Server Tasks

Published on October 28, 2026

A new server does not need a long command-line ceremony before it can host a site. FASTPANEL puts the routine work in one place: websites, domains, databases, SSL certificates, mail, backups, and access controls. This guide explains how to use FASTPANEL safely from the first login through normal daily administration, with enough technical detail to avoid the small mistakes that usually become a Friday evening problem.

Start with the server and account

Log in to FASTPANEL using the panel address and administrator credentials supplied with your server. Use a password manager, then change any temporary password immediately. If two-factor authentication is available in your deployment, enable it before creating websites or adding client access.

The dashboard gives a quick view of system resources and installed services. Check available disk space, memory use, and the status of core services before loading a production site. A server can look healthy while its disk is nearly full, particularly after an import or a backup job. Storage alerts are less exciting than a website outage, but they are much cheaper.

For agency or team use, avoid sharing the administrator login. Create separate user accounts with only the permissions each person needs. Give a developer access to a specific site, for example, rather than handing over the keys to every domain, database, and mail account on the machine.

Confirm the software stack

Before deployment, review the PHP versions, web server configuration, and database service available on the server. A modern application may need PHP 8.2 or later, while an older ecommerce plugin can fail on a newer release. Do not select a version just because it is newest. Match the application vendor's supported version first, then plan upgrades in a test environment.

If you are moving an existing site, note its current PHP version, extensions, cron jobs, database size, document root, and mail configuration. Migration goes much better when these facts are written down instead of being recovered from memory at 2 a.m.

How to use FASTPANEL to create a website

Open the Websites section and choose the option to add a new website. Enter the domain name, select the appropriate PHP version, and create the site. FASTPANEL will prepare the web root and the associated configuration for the domain.

For a new WordPress, Laravel, or custom PHP project, upload files through the built-in file manager or connect with SFTP using the site credentials. SFTP is the better choice for larger deployments and repeatable workflows. The file manager is useful for a quick edit, a small upload, or checking whether an archive extracted where you expected it to.

Make sure the application's public directory is the web root. For WordPress, this is commonly the directory containing `wp-config.php`. For Laravel, the web root should point to the `public` directory, not the project root. Exposing the wrong directory can reveal configuration files or simply produce a very confusing error page.

Next, create a database and a dedicated database user in the Databases section. Use a unique, long password and give that user access only to the required database. Add those credentials to the application configuration file. For an imported site, upload the SQL backup through the database tool or command line, then update the configuration values to match the new server.

After files and database are in place, test the site using a temporary preview method if available, or wait until DNS points to the server. Do not change production DNS until the site loads correctly, the admin area works, and forms or checkout functions have been tested. This is not the most beautiful DNS situation, but it is under control when the preparation is done first.

Point the domain and secure it with SSL

FASTPANEL can create the website configuration, but public traffic still depends on DNS. At your DNS provider, point the domain's A record to the server's IPv4 address. Add an AAAA record only if IPv6 is configured and tested on the server. For `www`, either create a matching record or use the redirect approach supported by your site setup.

DNS changes can appear quickly, but propagation depends on existing TTL values and resolver caches. Keep the old hosting active until the new site is serving correctly from the new server. For email-hosting domains, preserve existing MX, SPF, DKIM, and DMARC records unless you are deliberately moving mail too.

Once DNS resolves to the server, open the SSL section for the website and issue a certificate. The panel can normally request a Let's Encrypt certificate automatically. Validation will fail if DNS is incorrect, port 80 is blocked, or another web server rule intercepts the validation request. Fix the basic path first rather than repeatedly requesting certificates. The logs are telling the same story now.

After the certificate is active, force HTTPS in the website settings or application configuration. Then test the HTTPS version, the non-www and www variants, and at least one inner page. A green padlock on the home page is not a full test if product images, scripts, or API calls still load over HTTP.

Handle email, cron jobs, and routine maintenance

If the server will send or receive mail, create mailboxes in the Mail section and set strong passwords. Configure SPF, DKIM, and DMARC records before relying on server-sent transactional messages. These records improve deliverability, but they do not repair a poor sending reputation or a compromised contact form.

Use cron jobs for scheduled application tasks such as WordPress maintenance, Laravel scheduler commands, report generation, or queue processing. In FASTPANEL, add the command, choose a schedule, and set an appropriate user context. Start conservatively. A task scheduled every minute can be correct for a queue worker, but it can also create unnecessary load if the command takes longer than expected.

Check cron output after deployment. If an application does not log scheduled work clearly, send output to a controlled log file or a monitored mailbox. Silent failures are a favorite hobby of scheduled tasks.

Keep software current, but treat updates as changes rather than rituals. Apply security updates promptly, especially for the operating system, PHP, CMS core, and exposed plugins. For major PHP or application upgrades, take a backup and test compatibility first. The right update path depends on how critical the site is, its extension stack, and whether you have a staging environment.

Backups are the recovery plan, not a checkbox

Set up scheduled backups before the server holds data you cannot recreate. Include website files, databases, and any relevant mail data. Database backups deserve special attention because an archive of files alone will not restore orders, customer records, or form submissions.

Choose a retention period that matches how quickly bad changes are discovered. A daily backup retained for seven days may be enough for a small brochure site. An active store or SaaS application may need more frequent database backups and longer retention. Keep at least one copy away from the production server. If the only backup sits on the same disk as the site, it is more of a hopeful duplicate.

Test a restore on a nonproduction location when possible. Confirm that both files and database restore together, credentials work, and the application opens without missing assets. A backup system earns trust during a restore, not when a scheduled job says “completed.”

Troubleshoot from symptoms, not guesses

When a site returns a 500 error, starts loading slowly, or shows a database connection failure, begin with the website and server logs available in FASTPANEL. Check the timestamp, identify the affected domain, and look for a repeated PHP, permission, or database message. One clear error is more useful than ten random configuration changes.

Common issues are usually practical: incorrect database credentials after migration, wrong file ownership, exhausted disk space, a PHP extension missing after a version change, or an expired SSL certificate caused by DNS changes. Verify the service status and recent changes before restarting anything. Restarting services can hide a clue and disrupt sites that were not involved.

For persistent performance issues, inspect CPU, RAM, and disk usage alongside application logs. A traffic spike, a slow database query, a runaway backup process, and an under-sized VPS can all feel like “the site is slow,” but the fix is different for each. Monitoring gives the useful answer: what became busy, when, and for how long.

FASTPANEL is designed to make daily hosting work manageable, not to replace sensible operational habits. Build the site carefully, keep access limited, verify backups, and investigate alerts while they are still small. If the server needs a second pair of eyes, Kodu.cloud support can help turn panel symptoms into an actionable next step.

A calm server is rarely an accident. It is usually the result of a few routine checks done before they become urgent.

Andres Saar Customer Care Engineer