MyBB Setup Breakdown: Essential Server Metrics and Permissions

Preparing a server environment for community software requires establishing precise configurations before running the web installer. When setting up a discussion board using MyBB, getting file permissions, server configuration rules, database choices, and root paths right from the start ensures your community platform remains accessible and secure. This key-numbers breakdown covers the core metrics and prerequisites detailed in the Install - MyBB Documentation.
Permissions by the Numbers: 666, 755, 775, and 777
Correct permissions prevent web server write failures while blocking unauthorized modifications. Prior to applying file permissions, you must rename inc/config.default.php to config.php. When setting up directories on Unix-like environments, the official guidance suggests evaluating less permissive modes before using open write access:
- chmod 755 or chmod 775: Modes to try on directories before applying broad write permissions.
- chmod 666: Applied directly to configuration targets:
inc/config.phpandinc/settings.php. - chmod 777 (or 0777): Assigned to volatile storage:
cache/,cache/themes/,uploads/, anduploads/avatars/. - chmod 666 (Optional language files): Covers
inc/languages/english/*.phpandinc/languages/english/admin/*.php. - chmod 777 (Optional backup directory): Covers
admin/backups/alongside cache and upload assets.
On Windows systems, corresponding folders and files require Full modify permissions. Administrators managing remote servers can adjust these attributes using an FTP client like FileZilla or via the command line.
Database Configurations: 4 Supported Engine Options
MyBB provides native support for multiple backend databases during the browser installation phase. The installer displays input fields based on the selected engine:
- MySQL: Standard relational database option.
- MySQL Improved: When choosing between standard MySQL and MySQL Improved, Improved is typically the better choice.
- SQLite 3: File-based engine requiring a Database Path rather than host, username, password, or database name entries.
- PgSQL: PostgreSQL relational database option.
Unless your host provides specific alternate details, the database host defaults to localhost. By default, the installer applies the table prefix mybb_. If an installation already exists within that target database using that prefix, it must be changed to another string. For broader comparisons of how backend requirements align across platforms, see our Forum Software Server Requirements Compared.
Server Configuration Files: 2 Web Server Directives
The standard archive provides two separate configuration files in the root folder to handle web server routing and protection:
- Apache Directives: The file
htaccess.txtmust be renamed to.htaccessand kept in the MyBB root directory. Additionally, verify that an existing.htaccessfile is present in theadmin/backups/directory (which comes pre-renamed inside the package). - Nginx Directives: Directives within
htaccess-nginx.txtmust be added directly into your server's Nginx configuration file.
Understanding these server baselines is essential when reviewing your infrastructure prior to deployment, as discussed in our guide to starting a forum.
Command-Line Provisioning: Aria2 Version 1.9.3 and CLI Tools
For administrators installing over SSH, the Install - MyBB Documentation outlines shell-based extraction routines. The automated preparation flow requires standard system utilities including unzip, mv, rm, and chmod, paired with one of four download tools:
wgetcurlaria2(requiring version >= 1.9.3)lynx
These commands download the archive package directly to the host, extract the Upload/* tree, reposition the application files into the document root, delete the temporary archive, rename the configuration file, and recursively apply 0777 permissions to cache, uploads, settings, and configuration targets.
Installation Finalization: Account #1 and Directory Locking
When executing the web installer (accessed via /install or a subdirectory like /forums/install), board settings are applied:
- Default Forum Name: Sets automatically to
Forums. - Cookie Handling: In version 1.4 and later, the Cookie Domain and Cookie Path fields are pre-filled automatically. If hosting multiple boards on a single domain, adjust the path to your specific folder (such as
/forums/). - Administrator User ID #1: The initial administrative account generated during setup receives user ID #1, granting complete access to every section of the Admin CP.
- Lock File Safeguard: Once finished, the
install/directory must be removed, or locked by creating a file namedlockinside the directory to disallow access to installer and upgrader routines.
Sources
Published October 29, 2026. No affiliate links on this page. Facts come from the sources linked above; check them for updates.