I've decided to finally look more into this. After I click on the Go button it the Setup screen (like after an update to the PHP version), it appears to do some work and then just never responds back. I have to restart the Apache service to the site to respond again. When I check the Setup and Security logs.. they look as if it performed the setup correctly.

Digging into the Apache access logs I noticed this:

127.0.0.1 - - [14/Feb/2020:05:42:18 -0600] "GET /zp-core/setup.php?autorun=gallery&xsrfToken=38e11f75f3fbccf8dac16fcf8ac8201f3fc60323 HTTP/2.0" 302 -
127.0.0.1 - - [14/Feb/2020:05:42:19 -0600] "GET /zp-core/setup/index.php HTTP/2.0" 200 14847
127.0.0.1 - - [14/Feb/2020:05:42:19 -0600] "GET /zp-core/setup/setup.css HTTP/2.0" 200 5266
127.0.0.1 - - [14/Feb/2020:05:42:19 -0600] "GET /zp-core/images/warn.png HTTP/2.0" 200 691
127.0.0.1 - - [14/Feb/2020:05:42:19 -0600] "GET /zp-core/admin.css HTTP/2.0" 200 46153
127.0.0.1 - - [14/Feb/2020:05:42:19 -0600] "GET /zp-core/images/zen-logo.png HTTP/2.0" 200 1748
127.0.0.1 - - [14/Feb/2020:05:42:19 -0600] "GET /zp-core/locale/en_US/flag.png HTTP/2.0" 200 3233
127.0.0.1 - - [14/Feb/2020:05:42:20 -0600] "GET /zp-core/images/admin-buttonback.jpg HTTP/2.0" 200 778
127.0.0.1 - - [14/Feb/2020:05:42:20 -0600] "GET /zp-core/images/comments-on.png HTTP/2.0" 200 664
127.0.0.1 - - [14/Feb/2020:05:42:20 -0600] "GET /zp-core/images/burst.png HTTP/2.0" 200 613
127.0.0.1 - - [14/Feb/2020:05:42:20 -0600] "GET /zp-core/images/pass.png HTTP/2.0" 200 268
127.0.0.1 - - [14/Feb/2020:05:42:35 -0600] "GET /page/setup_set-mod_rewrite?z=setup&returnmode HTTP/2.0" 301 282

So, it seems to be triggering a 301 redirect but it never goes there. Mod Rewrite is enabled in Apache since all the .htaccess stuff works. Now, everything works fine on my webhost. This is just a local issue. Any idea where to start looking? I'll keep looking at things on my end.

I have not encountered this anyway. What I did encounter that sometimes the modrewrite check does fail althought modrewrite is active. There is sadly no real check via PHP or else for this so we use a fake ajax request to a modrewrite url to check.

Sorry to add to this old comment but this still happens with version 1.5.7 and latest version of Apache 2.4.52. Stops at the same line in the logs but the actual setup seems to work fine, I have to stop the Apache Service and restart it to get back into the gallery where everything seems to have gone fine.

Once again, this is only a local issue.

I suppose I could start the whole process over with a new database and everything to see if it fails with a fresh install as well. Make some kind of test gallery. Anyway, if you have any ideas that would be cool.

Thanks,
Mark H.

I still have not encountered this on any host I use… The last call above request the setup/setup_set-mod_rewrite.php page using a rewritten URL /page/setup_set-mod_rewrite/ to check if rewriting works. Sadly there is no other way to check if this works.

Not sure where the 301 redirection comes from above.

The check call is done via a setup class method on line 748 defaultOptionsRequest() via cURL.