When the Softaculous installer unpacks the files,
it often defaults them to permissions that prevent the application
from writing to its own config files during the initial wizard setup.
This causes the wizard to drop into a silent loop or hit
a 403 Forbidden / 500 Internal Server Error on API requests.
Here is how you can fix it and get past that screen.
»»» METHOD 1 «««
Correcting File & Folder Permissions (Recommended)
The app (e.g. Akaunting) needs write access to its core config files
and directories to complete the setup.
Log into your hosting control panel and open the File Manager.
Navigate to the directory where you installed the app
(e.g. public_html or a subdomain folder).
Update the permissions for the following files and directories:
.env file: Change to 744 or 755
(it often defaults to restrictive 600 or 644 which blocks the wizard).
config/ directory: Ensure the entire folder is set to 755.
config/settings.php and config/database.php
Ensure these are set to 744 or 755.
storage/ and bootstrap/cache/ directories:
Ensure these are set recursively to 755.
Permissions higher than 755 for directories or 644/744 for files
might trigger a 500 Internal Server Error.
Stick to 755 for folders and 744 for the .env file first.
Once changed, clear your browser cache (or open an Incognito window)
and attempt the login/wizard again.
»»» METHOD 2 «««
The .env Force-Bypass
If correcting the permissions still leaves you on the wizard screen
because the database migration was only partially completed,
you can set the app (e.g. Akaunting) to a state of install finished
by modifying the environmental variables directly.
In the control panel's File Manager, locate and edit the .env file
in your app's (e.g. Akaunting) main folder.
Find the line that says:
APP_INSTALLED=false
and change it to:
APP_INSTALLED=true
Save the file and refresh your browser. This will completely bypass
the setup wizard and take you to the dashboard or standard login page.
»»» METHOD 3 «««
Check for SSL Issues
Sometimes the wizard isn't failing because of files,
but because Softaculous configured the application to use https://
before you assigned all necessary SSL certificates.
If your browser console (F12 > Console tab) shows Mixed Content errors
or blocked assets, edit your .env file, change
APP_URL=https://yourdomain.com to http://yourdomain.com temporarily,
complete the wizard, and switch it back once your SSL certificates
are fully active.
