• Resolved SaraCravewordpress-40

    (@saracravewordpress-40)


    Hi

    I’m getting the following message when trying to log into the CMS using Chrome browser;

    Fatal error: Maximum execution time of 180 seconds exceeded in /websites/bl/blog.saracrave.com.au/wp-includes/Requests/Transport/cURL.php on line 162

    I’ve tried in IE browser, and got the following message;

    503
    Service Unavailable
    The server is temporarily busy, try again later!

    I’v contacted the hosting provider (netregistry.com.au) and they say there is no problem with overload on the server.

    Running on litespeed server using PHP 7

    I’m not sure how to resolve this, so any help is greatly appreciated.

    Lenny

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hello @saracravewordpress-40

    Please add this code in config.php set_time_limit(180);

    Important: Paste before

    /* That's all, stop editing! Happy blogging. */

    Hope this will help.

    Thanks.

    Try deactivating plugins until you’re able to log in. Since you can’t do this from the admin, being locked out and all, you can do this via FTP by connecting, going to the wp-content/plugins folder and renaming the plugin folders one-by-one, attempting to log in between each one. Renaming a plugin folder essentially deactivates it.

    If you can identify the culprit, rename all your plugins back to what they were (except the one that’s responsible), log in and re-activate them. Then contact the plugin developer for further assistance.

    Thread Starter SaraCravewordpress-40

    (@saracravewordpress-40)

    Hi @wbcomdesigns
    thanks for your advice.

    I’ve followed your suggestion to edit the config.php but still getting the same error message.

    Puzzles me, because I haven’t recently changed anything in the site, and I haven’t added any new plugin either

    Any other thoughts

    Regards

    Lenny

    Hi @saracravewordpress-40

    Go to this file: wp-includes/deprecated.php and find this line in (deprecated) wp_get_http() function:

    @set_time_limit ( 60 );

    comment this line.

    Try reviewing this:
    https://codex.wordpress.org/Common_WordPress_Errors#Maximum_execution_time_exceeded

    Hope this will help.

    Thanks.

    • This reply was modified 8 years, 9 months ago by wbcomdesigns.
    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    @wbcomdesigns, Thanks for helping out, but I have to raise that this is a core file and should not be touched.

    @saracravewordpress-40 Did you try my advice? The error is occurring in a core file, but it’s in a function that plugins would use. You’d be better off figuring out if the issue is with one of your plugins than simply increasing the time allowed for whatever’s already taking far too long.

    Thread Starter SaraCravewordpress-40

    (@saracravewordpress-40)

    Hi @jakept

    Sorry I didn’t respond sooner, I’m in Aus and needed to sleep. I’ve worked through the plugins today. Unfortunately I am using quite a few, and was near the end before I found the problem.

    It was securi

    Perhaps because I also had Wordfence installed. I have delected securi and now everything seems to be working fine.

    Thanks very much for your assistance. I appreciate the help!

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘problem logging into CMS’ is closed to new replies.