I am developing a custom theme for our Drupal based website, and I needed to log out to check on the look of the site for an anonymous user.
Once I logged out, I could not log back in. I tried several admin accounts, on several computers, and none of them worked.
Thankfully, my laptop loads the website logged in as admin. From there, I can clear the cache (as well as with drush), and I can see the server logs as well.
Interestingly enough, when I attempt to log in as a user, the logs show that a session has been opened for that person, but the browser on the user side just refreshes back to the home page and does not log the person in.
My admin skin is set to Bluemarine, so unfortunately that isn't the issue. I also changed the sites theme to Garland, and I still have no luck logging in with any other login or computer.
I am thinking my next step will be to revert to an earlier version. Although, it would be great to find out what I did to break it so I don't do it again.
try surfing to http://your_domain/user
it will take you to the login page.
Related
Background:
I have a WordPress website that lives in a Google Cloud-based load balanced environment, and as I work through getting CI/CD setup I elected to isolate one of the servers so that my team could properly run through isolated testing. Since the website is on a regular domain (www.mybusiness.com), I created a duplicate database from our production DB and pointed the isolated server at this new test database. From there, I updated both the 'siteurl' and 'home' values with the isolated server's IP address in my wp_options table, and from there I can access my isolated WordPress site by simply using the URL. However, this is where things get frustrating: the login page simply refreshes after a successful login attempt, while blatantly incorrect login attempts with invalid credentials properly return user login error messages.
After countless hours searching the Internet, Stack, and elsewhere, I've found that the most common solutions are either:
Clear your browser's cookies / cache.
Try logging in with completely different devices (other cell phones, laptops) to confirm it's not a device or local browser-cache issue.
Deactivate and test each plugin,
Confirm your 'siteurl' and 'home' values are correct.
Test your .htaccess file to confirm that's not the problem.
Clear your user's WordPress 'session_tokens' meta_key value.
Revert back to an older / default WordPress theme to confirm if it's a theme problem
Run WordPress's built-in DB repair tool.
Create new WordPress salts and swap them in inside the wp-config.php file.
Enable the 'WP_DEBUG' constant to see if anything in the error logs pops up.
Test non-HTTPS versions of 'siteurl' and 'home'.
After trying all of the above, nothing seems to work: reverting to an older theme (twentynineteen) still presents the same login page refresh issue, and I've gone through every plugin on the server to see if deactivating one or all of them creates a solution - none seem to be the root cause. Error, mysql, and auth logs are also maddeningly clean.
Interestingly, if I add a trailing slash to my IP address-based 'home' and 'siteurl' value, from 'https://11.11.11.11' to 'https://11.11.11.11/' I do successfully get to the correct internal landing page (https://11.11.11.11/landing-page/) - however it just displays a 404 with the basic white screen.
Current WordPress version: 5.4.7
This leaves me with a few questions:
Is this a file permissions issue somewhere? Are there any key WordPress files in which permissions could create this effect?
Would Apache or anything VPC be in play here? I checked out our Apache .conf files, but those don't seem to be the suspect.
Should we look into a WordPress upgrade knowing we're a bit behind with 5.4.7?
Thank you in advance for the help!
I have an major problem with xenForo Logins on nginx and tried everything foundable out.
The xenForo is not the problem it workes fine on an other apache server but I need to move it to nginx.
I'm using the newest nginx and php7.1, php-fpm and all requested sources for xenForo are installed. Other Sites (like Roundcube) works fine. I use the default site config for all sites with - so far - no problems.
Now, for the problem. When I logi to my xenForo ACP the login works fine but I get immediately logged out. Some times I get logged out a few minutes later, when I change the site. On the user site the login works pretty fine als long as I stay on the forums pages (as the forum, member page, profiles) and get logged out when I use a 3rd party site programmed by me (worked fine on apache without problems).
The xenForo Filesystem is owned by www-data:www-data and chmod permissions are set correctly.
In the php.ini file I set the correct path for the sessions to /var/lib/php/sessions and with an external simple script I proved that the sessions are saved correctly with no problems.
No errors displayed.
As long as I can say, everything works fine just the Login makes real trouble and I get out of ideas.
Maybe someone here can help me and find something I didn't see.
Kind Regards,
//Edit:
I found out that this Problem Not appears on the user site if the "Keep me logged in" button is ticket. Ob ACP there is no such button.
//Edit:
I found out, that the Cookie didn't get dropped, it's still there.
//Edit:
The timezones are correct.
I'm not so good in explaining my problems so if you find anything wrong I apologize for it.
So my problem is that in my web site I have 6 modules-super, manager, sales, cashier, technical support & client. If I open all of them in chrome or in firefox & login anyone of them it doesn't effect other modules. But when all of them are logged in & when I logout from one of them all of those modules logout.
This doesn't happen while login but why it happens while logout?
I cannot post my code, sorry.
Whatt should I do?
Any help would be great.
Thanks.
Edit: I forgot to mention, but my website is running on localhost. Its not online.
It's likely that you're storing a single login token for all sessions logged in and when the user logs out, that token is removed and revokes access for each browser. It would be better to set cookies to maintain login state.
Since I can't see your code, I can't give you a more specific answer.
So I'm completely new to working with WordPress and I've had to figure this out by watching YouTube videos and reading articles. I'm not a programmer, all I really understand is HTML & CSS.
So I finished the site on the localhost and I tried to upload it to my hosting service. I created a database and my hosting provider walked me through on creating a subdomain. After that was completed I logged into the admin side of to redirect the URLs. Once I clicked 'save' it logged me out and when I tried to log back in it gave me this error "ERROR: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress." However, the cookies are enabled and the site is live in its subdomain. When I go to test.mydomain.com it works, there's a few things broken but it's showing up. For example, when I click a link it takes me to a localhost url but if i click on the link again it takes me back to the test.mydomain.com url. Plus, when i go to the admin site it's still giving me the error. I have no idea how to go about fixing this. I tried to figure it out but I don't really understand since I'm not familiar with WordPress. Please help!
Using symfony framework 1.4 I have created a website. I'm using sfguard for authentication.
Now, this is working great on WAMP (windows). I can login to several accounts on different browsers and use the website.
I have ubuntu server 9.10 running apache (everything up to date and default configuration). On my server, when I login to the website in one browser it works great. When I on my other computer login with another user account on the public website, the login is successful. But when I refresh/go to another page the first user is shown as logged in instead!
Also, when I press logout, It's not showing that I'm logged out after page load. When I press f5 again I'm logged out.
As mentioned, all this works as expected on my local installation. I'm thinking there something wrong with my PHP session configuration on my ubuntu server, but I've never touched it..
Please help me. This is a school project and I'm presenting it today :(
It's unlikely to be the session handler (certainly not the problem if you are using the default handler). Top of my list of things to check is whether you are sending out the right caching information in the authenticated pages (i.e. either no-cache or Varies: cookie).
C.