New install, can't access pages other than Home, can browse subdirs

[codevark]

Hi, I'm having an issue similar to: https://processwire.com/talk/topic/9421-installation-error/#entry90700

ProcessWire installed in /pw/. I've tried the SymLinks stuff and all combinations of the Rewrite stuff. No change. I can't get to Admin, About, or Sitemap pages.

Apache/2.2.15 (CentOS) Server at Port 80 (my own in-house webserver)

Also, I can browse to /pw/site, /pw/wire and see everything in the filesystem. Same for the unused site- dirs (which I thought were supposed to get deleted by install?)

[AndZyk]

Welcome codevark,

uncommenting line 124 in the .htaccess-File, for setting the RewriteBase to "/", as stated in the thread you posted didn't solve the problem?

Usually this is the problem when a new ProcessWire install is hosted in a subdirectory.

Regards, Andreas

[Martijn Geerts]

Is the .htaccess in place?

Second question: Are the other site profiles still in there?

When the second question is Yes, PHP is probably not allowed to write.

More information about permissions: https://processwire.com/docs/security/file-permissions/

[codevark]

@Andreas - nope.

@Martijn - .htaccess is there and, the other site profiles are still there. Apache seems to be running as Apache, not root. If I look at the /pw/ dir, everything it it is owned by root. Files are 644, dirs are 755. Should I change owner, permissions, or both?

Updated: However.. in config.php, the chmod settings are files 666, dirs 777.

[Martijn Geerts]

It looks like a permissions issue.

Are /site/assets/logs/ & /site/assets/sessions/ empty ? 

If so php can't write, but it need to. 

Probably better when others join this discussion, because I'm far from expert in permissions.

[codevark]

/pw/site/assets/logs contains modules.txt and system-updater.txt.

/pw/site/assets/sessions contains a single sess_... file.

[Martijn Geerts]

Oke...

Could you open your .htaccess and type: agfagergwtuh8rh at the top (or something).

When that results in a 500 your .htaccess is working at least.

[AndZyk]

I had the experience, that on one server I needed to set all permissions in the "site/assets/file"-folder to 777 in order to keep my ProcessWire install running.

Although I highly wound't recommend it, because you would make your site vulnerable. A good server set-up wouldn't need such workarounds. But I am no expert in permissions as well.

[codevark]

ah.. that's it. adding garbage to .htaccess had no effect. So, I need to mess with httpd conf?

in httpd.conf, the directives for default / are:

Options FollowSymLinks

AllowOverride None

and for docroot (/var/www/html/) are:

Options Indexes FollowSymLinks

AllowOverride None                                               <------- CHANGING THIS TO "ALL" FIXED IT.

I tried changing this to AllowOverride None: for / this had no effect, for docroot, it hosed everything*.

*probably because I still had garbage in .htaccess? Once I took the garbage out, back to square one. ..uh...

wait, SOLVED, forgot to restart httpd that last time, sorry. all working now, thanks!!!

(and, now I can't browse those subdirs that I shouldn't be able to look into..)

[Martijn Geerts]

Could you try:

AllowOverride All
Options Indexes MultiViews FollowSymLinks
Require all granted

Happy to hear it's working ! Edited October 5, 2015 by Martijn Geerts
Added happy to hear...