Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Installing forum software is not one universal procedure. A hosted service, a PHP package on shared hosting, a Composer-based application, and a Docker deployment each require different skills and infrastructure. Choose the deployment model first, then prepare DNS, HTTPS, databases, email, backups, and security before inviting users.

Choose hosted or self-hosted first

Model Best for You manage Main trade-off
Hosted forum Owners who want the fastest launch Branding, permissions, content and policies Recurring fees, provider limits and export dependencies
Self-hosted PHP Shared hosting and conventional forums Server, database, updates, backups, email and security More control, but more maintenance
Self-hosted Docker Administrators comfortable with Linux and VPSs Linux, Docker, firewall, storage, upgrades and recovery Powerful modern platforms, but unsuitable for ordinary cPanel hosting

Hosted services remove most server administration. Discourse’s hosted plans are described at its official pricing page, while Discourse software remains available for self-hosting. Self-hosting can reduce license costs and gives you infrastructure control, but “free software” does not make hosting, email, backup storage or technical labor free.

Match the platform to your situation

Platform Good fit Technical requirements Important limitation
phpBB Traditional open-source forum on ordinary hosting Web server, supported PHP modules and SQL database You maintain compatibility, updates and anti-spam
Flarum Modern, lightweight PHP forum Apache or Nginx, PHP extensions, MySQL/MariaDB, SSH; Composer for extension management Web-root and package compatibility require care
Discourse Modern community on a Linux VPS or managed hosting 64-bit Linux, SSH and Docker; 1 GB RAM with swap is a documented minimum, not a performance guarantee Official self-hosting is Docker-based; cPanel and Plesk methods are unsupported
XenForo Commercial traditional forum with first-party support Server meeting the current license requirements Paid license and separate hosting; verify current terms at the purchase page

Use the interaction model—not popularity alone—as your deciding factor. Forums organize categories, topics and replies; they are different from chat, comment systems, social networks, knowledge bases and learning-management systems. Check importer availability before replacing an existing community.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Prerequisites checklist

  • A domain or subdomain and access to its DNS records.
  • HTTPS support and control of ports 80 and 443 where applicable.
  • Hosting sized for registrations, concurrent visitors, attachments, search indexing, logs and backups.
  • The required PHP version and extensions, database engine, SSH, Composer or Docker access for your platform.
  • A separate backup destination, not only disk space on the production server.
  • Reliable outbound email or a transactional SMTP provider.
  • A patching, firewall, monitoring and incident-recovery plan.

Generic installation workflow

  1. Define the community. Decide whether it is public, private or invitation-only; estimate users and traffic; and list needs such as attachments, private messages, SSO, subscriptions or embedding.
  2. Choose the deployment model. Use hosted or managed service if you cannot maintain Linux, databases, security updates and restores. Choose phpBB for compatible shared hosting, Flarum when SSH and Composer are available, Discourse for a Docker-capable VPS, or XenForo when a commercial license and support fit the budget.
  3. Prepare infrastructure. Confirm DNS, HTTPS, operating-system resources, database access, email, firewall rules and separate backup storage.
  4. Create database credentials. Use a dedicated database and user. Record name, host, port, engine, character-set requirements and password privately; never publish credentials or leave them in shell history.
  5. Install the package or container. Upload a vendor archive for phpBB or XenForo, create a Composer project for Flarum, or run the official Docker installer for Discourse.
  6. Run the setup wizard. Enter the database connection, create the administrator, set the canonical hostname, language, time zone, site name and email sender.
  7. Configure DNS and HTTPS. Test the intended hostname, HTTP-to-HTTPS redirect, certificate, www/non-www behavior, reverse proxy and attachment URLs.
  8. Configure email. Verify registration, password reset, moderation alerts, private-message notifications and digests. Align SPF, DKIM and DMARC where applicable.
  9. Lock down the system. Remove or disable installers, restore least-privilege permissions, update every component, restrict administrator access, review uploads and enable rate limiting and anti-spam controls.
  10. Back up and restore-test. Include the database, uploads, configuration, themes, extensions, container volumes and infrastructure settings. A backup is unproven until restored elsewhere.

Detailed path: install phpBB on conventional hosting

Use the official phpBB installation guide for the exact release you are installing. Its 3.3.x documentation lists supported PHP and database combinations, but requirements are release-specific; do not copy old PHP versions from legacy documentation.

  1. Create a database and a dedicated database user with the privileges phpBB requires.
  2. Download the official package, extract it locally and upload the complete directory structure.
  3. Temporarily make config.php and the directories identified by the release documentation writable. Examples such as 666 or 777 in documentation are compatibility instructions for installation, not a blanket security recommendation.
  4. Open the installation path, for example https://your-domain.example/forum/install/, then complete the requirements check.
  5. Enter database details and create the administrator account. Let the installer generate the configuration.
  6. Restore restrictive permissions using correct file ownership and the narrowest access your host supports.
  7. Delete or disable the installer directory when the release instructions require it.
  8. Set the site name, language, time zone, registration policy, permissions, email and anti-spam controls.
  9. Test registration, password recovery, posting, moderation and uploads, then create and restore-test a backup.

Alternative path: Discourse on a VPS

Official self-hosted Discourse installation is Docker-based and expects SSH access to a 64-bit Linux server. Read the official installation requirements before provisioning. cPanel, Plesk, Webmin and similar non-Docker methods are not officially supported.

  1. Provision a fresh Docker-compatible Linux VPS. The cloud guide lists a modern single-core CPU, 1 GB RAM with swap as a minimum, and recommends a dual-core CPU; traffic, indexing and plugins may require more.
  2. Point the domain or subdomain DNS record to the server and ensure ports 80 and 443 are available.
  3. Connect over SSH with sufficient privileges and run the official command:
wget -qO- https://raw.githubusercontent.com/discourse/discourse_docker/main/install-discourse | sudo bash
  1. Enter the hostname, administrator email and mail settings in the interactive wizard, review the generated configuration and allow the container to build.
  2. Open the site over HTTPS, register the administrator account using the configured email and complete the in-app setup.
  3. Configure SMTP, backups, authentication, moderation and trusted domains. SMTP may be skipped for an initial test with alternate login behavior, but a production community normally needs reliable email for verification, notifications, digests and recovery.
  4. For maintenance, the Docker project documents commands such as:
cd /var/discourse
./launcher rebuild app
./launcher logs app
./launcher enter app

The cloud guide says HTTPS can be configured automatically and that builds generally take several minutes, but timing varies with the server and network. Use current official documentation rather than commands copied from old tutorials: cloud installation guide and Docker project.

Flarum and XenForo notes

Flarum

Flarum’s installation documentation expects a compatible Apache or Nginx setup, PHP extensions, MySQL or MariaDB and SSH. The documented 1.x Composer example is:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
composer create-project flarum/flarum:^1.8.0 .

Set the web root to the installation’s /public directory, then finish in the browser. The command is version-specific; consult the documentation for the major version you intend to run, including the separate 2.x installation path. Treat extension managers as privileged package installers and use them only when all administrators are trusted.

XenForo

For a new deployment, follow XenForo’s installation procedure. Do not use the upgrade procedure for a new site; existing installations should follow the install-versus-upgrade guidance. XenForo offers a paid installation or upgrade service, and its purchase page describes licensing and first-party add-ons. Check current requirements, prices and terms immediately before buying.

Post-installation configuration

  • Create a small, understandable category structure; empty subforums discourage participation.
  • Define roles for members, moderators and administrators, and test every permission boundary.
  • Publish community guidelines, privacy information, terms and a process for reporting abuse.
  • Enable registration verification, rate limits, CAPTCHA or equivalent anti-spam controls, moderation queues and bans.
  • Set attachment types, size limits, image processing and storage quotas.
  • Configure branding, mobile layout, search indexing policy, analytics and canonical URLs.
  • Seed useful discussions and explain how new members should participate; installation alone does not create an active community.

Test with separate user roles

Role Tests
Anonymous visitor HTTPS, readable categories, search visibility, registration and mobile layout
New member Verification email, posting, editing, attachments, subscriptions and password reset
Moderator Reports, queues, edits, locks, bans, notifications and audit history
Administrator Permissions, extensions, backups, restore procedure, settings and recovery access
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Troubleshoot by symptom

Database connection errors

Recheck host, port, driver, username, privileges, database version and character set. Flarum treats MySQL and MariaDB as distinct drivers in its configuration, so select the documented driver for your installation.

Blank page or installer cannot write

Inspect application and web-server logs, verify PHP extensions, ownership and writable cache/configuration directories, and avoid solving every problem with chmod 777.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

404s, redirect loops or certificate failures

Check DNS and IPv6 records, web-root or reverse-proxy rules, the canonical hostname, certificate coverage and whether ports 80/443 are occupied. Discourse’s cloud guide specifically covers DNS and port conflicts.

Email does not arrive

Confirm SMTP credentials, encryption and port; inspect logs, bounces and suppression lists; test multiple providers; and configure sender-domain authentication and reverse DNS. A forum without working password recovery is not production-ready.

Slow pages, failed builds or upload errors

Check RAM, swap, CPU, disk capacity, database growth, search indexing, image processing, backup jobs and plugin or extension load. Minimum hardware figures are not guarantees under heavy traffic.

Migration and ongoing maintenance

Before replacing an existing forum, verify an importer, password compatibility, attachment and private-message support, URL redirects, timestamps, groups, bans and rollback. Keep the old site read-only while testing. Discourse documents importers for platforms including vBulletin, phpBB and Vanilla; XenForo describes imports from several systems, but exact support depends on the source and version.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Schedule operating-system, runtime, database, forum, theme and extension updates. Stage upgrades when possible, keep backups off-server, monitor disk and email health, and periodically perform a restore drill. Protect database and Redis ports with a firewall in multi-container deployments, as noted in the Discourse Docker documentation.

The Bottom Line

Choose managed hosting if you cannot operate a server. Choose phpBB for compatible conventional PHP hosting, Flarum when you have Composer-capable PHP hosting, Discourse for a Docker-ready Linux VPS or official hosted service, and XenForo when commercial licensing and support justify the cost. In every case, email, backups, permissions, updates and moderation are part of installation—not optional follow-up work.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply. Prices as of November 19, 2026 7:04 am GMT.