Unable to connect to WordPress

  • tomcmp

    (@tomcmp)


    10 months ago

    Hello,

    I can no longer access my administrator dashboard. I activated debug mode and got the following error messages:
    Cannot modify header information – headers already sent by

    I then checked that there were no white spaces before the <?php and I changed the encoding to UTF-8-BOM on the files concerned but nothing changed

    I tried deactivating my plugins, nothing changes
    I changed the theme (I can do it via Plesk even without admin access) and I no longer have any error messages since the previous error messages were from the theme file but I still cannot not log in. I no longer have any error messages, the login page just reloads when i try to log in.
    I tried to change the password using Lost Password? link but I don’t receive the password change email.
    I have cookies enabled on the site, the WordPress test cookie is present

    I don’t know what to do as I don’t get any error messages, any ideas?

Viewing 9 replies - 16 through 24 (of 24 total)
  • Thread Starter tomcmp

    (@tomcmp)


    I restored a backup before the problem appeared but that did not resolve the problem

    I haven’t touched the server but other people have access to it and were able to make changes

    Moderator James Huff

    (@macmanx)

    Ok, so that suggests to me that the problem isn’t WordPress.

    Are you sure that you cleared all cookies related to the domain in your browser?

    Can you try logging in from a different browser?

    Does anyone else have access to the site, and can they log in?

    Thread Starter tomcmp

    (@tomcmp)

    Yes, all cookies are deleted. I tried from other browsers or in private browsing but I cannot log in. No one else can log in but they have access to the site

    Moderator James Huff

    (@macmanx)

    Then I’d have to guess at this point someone made a change to the server configuration, since a restored pre-incident backup should of course function exactly as the site functioned pre-incident otherwise.

    Can they roll the server back to the configuration it was before this started?

    Thread Starter tomcmp

    (@tomcmp)

    Unfortunately no

    Moderator James Huff

    (@macmanx)

    They can’t rollback or there way no server change before this started?

    If there was a sever change before this started, what was it?

    Thread Starter tomcmp

    (@tomcmp)

    I can’t tell you if there have been changes or not on the server but in any case they can’t rollback

    Moderator bcworkz

    (@bcworkz)

    I changed the encoding to UTF-8-BOM

    UTF-8 is correct, but there must not be a BOM in the files. The BOM is the first 3 bytes in the file, in hexadecimal they are EF BB BF. They shouldn’t be there.

    It’s unclear if these would affect your login ability. Kind of a long shot, but have you tried simply directly going to your site’s /wp-admin/ page? Sometimes the redirect_to parameter in the login URL is incorrect and you can get stuck in an infinite login loop despite the fact you are actually logged in. By directly going to a back end URL, this breaks the infinite loop.

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    A BOM being present will absolutely prevent login. There is no case where an HTML page should ever produce a BOM.

    Basically, resave your text files that you edited recently with a no bom setting. You should never use a BOM under any circumstances when you’re editing text files that are also PHP.

Viewing 9 replies - 16 through 24 (of 24 total)
  • The topic ‘Unable to connect to WordPress’ is closed to new replies.