404 for all URLS but Home Page

[WLBentley]

I've installed ProcessWire following along the DigitalOcean Tutorial, although my server is running Ubuntu 14.04, and the web root is at /var/www/html, not /var/www. I cloned ProcessWire 2.7 from the GitHub repository instead of downloading a zip file.

I successfully completed the Install.php process, and un-commented # RewriteBase /. I've tested that mod_rewrite is installed.

(Though when the install process was complete, I still had to manually remove install.php, the site/install files, etc.)

I am unable to log in to the admin pages, because the link to /processwire/ returns a 404 error. Same for the About & Site Map pages on the Home (Basic) page.

I already followed the Troubleshooting Guide page for URLS Not Working, but nothing changed.

There is no errors.txt file in site/assets/logs/.

What can I do to get this working?

Thanks in advance for any help.

[ottogal]

Just guessing: Shouldn't you change    RewriteBase /     to     RewriteBase /html/   ?

[WLBentley]

52 minutes ago, ottogal said:

Just guessing: Shouldn't you change    RewriteBase /     to     RewriteBase /html/   ?

Well, I did try that and it still didn't work. The actual web root, which originally contained the Apache default index.html, is /var/www/html/. ProcessWire is not installed in a subdirectory. This is the directory structure:

drwxr-xr-x 4 root root  4096 Jul 23 03:23 ./
drwxr-xr-x 3 root root  4096 Jul 22 22:37 ../
-rw-r--r-- 1 root root   450 Jul 22 22:36 COPYRIGHT.txt
-rw-r--r-- 1 root root 11906 Jul 23 03:16 .htaccess
-rw-r--r-- 1 root root  7473 Jul 22 22:36 index.php
-rw-r--r-- 1 root root 17120 Jul 22 22:36 LICENSE.txt
-rw-r--r-- 1 root root 18781 Jul 22 22:36 README.md
drwxr-xr-x 5 root root  4096 Jul 22 22:49 site/
drwxr-xr-x 5 root root  4096 Jul 22 22:36 wire/

[fbg13]

Try to look at your log files /var/log on Debian (should be the same for Ubuntu).

[WLBentley]

13 hours ago, fbg13 said:

Try to look at your log files /var/log on Debian (should be the same for Ubuntu).

The apache2/access.log shows the 404s, but we already knew that.

66.255.234.225 - - [23/Jul/2016:16:58:58 -0400] "GET /site-map/ HTTP/1.1" 404 500 "http://138.68.10.209/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.7 (KHTML, like Gecko) Version/9.1.2 Safari/601.7.7"
66.255.234.225 - - [23/Jul/2016:16:59:01 -0400] "GET /about/ HTTP/1.1" 404 497 "http://138.68.10.209/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.7 (KHTML, like Gecko) Version/9.1.2 Safari/601.7.7"
66.255.234.225 - - [23/Jul/2016:17:05:40 -0400] "GET /site-map/ HTTP/1.1" 404 501 "http://138.68.10.209/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.7 (KHTML, like Gecko) Version/9.1.2 Safari/601.7.7"

nothing relevant in apache2/error.log, it just shows my restarts.

It seems to me something like this should be generating error messages in a ProcessWire log. But it's not.

 

[WLBentley]

Ok. It was a bad Apache config file setup. Problem solved.

Needed to use the correct config file (000-default.conf) and to have AllowOverride All set for the correct directory.

Thanks.