Skip to content
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

Some people met with white screen after attempting to login #2062

Closed
Aaronsss opened this issue Nov 24, 2016 · 11 comments
Closed

Some people met with white screen after attempting to login #2062

Aaronsss opened this issue Nov 24, 2016 · 11 comments
Labels
status: testing required Someone needs to confirm this issue's existence and write a test to prevent the fix from regressing. type: bug A problem that should not be happening
Milestone

Comments

@Aaronsss
Copy link

I have reports now of two individuals who are unable to login on the site. They are met with a white screen after clicking login and are not logged in. What I / they have tried:

  • They have tried using both firefox and chrome
  • They have cleared cache and cookies
  • One guy tried it on 4 diffrent PC's
  • I cleared site cache
  • I changed one of the user accounts passwords and managed to log in with it fine myself

I just cant think what else is causing it its strange that its only some users and that others can log in with the account.

@tgtje
Copy link
Contributor

tgtje commented Nov 25, 2016

Similar to #1870 ?

@Aaronsss
Copy link
Author

Potentially but I am unsure, sorry I meant to update this last night. I believe I have discovered the issue. The users IP's were banned for too many login attempts. Originally, I had assumed this not to be the case as the 'Banned users' section in the status menu in the admin area said there are 0 bans and also the users could still see the site as a guest. Is it worth having that menu fixed and potentially the ban thing too or is that intentional?

@Moc
Copy link
Member

Moc commented Nov 25, 2016

I believe I have discovered the issue. The users IP's were banned for too many login attempts.

Is it worth having that menu fixed and potentially the ban thing too or is that intentional?

If being banned is indeed the cause for the blank page behaviour, then this needs to be fixed. Especially if you can still visit as a guest. Testing required to see what exactly happens and see what improvements need to be made.

@Moc Moc added the status: testing required Someone needs to confirm this issue's existence and write a test to prevent the fix from regressing. label Nov 25, 2016
@Moc Moc added this to the e107 v2.1.3 milestone Nov 25, 2016
@Moc Moc added the type: bug A problem that should not be happening label Nov 25, 2016
@CaMer0n
Copy link
Member

CaMer0n commented Nov 25, 2016

Please add define('e_DEBUG', true); to your e107_config.php file. Does it display any messages (other than a white page) ?

@Aaronsss
Copy link
Author

No debug information is displayed when trying to login through the bootstrap menu or the login.php page.

@CaMer0n I have messaged you about it on Gitter.

@CaMer0n
Copy link
Member

CaMer0n commented Dec 1, 2016

If there are no ban messages.. one needs to enter some here (if they desire)
/e107_admin/banlist.php?mode=main&action=times

@CaMer0n CaMer0n modified the milestones: e107 v2.1.3, e107 v2.1.4 Dec 23, 2016
@IAmCainey
Copy link

IAmCainey commented Jan 14, 2017

I have this issue @ #2275 i did the debug and it just say your ip is banned

@Moc Moc modified the milestones: e107 v2.1.5, e107 v2.1.4 Jan 17, 2017
@Moc Moc removed the type: bug A problem that should not be happening label Jan 17, 2017
@MikeyGMT
Copy link
Contributor

MikeyGMT commented Jan 29, 2017

One of my sites saying the same .... I appended the filename it was looking for: cache/banactions.php
There isn't one. I could not find my IP in the other two banlist files or the table either.
The filename appears to come from
iphandler_class.php line 92
const BAN_FILE_ACTION_NAME = 'banactions';
#1975 suggests that banactions is incomplete.

ed: fyi there were new IPv6 entries, and I have checked but I don't yet have v6 IP.
ed2: aha, but e107 thinks we do have IPv6.

@MikeyGMT
Copy link
Contributor

I got e107 to show my IP by adding this after line 177.
echo ($this->ourIP);
Commented my IP from the banlist table and the two ban files in the system/a1B2c3/cache folder.

I suspect logged in using a browser saved old password. I reset my password in the database - using the md5 action. Then re-logged in and updated the password. All working.

@CaMer0n CaMer0n modified the milestones: e107 v2.1.5, e107 v2.1.6 Mar 21, 2017
@Moc
Copy link
Member

Moc commented Apr 17, 2017

@Aaronsss Is this issue still happening?

@CaMer0n CaMer0n modified the milestones: e107 v2.1.6, e107 v2.1.7 Aug 10, 2017
@CaMer0n CaMer0n modified the milestones: e107 v2.1.7, e107 2.1.8 Dec 24, 2017
@Moc Moc added the type: bug A problem that should not be happening label Feb 28, 2018
@CaMer0n CaMer0n modified the milestones: e107 2.1.8, e107 2.1.9 Jul 18, 2018
@CaMer0n CaMer0n modified the milestones: e107 2.1.9, e107 2.2.0 Aug 22, 2018
@JoniPeti JoniPeti mentioned this issue Nov 2, 2018
@Moc
Copy link
Member

Moc commented Jan 16, 2019

I am assuming this issue is fixed. If not, please let me know and I'll re-open.

@Moc Moc closed this as completed Jan 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: testing required Someone needs to confirm this issue's existence and write a test to prevent the fix from regressing. type: bug A problem that should not be happening
Projects
None yet
Development

No branches or pull requests

6 participants