THCZ Book Edition 2026

FreeWebPanel User Manual

Hosting control panel operations for domains, websites, AutoSSL, mail, databases, files, apps, hosting accounts, backups, updates, recovery, agencies, and providers.

FreeWebPanel VPS owners, agencies, resellers, hosting providers, WordPress teams, and server operators Online reader + downloadable PDF 2026-07-04
01 / 48
02FreeWebPanel

How To Use This Manual

Read the first pages once, then jump to the task-specific chapters.

FreeWebPanel User Manual is designed as an online reader and a downloadable PDF. The online reader has navigation, motion, and expandable reading rhythm. The PDF is static, readable, and suitable for forwarding or printing.

  • Start with the overview and quick start.
  • Use the operations chapters when doing live work.
  • Use troubleshooting and FAQ before asking for support.
  • Do not paste secrets, private keys, API keys, customer data, or live server logs into public channels.
02 / 48
03FreeWebPanel

Source Map

The manual is based on public pages, local docs, and rollout notes.

These manuals consolidate the current public product story, live docs, release notes, and operational commands into a single readable book. They are intentionally public-safe.

  • FreeWebPanel public site: https://freewebpanel.com/
  • FreeWebPanel docs page: https://docs.talktoai.org/freewebpanel/
  • Install command: https://freewebpanel.com/downloads/thcz-install.sh
  • TalkToAI services docs: https://docs.talktoai.org/services/
  • ZSEC docs: https://docs.talktoai.org/zsec/
03 / 48
04FreeWebPanel

FreeWebPanel visual map

A visual orientation page for the manual.

The image is not a screenshot. It is a visual map for the product: the control surface, protected assets, operating paths, and review mindset this manual teaches.

  • Use the cover language as a memory aid for the product workflow.
  • Return to the table of contents when the task becomes specific.
  • Use commands only after reading the safety notes.
04 / 48
05FreeWebPanel

Table Of Contents

38 main chapters plus appendices.

Each chapter is short enough to scan but complete enough to act on. Use the page numbers in the PDF footer or the online jump links.

  • 01 / What FreeWebPanel Is
  • 02 / Who It Is For
  • 03 / Supported Server Direction
  • 04 / Clean VPS Principle
  • 05 / Install Command
  • 06 / Installer Preflight Checks
  • 07 / First Login
  • 08 / Login Recovery
  • 09 / Dashboard Overview
  • 10 / Websites
  • 11 / Domains
  • 12 / AutoSSL
  • 13 / Mail Accounts
  • 14 / Databases
  • 15 / File Manager
  • 16 / Apps And WordPress
  • 17 / Hosting Accounts
  • 18 / Backups
05 / 48
06FreeWebPanel

Table Of Contents Continued

Later chapters cover operations, troubleshooting, support, and glossary.

The second half is built for real usage: what to check, what to avoid, and how to explain problems safely.

  • 19 / Restore Workflow
  • 20 / Updates
  • 21 / Recovery Flows
  • 22 / Security Basics
  • 23 / ZSEC Companion
  • 24 / Firewall And Ports
  • 25 / DNS And Nameservers
  • 26 / SSL Troubleshooting
  • 27 / Mail Troubleshooting
  • 28 / Database Troubleshooting
  • 29 / File Permission Troubleshooting
  • 30 / Agency Workflow
  • 31 / Provider Workflow
  • 32 / Migration From Another Panel
  • 33 / Comparing Alternatives
  • 34 / SEO And Landing Pages
  • 35 / Structured Data
  • 36 / Support Requests
  • 37 / Operations Checklist
  • 38 / Glossary
06 / 48
01Chapter

What FreeWebPanel Is

FreeWebPanel is a hosting control panel lane for VPS owners, agencies, resellers, hosting providers, and operators who need websites, domains, SSL, mail, databases, files, apps, accounts, updates, and recovery workflows.

FreeWebPanel is a hosting control panel lane for VPS owners, agencies, resellers, hosting providers, and operators who need websites, domains, SSL, mail, databases, files, apps, accounts, updates, and recovery workflows.

  • It aims to be practical and approachable.
  • It should reduce hosting friction without hiding server responsibility.
  • It is positioned as a free/pro Linux hosting control panel path.
Do next
  • Use it when the user wants hosting control rather than raw terminal-only management.
07 / 48
02Chapter

Who It Is For

FreeWebPanel is useful for single-site owners, web agencies, SEO teams, hosting providers, resellers, and server operators.

FreeWebPanel is useful for single-site owners, web agencies, SEO teams, hosting providers, resellers, and server operators.

  • Beginners need safe defaults.
  • Agencies need repeatable deployments.
  • Providers need accounts, isolation, mail, SSL, and recovery flows.
Do next
  • Choose the workflow by audience before configuring services.
08 / 48
03Chapter

Supported Server Direction

FreeWebPanel material positions the panel around Ubuntu, AlmaLinux, and RockyLinux hosting control.

FreeWebPanel material positions the panel around Ubuntu, AlmaLinux, and RockyLinux hosting control.

  • Ubuntu VPS is the main install story.
  • Clean servers are safer than overloaded legacy machines.
  • Panel installs should not be tested first on irreplaceable production servers.
Do next
  • Use a fresh VPS or snapshot before installing.
09 / 48
04Chapter

Clean VPS Principle

Hosting panels touch web server, mail, database, firewall, SSL, users, files, and service configuration. A clean VPS reduces conflicts.

Hosting panels touch web server, mail, database, firewall, SSL, users, files, and service configuration. A clean VPS reduces conflicts.

  • Avoid installing over an unknown control panel.
  • Snapshot before major changes.
  • Read preflight warnings.
Do next
  • If migrating, document old DNS, mailboxes, databases, and files first.
10 / 48
05Chapter

Install Command

The primary install command is a one-line shell installer.

The primary install command is a one-line shell installer.

  • Read the script source before running on sensitive machines.
  • Use sudo/root only when you understand the target.
  • Run on a supported server.
Do next
  • Command: curl -fsSL https://freewebpanel.com/downloads/thcz-install.sh | sudo bash
11 / 48
06Chapter

Installer Preflight Checks

Preflight checks should identify OS, privileges, ports, packages, disk, hostname, and obvious conflicts before making changes.

Preflight checks should identify OS, privileges, ports, packages, disk, hostname, and obvious conflicts before making changes.

  • Do not ignore warnings.
  • Fix hostname/DNS before mail setup.
  • Keep enough disk free for sites, mail, databases, and backups.
Do next
  • Record preflight output when asking for support.
12 / 48
07Chapter

First Login

After install, the first login flow should show the panel URL, credentials, and any required final setup steps.

After install, the first login flow should show the panel URL, credentials, and any required final setup steps.

  • Save credentials safely.
  • Change temporary passwords.
  • Restrict admin access.
Do next
  • If login info is lost, use thcz-login-info.
13 / 48
08Chapter

Login Recovery

The login recovery command is part of the public FreeWebPanel direction.

The login recovery command is part of the public FreeWebPanel direction.

  • Use it on the server, not in a browser.
  • Protect the output.
  • Rotate credentials if exposed.
Do next
  • Command: thcz-login-info
14 / 48
09Chapter

Dashboard Overview

The dashboard should quickly show websites, domains, SSL status, mail, databases, backups, server health, updates, and important warnings.

The dashboard should quickly show websites, domains, SSL status, mail, databases, backups, server health, updates, and important warnings.

  • A dashboard is for scanning.
  • Deep settings belong in dedicated pages.
  • Warnings should be actionable.
Do next
  • Check dashboard after every install, restore, or update.
15 / 48
10Chapter

Websites

Website management should support creating sites, pointing document roots, managing runtime settings, and seeing status.

Website management should support creating sites, pointing document roots, managing runtime settings, and seeing status.

  • Keep one site per clear directory.
  • Document app type.
  • Do not mix unrelated projects in one folder.
Do next
  • Test each site with HTTP and HTTPS after creation.
16 / 48
11Chapter

Domains

Domain management connects DNS names to websites and services.

Domain management connects DNS names to websites and services.

  • DNS must point to the server.
  • Propagation takes time.
  • Mail and web DNS are separate concerns.
Do next
  • Check A/AAAA, MX, SPF, DKIM, and DMARC where relevant.
17 / 48
12Chapter

AutoSSL

AutoSSL should request and renew certificates for domains that resolve correctly.

AutoSSL should request and renew certificates for domains that resolve correctly.

  • DNS must be correct first.
  • Ports 80/443 must be reachable.
  • Renewal failures should be visible.
Do next
  • If SSL fails, check DNS, firewall, web server, and rate limits.
18 / 48
13Chapter

Mail Accounts

Mail support means users, mailboxes, domains, DNS records, spam posture, and deliverability boundaries.

Mail support means users, mailboxes, domains, DNS records, spam posture, and deliverability boundaries.

  • Mail is DNS-sensitive.
  • Set SPF, DKIM, DMARC.
  • Avoid using a poor-reputation IP for serious email.
Do next
  • Test inbound and outbound mail before promising production readiness.
19 / 48
14Chapter

Databases

Database management should allow creating databases/users, assigning permissions, and understanding backups.

Database management should allow creating databases/users, assigning permissions, and understanding backups.

  • Use separate users per app.
  • Limit privileges.
  • Back up before migrations.
Do next
  • Store database credentials outside public web roots.
20 / 48
15Chapter

File Manager

File management helps upload, edit, move, and inspect website files without always using SSH.

File management helps upload, edit, move, and inspect website files without always using SSH.

  • Avoid editing live production code without backup.
  • Check permissions.
  • Do not upload secrets to public folders.
Do next
  • Use version control for serious projects.
21 / 48
16Chapter

Apps And WordPress

App deployment can include WordPress and other site stacks.

App deployment can include WordPress and other site stacks.

  • Keep app versions updated.
  • Use SSL.
  • Use strong admin credentials.
  • Install only trusted plugins/themes.
Do next
  • Back up before plugin or theme changes.
22 / 48
17Chapter

Hosting Accounts

Hosting accounts are useful for agencies, resellers, and providers who need separation by customer or site.

Hosting accounts are useful for agencies, resellers, and providers who need separation by customer or site.

  • Separate users.
  • Limit access.
  • Avoid sharing admin credentials with clients.
Do next
  • Define account owner and quota policy before onboarding customers.
23 / 48
18Chapter

Backups

Backups are the difference between inconvenience and disaster.

Backups are the difference between inconvenience and disaster.

  • Back up files, databases, mail, and config.
  • Store copies off-server.
  • Test restores.
Do next
  • Never trust a backup that has not been restored in a test.
24 / 48
19Chapter

Restore Workflow

Restore workflows should be calm and documented.

Restore workflows should be calm and documented.

  • Identify what failed.
  • Select the right restore point.
  • Restore smallest needed scope first.
  • Verify after restore.
Do next
  • Keep a restore checklist on hand.
25 / 48
20Chapter

Updates

Panel updates and system updates should be planned, not random.

Panel updates and system updates should be planned, not random.

  • Read changelog.
  • Back up first.
  • Update during a maintenance window.
  • Verify sites after.
Do next
  • Document panel and OS versions after updates.
26 / 48
21Chapter

Recovery Flows

Recovery flows should include login recovery, service restart, backup restore, DNS correction, and update rollback where possible.

Recovery flows should include login recovery, service restart, backup restore, DNS correction, and update rollback where possible.

  • Do not panic-reinstall.
  • Collect logs.
  • Fix the smallest broken component.
Do next
  • Use thcz-login-info for login problems; use logs for service problems.
27 / 48
22Chapter

Security Basics

Hosting security starts with updates, SSH keys, firewall policy, least privilege, backups, and monitoring.

Hosting security starts with updates, SSH keys, firewall policy, least privilege, backups, and monitoring.

  • Disable unnecessary services.
  • Use strong passwords or keys.
  • Keep admin panels private where possible.
Do next
  • Run security checks after initial setup.
28 / 48
23Chapter

ZSEC Companion

ZSEC can support update discipline for Linux servers with security-only updates and advisory notes.

ZSEC can support update discipline for Linux servers with security-only updates and advisory notes.

  • ZSEC does not replace backups.
  • ZSEC does not accept remote commands.
  • Use it as part of operations discipline.
Do next
  • Read ZSEC docs before enabling automation.
29 / 48
24Chapter

Firewall And Ports

A hosting server usually needs web, mail, DNS, SSH, and panel access depending on configuration.

A hosting server usually needs web, mail, DNS, SSH, and panel access depending on configuration.

  • Open only what is needed.
  • Restrict admin ports.
  • Keep SSH recoverable.
Do next
  • Document every open port and why it exists.
30 / 48
25Chapter

DNS And Nameservers

DNS setup affects web, mail, SSL, and deliverability.

DNS setup affects web, mail, SSL, and deliverability.

  • Use consistent nameservers.
  • Set glue where needed.
  • Avoid changing everything at once.
Do next
  • Use DNS check tools before blaming the panel.
31 / 48
26Chapter

SSL Troubleshooting

SSL failures usually come from DNS, firewall, web server conflicts, bad redirects, or rate limits.

SSL failures usually come from DNS, firewall, web server conflicts, bad redirects, or rate limits.

  • Confirm domain resolves.
  • Check HTTP challenge path.
  • Check port 80.
  • Review certificate logs.
Do next
  • Fix DNS before repeated certificate requests.
32 / 48
27Chapter

Mail Troubleshooting

Mail issues often come from DNS, IP reputation, port blocking, authentication, or spam policy.

Mail issues often come from DNS, IP reputation, port blocking, authentication, or spam policy.

  • Check MX.
  • Check SPF/DKIM/DMARC.
  • Check logs.
  • Check whether provider blocks outbound SMTP.
Do next
  • Use test mailboxes before moving real customers.
33 / 48
28Chapter

Database Troubleshooting

Database issues come from bad credentials, permissions, service down, full disk, corruption, or app config mismatch.

Database issues come from bad credentials, permissions, service down, full disk, corruption, or app config mismatch.

  • Check service status.
  • Check disk.
  • Check app config.
  • Restore from backup only after diagnosing.
Do next
  • Back up before repair attempts.
34 / 48
29Chapter

File Permission Troubleshooting

Permissions can break uploads, PHP, static files, and security.

Permissions can break uploads, PHP, static files, and security.

  • Avoid 777 as a lazy fix.
  • Use correct owner/group.
  • Keep secrets unreadable by web users.
Do next
  • Record working permission patterns per app.
35 / 48
30Chapter

Agency Workflow

Agencies need a repeatable project path: create account, add domain, deploy site, enable SSL, set mail if needed, set backups, document handoff.

Agencies need a repeatable project path: create account, add domain, deploy site, enable SSL, set mail if needed, set backups, document handoff.

  • Use checklists.
  • Keep client access limited.
  • Store handoff notes.
Do next
  • Create a standard new-site template.
36 / 48
31Chapter

Provider Workflow

Hosting providers need onboarding, account limits, support boundaries, backups, updates, billing integration, and abuse handling.

Hosting providers need onboarding, account limits, support boundaries, backups, updates, billing integration, and abuse handling.

  • Separate customer accounts.
  • Define acceptable use.
  • Monitor resource usage.
Do next
  • Document support levels clearly.
37 / 48
32Chapter

Migration From Another Panel

Migration should inventory domains, files, databases, mailboxes, cron jobs, DNS, SSL, and app configs before moving.

Migration should inventory domains, files, databases, mailboxes, cron jobs, DNS, SSL, and app configs before moving.

  • Do not migrate blindly.
  • Lower DNS TTL first.
  • Test on temporary domain or hosts file.
  • Keep old server until verification.
Do next
  • Create a migration checklist per customer.
38 / 48
33Chapter

Comparing Alternatives

FreeWebPanel can be positioned as a free/pro Ubuntu-first panel, but comparisons should be factual and respectful.

FreeWebPanel can be positioned as a free/pro Ubuntu-first panel, but comparisons should be factual and respectful.

  • Avoid defamatory claims.
  • Use feature tables.
  • Tell users to test on a clean VPS first.
Do next
  • Comparison pages should link to install, free, FAQ, demo, and benchmark pages.
39 / 48
34Chapter

SEO And Landing Pages

For product growth, FreeWebPanel needs clear pages for cPanel alternative, Ubuntu control panel, CWP alternative, CloudPanel alternative, mail server panel, agency hosting, providers, security, changelog, roadmap, and press.

For product growth, FreeWebPanel needs clear pages for cPanel alternative, Ubuntu control panel, CWP alternative, CloudPanel alternative, mail server panel, agency hosting, providers, security, changelog, roadmap, and press.

  • Each page needs a clear H1.
  • Use internal links.
  • Use real visible FAQ content.
  • Do not fake reviews.
Do next
  • Keep installer URL stable.
40 / 48
35Chapter

Structured Data

Public pages can use Organization, WebSite, SoftwareApplication, BreadcrumbList, FAQPage for visible FAQ, and HowTo only on real how-to pages.

Public pages can use Organization, WebSite, SoftwareApplication, BreadcrumbList, FAQPage for visible FAQ, and HowTo only on real how-to pages.

  • No fake AggregateRating.
  • Keep canonical URLs clean.
  • Match schema to visible page content.
Do next
  • Validate after changes.
41 / 48
36Chapter

Support Requests

A useful support request includes OS, VPS provider, install time, error, domain, logs excerpt, and what changed recently.

A useful support request includes OS, VPS provider, install time, error, domain, logs excerpt, and what changed recently.

  • Do not include passwords.
  • Do not include private keys.
  • Redact customer data.
Do next
  • Paste minimal relevant logs only.
42 / 48
37Chapter

Operations Checklist

Daily operations: dashboard, disk, backups, SSL, mail queue, security updates, error logs, and customer tickets.

Daily operations: dashboard, disk, backups, SSL, mail queue, security updates, error logs, and customer tickets.

  • Scan before making changes.
  • Fix warnings while small.
  • Schedule updates.
Do next
  • Keep a weekly restore test habit.
43 / 48
38Chapter

Glossary

FreeWebPanel terms map to hosting tasks: site, domain, SSL, mailbox, database, file manager, app, hosting account, backup, restore, preflight, recovery.

FreeWebPanel terms map to hosting tasks: site, domain, SSL, mailbox, database, file manager, app, hosting account, backup, restore, preflight, recovery.

  • Use plain labels.
  • Avoid internal-only terms in public UI.
  • Make every warning actionable.
Do next
  • Send new operators to this manual first.
44 / 48
45FreeWebPanel

Command And URL Appendix

Use these only in the right context.

Commands and URLs are repeated here so operators can find them quickly. Read the chapter before running commands on production systems.

  • Install FreeWebPanel: curl -fsSL https://freewebpanel.com/downloads/thcz-install.sh | sudo bash
  • Recover login details: thcz-login-info
  • Read docs: https://docs.talktoai.org/freewebpanel/
45 / 48
46FreeWebPanel

Safe Operations Checklist

Run this before serious changes.

A manual is only useful when it changes behavior. This checklist is the calm-before-action page for live work.

  • Confirm the exact account, server, domain, or project.
  • Back up before destructive or live changes.
  • Use read-only checks before write actions.
  • Keep keys and secrets out of prompts, screenshots, and PDFs.
  • Verify the result in a browser and with a direct HTTP or command-line check.
  • Record what changed and how to roll it back.
46 / 48
47FreeWebPanel

Questions And Answers

Fast answers for the most common manual questions.

These answers are intentionally short. Use the chapter pages for operational detail.

  • What is the install command? — curl -fsSL https://freewebpanel.com/downloads/thcz-install.sh | sudo bash
  • How do I recover login details? — Run thcz-login-info on the server and protect the output.
  • Should I install on a clean VPS? — Yes. A clean supported VPS or a snapshot is safest.
  • Does it manage mail and databases? — The FreeWebPanel direction includes mail accounts, databases, files, websites, domains, AutoSSL, apps, and hosting accounts.
  • Does it replace backups? — No. The panel should make backups easier, but you still need tested off-server backup discipline.
47 / 48
48FreeWebPanel

Next Best Step

Do the smallest useful next action.

FreeWebPanel becomes easier when the next action is explicit. Pick the task, read the matching chapter, run a tiny verification, then scale up only after the first result works.

  • New user: read overview, quick start, and glossary.
  • Operator: read install, security, backup, and troubleshooting chapters.
  • Reviewer: read source map, boundaries, and proof links.
  • Team: standardize keys, templates, support notes, and update windows.