Answered Cannot browse site unless logged into Manager - ERR_EMPTY_RESPONSE

Hi all,

MODX Revolution 2.5.7-pl

I can not browse my site (currently in development) unless I am logged into the Manager in the same browser session.

Any attempt to visit the site in a browser without a Manager tab logged in results in a long wait followed by:

This page isn’t working

yyy.zzz.net didn’t send any data.
ERR_EMPTY_RESPONSE

This happens from all locations and all browsers that I have tried.

My host (shared platform) looked at this and replied:

I think there is a problem with the script as it seems to be looping trying to open files in the '/home/yyy/zzz/htdocs/abc/core/cache/resource/web/' directory, eventually timing out.

There may be some sense in this as I guess non-logged-in users will be served from the cache, logged-in users would not. My understanding of the cache is limited.

I have cleared the MODX cache, flushed permissions to no effect.

I am somewhat stuck as to where to go from here. No new entries appear in the MODX Error Log after these page-load fails.

I have also started with a brand new installation of MODX on a separate server, restored the database from the original site and still witness the same behaviour.

In all cases everything is fine with a manager-logged-in browser session.

Because I had had my own browser logged into a manager session for some months before noticing this issue, the prospect of locating a working backup and losing subsequent changes is not particularly appealing as it stands!

Any contributions, thoughts or questions most welcome and apologies if I have missed any vital info.

Chris

I should perhaps also have mentioned that cache files appear to be being successfully created in the '/home/yyy/zzz/htdocs/abc/core/cache/resource/web/' directory as and when resources are edited / successfully viewed:

1.cache.php
2.cache.php
3.cache.php

... etc ...

Are you clearing the cache from within the MODX manager? This is not always successful.

If possible try the following...
1. Log out of the MODX manager
2. Access the /home/yyy/zzz/htdocs/abc/core/cache/ folder via FTP or SSH and deleting everything inside it.

Thanks for your reply Andy.

Interestingly, I didn't have permission to delete the folders & files in the cache folder - either via my host's CP or via FTP.

I reset ownership of all the items within (via my host's CP) and was then able to empty the folder.

Sadly, no difference in the serving of pages.

All cache files seem to have been repopulated successfully after me logging back into the manager and browsing the front end.

Chris

Since clearing the cache have you tried with a different browser, or cleared the cache of the browser you are using?

Are permissions set as...
Folders 755
Files 644 (with the exception of the config file which should be 400)

I guess the best way to see if its a looping issue caused by a custom snippet or something else would be to set the homepage to a blank template with the text 'hello world' and then see if you can view the homepage ok.

Thanks again Andy.

Have re-checked on various browsers and always have an incognito Chrome window open to check as well.

Without checking through every file & folder - it looks like folders are 755 and files are 644 as you say.

My config file seems to require 440 rather than 400 for the site to work.

Interestingly, with it set at 400 - I do get the "Could not load MODX config file." error even on a not-logged-in browser.

Chris

Quote from: lkfranklin at Jul 13, 2017, 04:26 PM

I guess the best way to see if its a looping issue caused by a custom snippet or something else would be to set the homepage to a blank template with the text 'hello world' and then see if you can view the homepage ok.

Good shout LK - just tried it, but same deal, new page is visible when on a logged-in browser session, ERR_EMPTY_RESPONSE error when not.

Chris

Could it be caused by an error in your .htaccess file? What happens if you rename you file to ht.access?

Ok so its not a snippet error. I would suggest next trying to run the MODX setup which will also check file/folder permissions for you and point out any errors. Have you altered any contexts or permissions on the site at all for users?