-
-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
phplist logs me off instantly #1038
Comments
Ah, that's interesting. A workaround for now may be to remove the phplist_admin_login table in your database. That will need some investigation to find out what's causing that. |
If you can add a line here: https://github.com/phpList/phplist3/blob/main/public_html/lists/admin/index.php#L336 something like print $remoteAddr; exit; and then reload the page, can you post the output? You may need to do a view-source if you get a blank page. |
Hey @michield! One thing I forgot to mention in my bug report: It worked with the previous version of phpList we used, which was 3.6.14 I think. I don't think the settings of my ISP changed in the meanwhile. It works for my colleague who has a IPv4 public IP. |
Ok, are you only using IP6 to connect? I did add a column for IP6, but it's not in use at the moment. I guess we need to detect the IP4/6 and store it in the correct column and then use that instead.
Yes, this is new functionality. As common with web-apps, for security purposes it will now (a) detect a login from a new IP and (b) alert about it. |
This issue has been mentioned on phpList Discuss. There might be relevant details there: |
When I try to log in to the admin panel and click on anything, I am logged out automatically and receive the following error message:
"Your session was invalidated by a new session in a different browser"
When I log in again I see this error on the top of the page
"Database error 1406 while doing query Data too long for column 'remote_ip4' at row 1"
Is phplist not yet IPv6 ready? Is there a workaround?
phpList version 3.6.15
The text was updated successfully, but these errors were encountered: