• Resolved alexrms

    (@alexrms)


    Get error…Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress…

    when attempting to login into admin

    Extensively searched Google and WordPress forums before posting this to no avail.

    Found posts dated back about a year and tried suggestions I read there. Did all the obvious things such as clearing cache and disabling plugins. Even renamed plugins folder temporarily to disable all plugins via FTP. Contacted host iPage and they dismissed the problem saying they can login ok. They are never much help anyway.

    Tried all browsers on several machines and uploaded fresh files in case of corruption.

    I can occasionally login with Safari for a short while then the problem returns.

    I installed my site at https://smoljanovic.eu/
    back in September 2014. This problem has been plaguing me since about 10 days ago and never before.

    my htaccess contents are…

    RewriteEngine on
    RewriteCond %{HTTP_HOST} ^www.smoljanovic.eu [NC]
    RewriteRule ^(.*)$ https://smoljanovic.eu/$1 [L,R=301,NC]
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    Can someone please help?

    Thanks,
    Alexander Smoljanovic
    https://smoljanovic.eu

Viewing 15 replies - 1 through 15 (of 28 total)
  • throws me a install screen right now.

    Thread Starter alexrms

    (@alexrms)

    Yes. That also happens far too often. I am told its because I have too many visits and the database can’t keep up.

    The fix for that was using the Wordfence falcon cache.

    I disabled all the plugins to rule out plugin problems and then of course, my site failed as well.

    I re-established the Wordfence cache as I momentarily was allowed to login admin using Safari.

    It took over 12 hours of trying to finally login again.

    Still can’t use admin with Firefox or Chrome.

    Site is ok to check now.

    Thread Starter alexrms

    (@alexrms)

    Update to my first post…

    I tuned the Falcon cache back since it didn’t appear to cause the login problem but configured it to not cache the WP test cookie.

    Not sure if I did that correctly, but here is the contents of the new htaccess file…

    #WFIPBLOCKS – Do not remove this line. Disable Web Caching in Wordfence to remove this data.
    Order Deny,Allow
    #Do not remove this line. Disable Web Caching in Wordfence to remove this data – WFIPBLOCKS
    #WFCACHECODE – Do not remove this line. Disable Web Caching in Wordfence to remove this data.
    <IfModule mod_deflate.c>
    AddOutputFilterByType DEFLATE text/css text/x-component application/x-javascript application/javascript text/javascript text/x-js text/html text/richtext image/svg+xml text/plain text/xsd text/xsl text/xml image/x-icon application/json
    <IfModule mod_headers.c>
    Header append Vary User-Agent env=!dont-vary
    </IfModule>
    <IfModule mod_mime.c>
    AddOutputFilter DEFLATE js css htm html xml
    </IfModule>
    </IfModule>
    <IfModule mod_mime.c>
    AddType text/html .html_gzip
    AddEncoding gzip .html_gzip
    AddType text/xml .xml_gzip
    AddEncoding gzip .xml_gzip
    </IfModule>
    <IfModule mod_setenvif.c>
    SetEnvIfNoCase Request_URI \.html_gzip$ no-gzip
    SetEnvIfNoCase Request_URI \.xml_gzip$ no-gzip
    </IfModule>
    <IfModule mod_headers.c>
    Header set Vary “Accept-Encoding, Cookie”
    </IfModule>
    <IfModule mod_rewrite.c>
    #Prevents garbled chars in cached files if there is no default charset.
    AddDefaultCharset utf-8

    #Cache rules:
    RewriteEngine On
    RewriteBase /
    RewriteCond %{HTTPS} on
    RewriteRule .* – [E=WRDFNC_HTTPS:_https]
    RewriteCond %{HTTP:Accept-Encoding} gzip
    RewriteRule .* – [E=WRDFNC_ENC:_gzip]
    RewriteCond %{REQUEST_METHOD} !=POST
    RewriteCond %{HTTPS} off
    RewriteCond %{QUERY_STRING} ^(?:\d+=\d+)?$
    RewriteCond %{REQUEST_URI} (?:\/|\.html)$ [NC]

    RewriteCond %{HTTP_COOKIE} !(comment_author|wp\-postpass|wf_logout|wordpress_logged_in|wptouch_switch_toggle|wpmp_switcher) [NC]

    RewriteCond %{HTTP_COOKIE} !test [NC]
    RewriteCond %{HTTP_COOKIE} !test\scookie [NC]
    RewriteCond %{HTTP_USER_AGENT} !test\scookie [NC]
    RewriteCond %{HTTP_USER_AGENT} !test [NC]
    RewriteCond %{REQUEST_URI} \/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)(.*)$
    RewriteCond “%{DOCUMENT_ROOT}/wp-content/wfcache/%{HTTP_HOST}_%1/%2~%3~%4~%5~%6_wfcache%{ENV:WRDFNC_HTTPS}.html%{ENV:WRDFNC_ENC}” -f
    RewriteRule \/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)(.*)$ “/wp-content/wfcache/%{HTTP_HOST}_$1/$2~$3~$4~$5~$6_wfcache%{ENV:WRDFNC_HTTPS}.html%{ENV:WRDFNC_ENC}” [L]
    </IfModule>
    #Do not remove this line. Disable Web caching in Wordfence to remove this data – WFCACHECODE
    RewriteEngine on
    RewriteCond %{HTTP_HOST} ^www.smoljanovic.eu [NC]
    RewriteRule ^(.*)$ https://smoljanovic.eu/$1 [L,R=301,NC]
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress
    ———————————–

    There is no change.

    Still no access via Chrome or Firefox.

    Any help would be appreciated.

    Thanks,
    Alexander Smoljanovic
    https://smoljanovic.eu/

    who told you install screen is there because of too many users. that is not at all a desirable behaviour. if database cant keep up it throws up a message ‘error connecting to database’.

    disable the cache plugins and clear their cache too.

    Thread Starter alexrms

    (@alexrms)

    iPage explained that WordPress redirects to install if too many database requests. They said the problem was WordPress not their server.

    If you look near the bottom of my sidebar, you will see…
    VISITORS ONLINE
    Most visitors online at one time were 598 on March 19, 2015 @ 11:33 am
    There are 2 Users online now.

    The site always fails when I get numbers like that.

    I can’t argue as I don’t know about such stuff. They asked me to read a large technival document about that but I hung up on the chat session when they couldn’t just explain it to me and wouldn’t help further.

    When I asked “Is that what did it?” they just kept repeating I should read the document.

    I initiated the chat with them the first time my site was down and kept redirecting to install screen.

    Anyway, that is not my concern now.

    I just want Admin access with Chrome and/or FireFox.

    Thanks

    Thread Starter alexrms

    (@alexrms)

    I habe cleared the cache hundreds of times and have explained that it was done in my first post

    ok, i missed that. cache plugin should be disabled else it again starts caching after we clear it.

    right now i can load https://smoljanovic.eu/wp-login.php?redirect_to=http%3A%2F%2Fsmoljanovic.eu%2Fwp-admin%2F&reauth=1 a login page appears, can you log in here? or you get cookie error here after entering username/password?

    iPage explained that WordPress redirects to install if too many database requests. They said the problem was WordPress not their server.

    this is not true.not sure why they will say like this.

    Thread Starter alexrms

    (@alexrms)

    I get the cookie error after logging in.

    This is what happens…

    ERROR: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.

    out of ideas now

    check this discussion
    https://www.ads-software.com/support/topic/cookie-error-when-logging-in?replies=117 niosus has posted a solution and seem to be workng for most of guys on thread

    Thread Starter alexrms

    (@alexrms)

    Like I said, I need to use the cache because my site easily fails when I don’t. Just as it did about 14 hours ago when you tried.

    It worked for months with the Wordfence falcon cache until about 10 days ago.

    Now it does not work with or without the cache.

    I read somewhere that the Wordfence caching reduces the need for many database requests and therefore prevents my site from totally crashing.
    I don’t see how I can blame the cache. It doesn’t crash when I use it. Should I not use Wordfence?

    Thread Starter alexrms

    (@alexrms)

    After the site came back up, it still took me over 12 hours to login using Safari because of the cookie problem.

    There is nothing about your error in the ticket system so I would venture to say that the issue is not in WP core. It could however be in your install.

    – How was your site installed? Using a installer or did you use FTP?
    – Does your host use Cloudfare or any server cache setup.

    If you have the ability to test on another server, I would do it. See if the problem goes away. $2.25/mo hosting may work but remember you get what you pay for.

    Taking a step back. If your host can log into your site (I am assuming you gave them credentials to get in), and you can, it is a server cache issue or OS./browser setup. If you did not give your host credentials, to test your login, they did not test it.

    You are using some plugins and widgets that may interfere with cookies and headers. Disable everything and revert back to the the twenty fifteen theme and check to see if the issue goes away.

    Thread Starter alexrms

    (@alexrms)

    Like I said in my first post, I checked the forums extensively and found the year old discussions.

    I went through all of it and found no help.

    Even tried uploading an old wp-login.php and commented out 3 lines to bypass test cookie check.

    It didn’t work.

    Thread Starter alexrms

    (@alexrms)

    Thanks.

    I gave host credentials.

    I renamed the plugin folder to disable everything in one shot.

    Yes, it was all tried

    Thread Starter alexrms

    (@alexrms)

    I installed using FTP

Viewing 15 replies - 1 through 15 (of 28 total)
  • The topic ‘Unable to login using Chrome or Firefox due to cookie error’ is closed to new replies.