Have you tried modifying your AllowOverride settings as suggested?

@mapkyca I forgot to specify that on the shared hosting environment on Dreamhost, it's not possible to edit your apache2.conf file, so that's not an option. In order for you to do so, you need to get a DreamCompute instance, or pay for a dedicated server.

I don't believe it's possible to change the AllowOverride directive anywhere else but in the apache2.conf file.

@voss https://httpd.apache.org/docs/2.4/mod/core.html#allowoverride may help?

I wonder whether rewrite is installed, but not necessarily enabled for your host.

If you're certain it is and you're convinced warmup is giving you an erroneous error you could try forcing the issue using the CLI installer: http://docs.withknown.com/en/latest/install/cliinstaller/

@cdn Hmm, No matter where I put the

AllowOverride All

directive int he .htaccess file, the site throws a 500 error.

I've tried putting it into the a Directory section, and also just putting it in the open, like I would normally do with

AllowOverride Indexes

for example.

Both result in HTTP 500 errors.

I suspect Dreamhost has done something to stop you from doing that.

Either way, it seems irrelevant since mod_rewrite seems to be working, as the vanilla .htaccess file works, including any new directives I've added to it, for example to always redirect http to https requests.

@voss DreamHost probably have that capability [locked down](https://httpd.apache.org/docs/2.4/mod/core.html#allowoverridelist).

iirc AllowOverride is verbotten in .htaccess, it has to be set in the central apache conf (for security reasons)

Do you get error logs with your DreamHost account? Are you able to see what shows up there when you get those 500 errors?

@benwerd when I place it as the first line in the .htaccess file, outside of any directives:

.htaccess: AllowOverride not allowed here

`` type directives are not allowed in .htaccess files, so whenever I put that in there, it simply says:

htaccess:

So, as @mapkyca says, and as I mentioned earlier, you can not change AllowOverride in .htaccess. You can only set it in the apache2.conf file. On Dreamhost, you can not change your apache2.conf if you are on shared hosting (which I am).

So, to get back to the issue, either Dreamhost has a non-standard setup, where they are able to hide the fact that mod_rewrite is installed and enabled, or the test being done by Known in the warmup section, to test whether mod_rewrite is installed and enabled, is missing something.

I'll happily take a look at the CLI installer, thanks for that @mapkyca,

NginX also suffers from the Rewrite test looping warmup due to some recent change(s) in master

Anecdotally, this appears to be a relatively new thing. Apparently the package on withknown.com does install, but newer packages don't. I guess this means I broke something when I rewrote the installer, although I can't for the life of me see what, or have any idea why it should only crop up on dreamhost.

That'd be quite helpful, actually. You can email me on marcus@marcus-povey.co.uk, my pgp key should be on the standard key servers or my website.

OK, I had a chance to check out what's happening. In warmup/WebInstaller.php, on line 41, is:

if (function_exists('apache_get_version')) {

I believe the function_exists call is returning false, so the rest of that if-clause isn't executed, and the function (with no explicit return) returns null.

Can't double check that is correct right now, I'll need to do so later today, but I think that's what's going on.

@ejheil and for Nginx it will never exist :o)

D'oh. Obviously.

Ok, I'll fix this shortly...

I've installed latest version of known: version = "0.9.9-a" build = 2019011501 on Debian stable

with the same error discribed above.

CLIinstall worked but the wrong .htaccess was distributed!

Then I've copyed manualy .httaccess-2.4.dist and renamed it. Also changed all left .htaccess files inside into "Require all denied".

The Apache known site-conf has " AllowOverride All" inside.

It seems like the Apache version info wasn't adequate for the Installer and the CLInstaller.

Now it stucks at https://blog.mydomain.tld/begin/ with "The requested URL /begin/ was not found on this server."

Maybe an bestpractice example apache2.4 site-conf could be provided in the documentation for better understanding of the requierements.

Thank you all

Still the same issue on DreamHost.

It was fixed, and then broken, and then fixed. We changed a lot of the JS recently, so try a bleeding edge build

Just tried a fresh install on nginx with php7.2-fpm and I'm in the same loop. Same issue with `-s dev`, which if I'm not mistaken uses the 'bleeding edge" code?