List the required forum categories, member groups and plugins. Check that a planned plugin supports the selected MyBB and PHP versions, particularly when moving an older forum.

Use the project's current supported release information and the requirements shown for the package you select. If Softaculous offers an older or unsuitable build, follow the current vendor installation process or ask us to confirm a suitable environment. Do not enable an unsupported PHP runtime simply to reproduce an old tutorial.

1. Back up any existing site at the destination. Choose an empty directory or a separate staging hostname for a new installation; never approve overwriting a working site without a migration plan.
2. Open Softaculous where your hosting service includes it. In cPanel, search for Softaculous Apps Installer. In SiteWorx, use Hosting Features > Softaculous where that integration is enabled.
3. Find MyBB and review the package and requirements before selecting Install. Select the correct HTTPS domain. Leave In Directory empty only when the empty domain root is the intended destination.
4. Complete the application-specific fields and a strong administrator credential stored in a password manager. Supply a reachable administrative email where requested. Review database, backup and update choices instead of accepting unsuitable defaults.
5. Start installation once and wait for the completion result. Record the public and administration URLs. Where this application needs the publisher's own deployment process, complete that process instead of forcing an outdated installer package.

Set the forum URL and cookie-related settings consistently with the HTTPS address. Configure board permissions using a normal member account as well as an administrator. Turn on the registration controls appropriate for your community.

Suppose the chosen forum address is https://community.example.com/. Use that exact hostname throughout this test, replacing it with your real forum URL. Do not assume a successful administrator login proves ordinary member sessions work.

1. Open the canonical HTTPS address in a fresh private window and sign in as a test member.
2. Open a forum, a topic and the member profile. Confirm navigation remains on the intended hostname and the account stays signed in.
3. Follow a notification link delivered by the forum and confirm it returns to the same installation.
4. Sign out, refresh a member-only page and confirm the private session is no longer available.

If the login disappears during navigation, compare the configured board URL and cookie scope with the actual browser address. Review those settings before reinstalling the forum or resetting unrelated accounts. Test plugins separately if the clean forum works but an added extension does not.

Test sign-in, sign-out, a new discussion, attachment upload and notification delivery. Verify that private forums remain private to guests and ordinary members.

A sign-in loop can come from an incorrect forum URL or cookie configuration. Check those values and caching before resetting accounts or reinstalling the database.

Keep files and data together in your recovery plan, test application updates in a copy when practical, and review logs after deployment. If installation fails, record the exact error, selected application/PHP versions and destination path before retrying.

• Choosing and managing applications with Softaculous
• Planning a migration from an older forum
• Troubleshooting email delivery, spam placement and authentication records
• Creating Web Hosting backups and planning a restore
• Installing XMB and checking the first setup
• Installing phpBB and checking the first setup

• Softaculous installation workflow
• Softaculous forums catalogue