Constant logging out

  • Hi-
    I've recently noticed an issue with one of my Perch sites where I am constantly being logged out of Perch. I go into the back end, make a change, get logged out. Log back in, navigate to another page, and I'm logged out. There doesn't seem to be any pattern to why I'm getting kicked out. All my users are experience something similar. Any suggestions?

  • We haven't purposefully changed anything in the hosting environment, but it's using a shared hosting with Network Solutions so they may have. Looks like it is running 3.14 so I could update and see if that helps. I'll see if I can get access to the server error logs.

  • I had the same problem with a site on Network Solutions in fact. My gut feeling is that it is a NS problem because the site worked on other environments flawlessly. We were not able to track down the problem and NS didn't seem to be very helpful.


    Good luck with getting error logs because that was a problem on the site I worked on. They didn't appear to be generated in the location that was indicated by the control panel.


    Let me know if you find an answer.

  • :( I was worried this would be the problem. I have had multiple issues using Perch on NS and they've never been helpful. Luckily, I've been able to move all our other sites over to a different hosting provider. THis one is 'stuck' there because the client prepaid for 5 years and the project manager doesn't want to switch. I'll let you know.

  • So, I did notice that it's currently running on PHP 5. If I switch to PHP 7, the perch runtime.php cannot be found. Switching it for some reason changes the document root. Any suggestions on what I can do to get it running on PHP 7?


    Here's the two different diagnostics


    Perch: 3.1.5, PHP: 5.6.17-pl0-gentoo, MySQL: mysqlnd 5.0.11-dev - 20120503 - $Id: 3c688b6bbc30d36af3ac34fdd4b7b5b787fe5555 $, with PDO

    Server OS: Linux, cgi-fcgi

    Installed apps: content (3.1.5), assets (3.1.5), categories (3.1.5), perch_blog (5.6.1), perch_events (1.9.5), perch_forms (1.12)

    App runtimes: <?php $apps_list = array( 'content', 'categories', 'perch_blog', 'perch_forms', 'perch_events' ); ?>

    PERCH_LOGINPATH: /perch

    PERCH_PATH: /data/2/5/74/155/5400970/user/6467411/htdocs/perch

    PERCH_CORE: /data/2/5/74/155/5400970/user/6467411/htdocs/perch/core

    PERCH_RESFILEPATH: /data/2/5/74/155/5400970/user/6467411/htdocs/perch/resources

    Image manipulation: GD Imagick

    PHP limits: Max upload 100M, Max POST 100M, Memory: 64M, Total max file upload: 64M

    F1: 3b606135b33e6a102526838f4152a807

    Resource folder writeable: Yes

    SCRIPT_NAME: /perch/core/settings/diagnostics/index.php

    REQUEST_URI: /perch/core/settings/diagnostics/

    DOCUMENT_ROOT: /data/2/5/74/155/5400970/user/6467411/htdocs

    HTTP_HOST: njdotlocalaidrc.com


    Perch: 3.1.5, PHP: 7.0.2-pl0-gentoo, MySQL: mysqlnd 5.0.12-dev - 20150407 - $Id: 7e72f9690b1498a1bead7a637c33a831c0d2f655 $, with PDO

    Server OS: Linux, cgi-fcgi

    Installed apps: content (3.1.5), assets (3.1.5), categories (3.1.5), perch_blog (5.6.1), perch_events (1.9.5), perch_forms (1.12)

    App runtimes: <?php $apps_list = array( 'content', 'categories', 'perch_blog', 'perch_forms', 'perch_events' ); ?>

    PERCH_LOGINPATH: /perch

    PERCH_PATH: /data/2/5/74/155/5400970/user/6467411/htdocs/perch

    PERCH_CORE: /data/2/5/74/155/5400970/user/6467411/htdocs/perch/core

    PERCH_RESFILEPATH: /data/2/5/74/155/5400970/user/6467411/htdocs/perch/resources

    Image manipulation: GD Imagick

    PHP limits: Max upload 100M, Max POST 100M, Memory: 64M, Total max file upload: 64M

    F1: 3b606135b33e6a102526838f4152a807

    Resource folder writeable: Yes

    SCRIPT_NAME: /perch/core/settings/diagnostics/index.php

    REQUEST_URI: /perch/core/settings/diagnostics/

    DOCUMENT_ROOT: /usr/services/vux/apache/htdocs

    HTTP_HOST: njdotlocalaidrc.com

  • Hi- So we switched to a new host for testing. And we're still getting this issue. We have multiple Perch sites and this is the only one doing it. It happens now with multiple hosts, so not a hosting issue.

    I've noticed it happens when we have more than one person logged into the back end.