amsgator

are cookies enabled in firefox?

https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences

If you have cPanel, login to your cPanel and open the file manager inside cPanel. At the top right corner there is a search box. Search for gmail.css and see if that file is on your server and if so what it is related to

Possibly your google translate widget?

I don’t understand where gmail.css is coming from…

If it is from a plugin, delete your cache and then try again

@willem.deboer if you cannot login to disable them in your dashboard just rename all of your plugin folders so they are not recognized by WordPress

@willem.deboer When I visit https://www.communsense.nl/ it sets the cookie for me so I’m not sure why it’s not for you.

I’m not sure what plugins you have running because you’ve got something running on your login page requiring the captcha. Disable all of your plugins and then try to login. There may be a plugin that is causing the issue.

No I didn’t visit the login page. When I visit the homepage of my site it sets a cookie so I figured his would too. I don’t have any fix going on my site other than the .htaccess redirect I posted.

When I visited the his login page it did set the cookie for me as well.

I just visited https://www.maiscashback.com/ and I’m not getting a cookie from https://www.maiscashback.com/ or https://maiscashback.com/ in firefox. Strange

@cam it sound like this is a fresh install and alfjmrodrigues hasn’t even been able to set his URLs in the settings because he can’t login. I’m wondering if WordPress isn’t looking for a cookie from https://maiscashback.com/ instead of https://www.maiscashback.com/

Does it let you set them during install? If so pass on this option.

Since he is accessing it from https://www.maiscashback.com/ it’s possible that is the issue.

@willem.deboer I got mine to work with just the wp-login.php commenting OR just the .htaccess redirect. I prefer the htaccess redirect since it’s not changing any core files that will be overwritten and flagged by wordfence

I have not tried more than one at a time. If you have more than one going at a time it might be causing a conflict

@alfjmrodrigues if this is a fresh install and you haven’t even been able to login to set your wordpress and site URLs, try logging in from https://maiscashback.com/wp-login.php (without the www). If that works you can set the URLs in the dashboard and go from there. It may be looking for a cookie from https://maiscashback.com/ and not https://www.maiscashback.com/

@cam I played around with both of my WordPress installations, and found that it does not matter if you have https://domain.com or https://www.domain.com set as the site URL and WordPress URL in the settings. You can use whichever you prefer.

What DOES matter, is that if you have the settings set to https://domain.com then you MUST login from https://domain.com/wp-login.php and if you have the settings set to https://www.domain.com then you MUST login from https://www.domain.com/wp-login.php. Let me know if you found something different.

The reason I posted the .htaccess redirect above is because my WordPress installations are not redirecting me from https://domain.com/wp-login.php to https://www.domain.com/wp-login.php (I have my site url and WordPress url set to https://www.domain.com) so I set it up so .htaccess does it for me.

@alfjmrodrigues try commenting out wp-login.php like you did in the video but remove the mu-plugins folder and the file inside. delete all the functions.php hacks if you made any as well, and try just the wp-login.php comments by itself. does it still throw the white screen?

If that doesn’t work, install 3.7 and set all the settings, including your wordpress address and site address set to in your dashboard, then upgrade to 3.7.1 and see if it let’s you login

Did you clear your cache and delete all your cookies?

If you are getting a white screen it sounds like more than a cookie problem to me, but I’m not a wordpress guru so who knows if it is or not.

You might want to try reuploading your theme files and the core files and checking your database. Also, deactivate your plugins by renaming the folders or backup the folders and delete them from the server and see if there’s a plugin causing it.

I’m not sure what gmail.css is, that sounds like something other than a wordpress core file?

It looks like @programmin is right. In my dashboard I have set the www-CNAME as the preferred and I get the cookie error when I access it with the non-www-CNAME.

If I go to https://mydomain.com/wp-login.php and try to log in (after deleting the cookie) it does not work. WordPress is not redirecting to the correct CNAME when I access the login page with the non-www CNAME.

After getting the cookie error it THEN redirects me to the www-CNAME which is why it lets me log in the second time.

However, if I manually type https://www.mydomain.com/wp-login.php it will let me login the first time and does not throw the error.

I was able to solve the issue by using .htaccess to force the CNAME I want since WordPress is not doing it for some reason.

# BEGIN Redirect non-www to www
	RewriteCond %{HTTP_HOST} !^www\. [NC]
	RewriteRule ^(.*)$ https://www.%{HTTP_HOST}/$1 [R=301,L]
# END Redirect non-www to www

If you prefer to use the non-www CNAME you can add this code to your .htaccess

# BEGIN Redirect www to non-www
	RewriteCond %{HTTP_HOST} ^www\.(.*) [NC]
	RewriteRule ^(.*)$ https://%1/$1 [R=301,L]
# BEGIN Redirect www to non-www

In order for this to fix the problem the CNAME you redirect to in your .htaccess must be the same CNAME specified in your dashboard. i.e., if you have specified https://domain.com in your dashboard, you need to redirect all www traffic to non-www traffic in .htaccess and vice versa.

So at least this solves it (at least for me) without editing any core files.

It might be, not sure. I think it’s more-so the htaccess file that gets generated when permalinks are turned on that fixes it. But I don’t want to hijack the thread with another problem