My problem: Users don't get further from login screen. They show up as logged-in in the manager log and Whos online, but the login screen just shows an empty login-form after submit login.
It all worked for several days after last upgrade to 2.7.0.pl, and then suddenly stopped.
Error log: (ERROR # /home/verkejml/public_html/core/model/modx/moduser.class.php : 362) PHP warning: session_regenerate_id(): Cannot regenerate session id - session is not active.
Tried:
Delete all files in core/cache.
Delete browser cache and cookies.
Different browsers and different users with different permissions, up
to admin.
Reading all forum questions about the same problem, no luck.
I have one admin user logged in, and I'm super afraid to log out that user, if I'm not able to login again, and therefor can't access the manager again.
My setup:
Modx Revo 2.7.0pl.
Just a few "standard" extras installed, all updated.
PHP 7.0.33
Question: Is there anything I can do without reinstall everything, and by that be forced to log out my only logged in user?
I got the answer from the incredibly engaged and knowledgeable problem solver in the Modx community, BobRay:
My (old) settings:
session_cookie_path => (blank)
anonymous_sessions => No
Changed to
session_cookie_path => /
anonymous_sessions => Yes
Thanks to BobRay for great help!
Well, there are any problems with MODX 2.7 + PHP 7.* nowadays.
Here are other possible steps which may help you:
Disable anonymous_sessions setting and relogin again
Remove modSessionHandler value for session_handler_class and relogin again
I have one admin user logged in, and I'm super afraid to log out that user, if I'm not able to login again, and therefor can't access the manager again.
Honestly I don't know how to test without logging out ((
Related
Recently, some colleagues have started working in my team, so I showed them the basics of drone, but when they wanted to access our drone server they get that message:
Login Failed. User limit reached
We login via Github and they have access to the repositories. In fact, one of them did commit something which run the job without any problems, he just could not see it as he could not login. Any ideas on why does he get that message? I have checked our configuration and it doesn’t seem to have any limit to the number of users on drone.
Looks like I reached the limits of the trial license.
I checked the limits of my current license at the /varz URL (eg. https://cloud.drone.io/varz)
Also, about the users seats and repos: https://docs.drone.io/enterprise/usage/
I have developed a website in Drupal 8 and have deployed it to production. I have created 7-8 other accounts for my content management team and have granted them limited privileges for creating, editing and deleting content.
Of late, I am facing a problem with the user login form, wherein the login works sporadically. Sometimes I am able to log in as the administrator in the first attempt, sometimes I am not. In the latter case, I have to reset my password via email using the reset password option. However, this approach works only temporarily for a single session, which means that as soon as I log out, I am unable to log in. My content managers are also experiencing the same problem.
I have tried the below things but no luck.
Truncating the flood, session, and all the cache tables and flood table manually from the database.
Disabling the Recaptcha module in the login form.
Enabling and disabling the HTTP Basic Authentication module.
Disabling server proxy configuration through the settings.php file.
Performing Drupal updates by running the update.php file.
The incorrect username and/or password error in the login has not been handled. When an incorrect username/password is entered the page only refreshes without displaying any custom message.
Edit: I have just observed that I had luckily forgotten to log out as the super admin on the site from another browser, Firefox. I investigated further to fix this problem and observed a pattern. I am able to login as the administrator when I manually clear the cache from Firefox (where I luckily forgot to logout). However, this works only for one session, which means after logging out the bug reappears. In order to make the login to again work as expected, I have to again clear the cache from Firefox.
Okay, after much banging my head over the wall for nearly a week, I have found a workarpund solution to this problem by uninstalling Internal Dynamic Page Cache and Internal Page Cache modules.
The problem was that the user login form was getting cached after one successful login. Using the Chrome developer tools the following response header was getting set and sent by Drupal.
X-Drupal-Dynamic-Cache: HIT
To elimnate this I had to uninstall the above two modules.
However this is just a workaround and not a solution, since disabling these two modules will have a tradeoff with the site performance.
Anyone who knows the solution to this problem, please post it here. I shall try them and update this space.
Thank you in advance.
I had issues in local environnement with a custom Login form too. The behaviour was different because for me.
It was the first login attempt just after clearing the cache drush cr that would fail, even if in the logs it was recorded that the user was successfully logged.
I fixed it in my Controller, by using a bit of code from the Core core/modules/user/src/Plugin/Block/UserLoginBlock.php
$form = $this->formBuilder()->getForm('Drupal\user\Form\UserLoginForm');
$placeholder = 'form_action_p_4r8ITd22yaUvXM6SzwrSe9rnQWe48hz9k1Sxto3pBvE';
$form['#attached']['placeholders'][$placeholder] = [
'#lazy_builder' => ['\Drupal\user\Plugin\Block\UserLoginBlock::renderPlaceholderFormAction', []],
];
$form['#action'] = $placeholder;
$build['user_login_form'] = $form;
We want to run two Jenkins instaces on the same server.
To log in Jenkins (using version 1.595) web GUI we are using the LDAP plugin (version 1.11). "Project-based Matrix Authorization Strategy" is selected and my user is granted admin access here. So once I am able to login I have admin rights. The symbol to the left of the users added in the matirx shows a "little man" so the user seems to be found on LDAP.
CASE 1: If I type in my credentials CORRECT I get redirected
to the page that was open just before I clicked the "log in" button.
NOT good -> Without allowing anonymous user to administrate I have no chance of doing anything.
CASE 2: If I type in them WRONG Jenkins tells me "Invalid login information. Please try again."
good -> as expected.
Also tried "Anyone can do anything" as security setting. Using this I do not get redirected to the login form, but to the last visited page from where i called the "login".
It does't matter what type of Internet Explorer I use. The result is always the same (Chrome, Firefox and Internet explorer were tested).
I already discussed with the colleague responsible for the LDAP maintenance. The incoming information are handled correctly (-> LDAP settings within Jenkins must be correct). But this fact is clear since wrong login information leads to "Invalid login information page", but correct login information do not.
Also made sure that the firewall makes no problems.
Do you have any idea why this is not working? Or what the reasons could be?
Is it possible that there is kind of a "redirection link" for logins?
Hard to say from the information you've provided, but one thing to check is that the casing on your username exactly matches the name you have set up in matrix authentication. LDAP is not case sensitive but Jenkins is, which means that you can be authenticated successfully without having the administrative access you are expecting.
One way to proceed would be to add the 'authenticated' (case sensitive) user to your matrix with some limited permission set and see whether you are able to get past the login page.
I found one reason!
After deleting the environment variable JENKINS_HOME I was able to login into Jenkins... At least via localhost. Before even this login wasn't possible too. As we run two instaces of Jenkins on the same Server it seems like they want to use the variable both -> leads to failures. But if I try to login via network from another PC I still can't login (same as before). The variable JENKINS_HOME gets set (as before) within the jekins.xml in jenkins installation folder so the enironmentvariable is properbly not in need. I opend a new question, as this is now an Apache error.
I guess the reason why I can login via localhost, but not via network must be our Apache 2.2 server which is handling information wrong. By using localhost I can bypass Apache (-> works) but via network Apache gets used (-> don't work).
Link to the new question: Jenkins behind Apache Server / Can't log in Jenkins
Clean install Magento 1.8.1. (2 hours old) I experienced the Magneto application booted off two separate users simultaneously on two separate Chrome Browsers(PCs) once I enter the Paypal tab to set up a new configuration on a clean install of 1.8.1. Do not remember if I got to save any Paypal edits. I had been in the back end editing for than 2 hours. I set the session time out at 36000 early on in the setup. Now it appears to give me as session id but will not allow access to the back end. It just keeps showing the login form after providing the correct credentials. Nothing in logs, cookies were wiped, cache cleared, even tried FF and observed the same effect.
Find the following code in /app/design/frontend/package_name/theme_name/template/persistent/customer/form/login.phtml
and put this line below the ablove code :
getFormKey(); ?>" />
I've been unable to login to my site for weeks and weeks now. I've tried everything I can find on forums and still no joy (eg: viewtopic.php?t=719540).
A few weeks back my Joomla site backend became unavailable with the error message "Unable to connect to LDAP server".
I have not updated or changed the site in quite a while. It just started happening. So I've ruled out anything I have done.
I will say the exact steps I have taken:
In phpMyAdmin, accessed 'jos_extensions' and then 'plg_authentication_ldap'. Changed 'enable' from '1' to '0'.
Accessed 'jos_extensions' and 'plg_authentication_joomla' and ensured it was enabled. ie '1'.
Accessed 'jos_users' and found out I'd been hacked with many new users (with names like 'habxnkxl') had been added. All passwords were changed to things like 'jnsnbjhbx'. I removed all the unwanted users and changed all passwords for users.
Followed the steps in 'how to recover your password page' (http://docs.joomla.org/How_do_you_recover_or_reset_your_admin_password%3F) and created a new super user 'admin2'.
edit
Now, 'repaired' jos_extensions, jos_users and deleted plg_authentication_ldap.
I've consistently been re-checking the login throughout the process, on firefox and safari, and still get the same "Unable to connect to LDAP server" error message. Even when I have turned off 'plg_authentication_ldap".
Your help in this matter would be greatly appreciated.
Thanks,
Nicol
Joomla 2.5
Set :
Client id 1
Enabled 1
Access 1
This worked for me :)