WordPress admin panel times out

  • Good morning,

    While I am working in the WordPress admin panel I run into a sporadic situation where the WordPress system becomes unavailable. I get a timed out message.

    During that time I delete cookies and history, but the system doesn’t respond. However, if I wait approximately ten minutes the system returns to normal. I do not have to log in; I have full functionality.

    If I remember correctly, this started happening after I upgraded. I have since re-installed the new version and I continue to experience the time out issues.

    Please share your thoughts.

Viewing 14 replies - 31 through 44 (of 44 total)
  • Thread Starter papaburke

    (@papaburke)

    Another update.

    I swithced themes from Weaver Xtreme to Twenty-sixteen. I wasn’t able to re-create the time out with 2016. I switched back to Xtreme and I was able to time the system out.

    Once I have access again I will switch back to 2016 to see if I can time it out. Please note, one test doesn’t prove anything.

    Please continue to share your thoughts.

    Thread Starter papaburke

    (@papaburke)

    Okay guys,

    I switched back to 2016 and I could not get the system to time out. I went back to Weaver Xtreme and received this error message:

    Warning: require(/var/www/vhosts/forgottenthymefarm.com/httpdocs/wp-content/themes/weaver-xtreme/inc/template-tags.php): failed to open stream: No such file or directory in /var/www/vhosts/forgottenthymefarm.com/httpdocs/wp-content/themes/twentysixteen/functions.php on line 353

    Fatal error: require(): Failed opening required ‘/var/www/vhosts/forgottenthymefarm.com/httpdocs/wp-content/themes/weaver-xtreme/inc/template-tags.php’ (include_path=’.:/usr/local/php54-cgi/pear’) in /var/www/vhosts/forgottenthymefarm.com/httpdocs/wp-content/themes/twentysixteen/functions.php on line 353

    I reloaded the Weaver Xtremem theme and it activated successfully. I was able to time the system out again.

    Could this be theme related?

    Very strange but what just happened seems to point to that. Did you contact Weaver support?

    Thread Starter papaburke

    (@papaburke)

    What about the error message; what does that mean? Does it identify the cause?

    I just posted this on Weaver’s forum.

    The error message basically shows the Weaver theme got corrupted. That is why reloading it worked.

    Is it possible your site has been compromised?

    @Wordfence I checked with Sucuri yesterday and they showed nothing.

    The web scan? That doesn’t check much and can’t examine site source code.

    @papaburke One of our guys can check if it’s compromised if you’re interested and will clean it for you. No charge. If you want to have us check if you’re compromised, email genbiz at wordfence dot com and let them know I sent you (I’m Mark Maunder).

    We do site cleaning commercially, mostly for the forensic data it gets us which we build into Wordfence in the form of the Threat Defense Feed. I don’t want to spam the forums with a link because it’s a paid service, but you can google it for more info.

    Mark.

    Thread Starter papaburke

    (@papaburke)

    Good morning Mark,

    Thank you for the offer; I appreciate it.

    I sent your team an email this morning and I asked for an understanding of the process and potential outcomes.

    Take care,
    Bill

    The web scan? That doesn’t check much and can’t examine site source code.

    Sucuri has long been a reliable way to check for hacking.

    This is theme specific. You need to let Weaver know what you found when you switched themes.

    Hi,

    I’m having a similar situation and wanted to share my observations in case these help in identifying the problem’s cause.

    The two similarities I have are:
    – I just upgraded my WordPress to 4.7.1 (I have 3 instances on the same server)
    – I just upgraded the Wordfence plugin to 6.2.10 (3 instances too)

    The error I’m getting is “Webpage not available. The webpage at https://<myserver&gt; could not be loaded because: net::ERR_CONNECTION_TIMED_OUT. My hosting provider is liquidweb.

    – My problem is sporadic when I’m working from home, it gets fixed after 4-5 clicks.
    – It’s happening in more than one network (with desktop and an android phone in a remote network).
    – In the android case, it is not sporadic. The user has been unable to access for a couple of hours now. However, I have other concurrent users working without issues (on a third location).
    – This is happening at the admin and end-user levels

    From my 3 instances, the one I’m having problems with is my “production site” (the other two sites are for development and testing). The only difference between the sites is that the production site 1) has more users, 2) is available as a mobile application (although all the code related to the mobile part is running on a separate location).

    I hope that helps. I just sent a note to my hosting provider to request an investigation. If that doesn’t help, I was planning to “turn off” two of the 3 sites I’m running.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    @mraminini

    Please start a new thread for your issue rather than “me, too”ing onto an existing one. Thanks.

    I don’t have a different issue. I’m getting the same thing everyone has been talking about here. I just wanted to share my observations in care they were useful to someone working on it.

Viewing 14 replies - 31 through 44 (of 44 total)
  • The topic ‘WordPress admin panel times out’ is closed to new replies.