This didn’t solve the issue. I read online that many users suggest changing ownership to www-data group, but when I check available groups with:
getent group | cut -d: -f1
I don’t see www-data listed anywhere. What am I missing here? How can I properly set the file permissions so WordPress can write its config file during installation?
check your /tmp dir permissions too. wordpress writes temp files there during setup, and if that fails, wp-config won’t get created. also try sudo setenforce 0 to disable selinux temporarily - i’ve seen it block file creation even when perms look fine.
Hit the same issue moving from Ubuntu to CentOS on my dev server. WordPress couldn’t write to the directory despite correct ownership - turned out the parent directories were blocking it.
Run ls -la /var/www/ and check if your html folder lets apache create files. I had to fix parent directory permissions, not just wp-site.
Double-check your Apache config too. Look for AllowOverride All and make sure the Directory block covers your wp-site path. WordPress needs proper Apache directives to write the config file - file permissions alone won’t cut it.
Manual WordPress setups are a nightmare. I’ve hit this same problem on different Linux distros - it’s always something new. SELinux blocks, parent directory permissions, Apache configs, temp directory headaches.
I got tired of playing whack-a-mole with permissions, so I automated the whole thing. My setup handles all the annoying bits - finds your web server user (apache, www-data, whatever), fixes directory permissions on the full path including parents, sorts Apache directives, deals with SELinux, and builds wp-config.php with your database info.
It checks your LAMP stack first and rolls back if something breaks. No more guessing which permission combo works on your distro.
Just throw in your database details and target directory. Takes 3 minutes instead of hours debugging why WordPress can’t write one stupid file.
This is probably a Linux distro issue with your web server setup. If you don’t have the www-data group, you’re likely on CentOS/RHEL/Fedora where Apache runs as the ‘apache’ user instead of the Debian/Ubuntu standard.
Just fixing ownership won’t cut it though. Your web directory needs write permissions. Bump the directory permissions to 775 temporarily during install:
sudo chmod 775 /var/www/html/wp-site/
After WordPress creates wp-config.php, drop it back to 755 for security. I ran into this exact thing on my CentOS box and this fixed it. Also check your Apache config - make sure it actually allows file creation in that directory. Some distros ship with locked-down settings that block writes even when ownership is right.
Your Apache probably runs under a different user than you think. Run ps aux | grep apache to check which user it’s actually using.
Honestly, instead of wrestling with permissions, just automate the whole WordPress setup. I built workflows that handle fresh installs - all the permission headaches, config files, everything.
The workflow detects your web server user automatically, sets the right permissions, creates wp-config.php with your DB credentials, and sets up the initial admin user. No more guessing at chmod/chown commands or figuring out which user group your system needs.
Just plug in your database info and target directory - automation does the rest. Takes 2 minutes instead of hours debugging permissions.
maybe it’s a selinux issue? try sudo setsebool -P httpd_unified 1 & httpd_can_network_connect 1. also, check wp folder permissions; they should be 755 for dirs & 644 for files. gl!