Cannot enable mod_rewrite - CentOS7 on DigitalOcean

ron_jeremy

I just fired up a CentOS7 Droplet, and then installed a LAMP stack by following these instructions:

https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-centos-7

I see the "Testing 1,2,3..." page when I visit my server's IP address, so I assume everything to be working fine. However, when I try to enable mod_rewrite, I see the following error:

[user@server conf]$ sudo a2enmod rewrite
[sudo] password for user:
sudo: a2enmod: command not found

After much searching I found this Apache help document but it's just way over the top for me to understand:

http://httpd.apache.org/docs/2.4/mod/mod_rewrite.html

What am I doing wrong?

flame

ron_jeremy I suggest you to read this article: https://www.digitalocean.com/community/tutorials/how-to-set-up-mod_rewrite
"a2enmod: command not found" did you install apache2? Did you install it globally?

jordanjay29 StackOverflow or the apache support site might be better options

What's the apache tag for?

jordanjay29

This isn't an installation question, really (this is a server configuration question, for which there are much better resources out there), but I had a free moment.

https://linuxacademy.com/blog/linux/enabling-mod-rewrite-on-apache2/

a2enmod is just a move tool. So you can simply move the files manually from the current location to the mods-enabled folder. Your file structure might be different than what the article describes, so investigate before you blindly use commands, please.

If you have other troubles, this really isn't the place to discuss server setups. StackOverflow or the apache support site might be better options. Once you have your server working, we'd be happy to help you get Flarum setup.

jordanjay29

flame Apache vs Nginx, because setting up Flarum's mod_rewrite rules have specific settings for different servers. It's not for setting up the server.

Kulga

I believe a2enmod is a debian specific implementation.
Debian has this thing where there are two config files, sites-available and sites-enabled.
You're supposed to place config files in sites-available and then sym-link them to sites-enabled when once ready for use. a2enmod (and a2dismod) are simply methods of quickly linking and unlinking the files in sites-available

Because you're using CentOS, the file structure may be different.

Essesntially, you'll want to make sure your config file for the site is being read by having a include line for it in the main config file. Probably located somewhere in /etc/apache2/*conf (sorry haven't used apache in awhile)