setup httpd on fc18 . starting fc18, new conf.modules.d is created to host all LoadModule directives with nn-.conf file convention to which set of modules to be loaded first. http://fedoraproject.org/wiki/PackagingDrafts/ApacheHTTPModules set up http on fc16 on FC16 with SELINUX on 1. Need to set UserDir public_html and /home/*/public_html in /etc/httpd/conf/httpd.conf properly. 2. Need to setsebool httpd_enable_homedirs true 3. Start httpd "service httpd start" 4. Enable access through firewall: "lokkit -p 80:tcp" 5. chcon -R -t httpd_user_content_t ~$login\/public_html When the upload.php gets "Possible file upload attack" or cannot create directory on /var/www/html directory, it could be caused by SELINUX. You can change the context chcon -R -t public_content_rw_t /var/www setsebool -P allow_smbd_anon_write 1 setsebool -P allow_httpd_anon_write 1 http://serverfault.com/questions/131105/how-do-i-get-selinux-to-allow-apache-and-samba-on-the-same-folder For suphp, you should change /etc/suphp.conf line 34 umask=0077 to unask=0022 if you want the directory to be read by apache or others. Problem encounter when setup httpd on fc14, Got (98)Address already in use: make_sock: could not bind to address 0.0.0.0:443 It is caused by duplicated Listen directive declaration. See the following web page. http://www.linuxquestions.org/questions/linux-software-2/98-address-already-in-use-make_sock-could-not-bind-to-address-0-0-0-0-443-a-110753/ I had this problem too. It turned out that i had the "Listen 80" directive in two config files: /etc/httpd/conf/httpd.conf /etc/httpd/conf.d/system-config-httpd.conf The latter comes from the Fedora Core system configurator for httpd. Removing "Listen 80" from httpd.conf solved the problem. I tried the above descriptions but I had noone listening on port 80 which got me confused. Cheers, Johan AH01617 Password mismatch htpasswd or .htaccess does not work http://stackoverflow.com/questions/15751242/apache-2-4-authentication-failure-password-mismatch bug in htpasswd Try htpasswd -b apacheticket username password interactive mode has bug. use -b option instead.