FreeWebPanel User Manual

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

DNS And Nameservers

DNS is the launch spine for FreeWebPanel: websites, nameservers, AutoSSL, mail, redirects, and customer domains all depend on clean records.

Start DNS work before moving production traffic. Decide whether the domain is using registrar nameservers, Cloudflare-style DNS, or FreeWebPanel-managed nameservers. Record the current state, lower TTLs where appropriate, then change one layer at a time.

• Website records: use A records for the root/apex and www to the server IPv4, AAAA only when IPv6 is correctly configured, and CNAME only where it will not conflict with required mail or apex behavior.
• OpenZero AIOS lane: create web.domain.com, ns1.web.domain.com, and ns2.web.domain.com A records to the same server IPv4, keep them DNS-only/grey-cloud while preparing the host, then use those nameservers for customer domains on the AIOS web node.
• Mail records: verify MX, SPF TXT, DKIM TXT, and DMARC TXT before promising mail delivery. A panel can create mailboxes, but DNS and IP reputation decide deliverability.
• SSL records: AutoSSL/HTTP validation needs the domain to resolve to the panel server, port 80 reachable, and no proxy or redirect blocking the challenge path.
• Nameserver delegation: only delegate customer domains to ns1/ns2 after glue/A records and panel DNS zones are ready. Keep a rollback note with old nameservers and previous MX records.

AIOS DNS example
web.domain.com  A  SERVER_IPV4
ns1.web.domain.com A SERVER_IPV4
ns2.web.domain.com A SERVER_IPV4

Customer domain checklist
apex A/AAAA -> correct server
www -> apex or server
MX -> intended mail host
SPF/DKIM/DMARC -> present
port 80 -> reachable for AutoSSL
old records -> documented before change

SSL Troubleshooting

AutoSSL depends on DNS, port 80, web-server routing, challenge files, redirects, proxies, and certificate-rate discipline.

When SSL fails, pause repeated certificate requests and diagnose the path. Repeated failed attempts can waste time and may hit provider rate limits. The correct order is DNS first, HTTP reachability second, panel/site mapping third, then certificate request.

• Confirm the domain and www resolve to the FreeWebPanel server with the intended A/AAAA records.
• Check port 80 is open publicly and the HTTP challenge path is not blocked by firewall, redirect loops, maintenance pages, or a proxy mode that hides the origin.
• Confirm the website exists in the panel, the document root is correct, and the domain is attached to the right account/site.
• If Cloudflare or another proxy is used, test DNS-only/grey-cloud during issuance when HTTP validation is failing.
• After issuance, verify HTTPS, forced redirects, mixed-content warnings, certificate name coverage, expiry date, and renewal behavior.

SSL triage order
1. DNS resolves to panel server
2. HTTP port 80 reaches the site
3. Domain maps to the correct web root
4. Challenge path is reachable
5. Certificate request is made once
6. HTTPS redirect and renewal are tested

Mail Troubleshooting

Mail success needs panel mailboxes, DNS authentication, provider port policy, reverse DNS, IP reputation, and realistic delivery expectations.

FreeWebPanel can provide the control surface for mail accounts and domain mail settings, but deliverability is wider than the panel. Treat mail as an operational service: test inbound, outbound, authentication, spam placement, and recovery before moving customer communication.

• Inbound mail: confirm MX points to the intended mail host, mailboxes exist, quotas are not full, and the domain is attached to the correct account.
• Outbound mail: check whether the VPS provider blocks SMTP ports, then verify SPF alignment, DKIM signing, DMARC policy, reverse DNS/PTR, and server hostname consistency.
• Forwarding: test forwards to Gmail/Outlook carefully because forwarded mail can fail SPF unless DKIM/ARC/provider policy is handled well.
• Reputation: new or poor-reputation IPs may place mail in spam even when records are technically correct. Use transactional providers for critical business mail when needed.
• Support notes: never paste full mailbox passwords, private customer messages, or raw authentication logs into public support channels.

Mail DNS minimum
MX  mail.domain.com
A   mail.domain.com -> SERVER_IPV4
TXT SPF: v=spf1 mx ip4:SERVER_IPV4 -all
TXT DKIM: panel/provider public key
TXT DMARC: v=DMARC1; p=quarantine; rua=mailto:postmaster@domain.com

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.