Log on troubles......

[Skitterbug]

Hi Hans,

Thanks for the email suggesting the https:// before Eileens website address. This worked for me! I appreciate the quick response and the solution!

Thank you!

[HansV]

Welcome back!

[viking33]

Hi Hans,

Thanks for the email suggesting the https:// before Eileens website address. This worked for me! I appreciate the quick response and the solution!

Thank you!

A hearty Welcome back from me also, Skitterbug!

[Skitterbug]

Hi Hans and Bob! Thanks for the cheery welcome back! I'm glad to be here! :)

[John Gray]

I had the same problem with using just http:// in Firefox 75.0.
Using https:// solved the problem.

Please could this info be put somewhere where the un-logged-on person could easily see it?

[HansV]

Hi John,

Thanks. I have added a remark to Login Problems; that thread is permanently displayed in the Lounge Portal.
Unfortunately, it doesn't work consistently - we had tried this when the problems first started, with mixed results...

[Doc.AElstein]

Just some passing info…
Using https:// before www.eileenslounge.com sometimes causes other issues
https://www.eileenslounge.com/viewtopic ... 53#p245767" onclick="window.open(this.href);return false;
https://www.eileenslounge.com/viewtopic ... 35#p255935" onclick="window.open(this.href);return false;

Playing around with https:// or http:// has not effected any of my occasional Login/Out problems so far ( I Use Internet Explorer or Google Chrome mostly ). But I will make a point of checking that again.

( Over the last few days I have consistently had the login/out problem from about late mid morning to midday German time. Mostly previously the problem effected me towards middle evening German time. As always the problem sorts itself out.)

[Nick Vittum]

phew!! I just got back in, after a 20+ hour lock-out. I missed it here.

[Argus]

I had the same problem with using just http:// in Firefox 75.0.
Using https:// solved the problem.

Please could this info be put somewhere where the un-logged-on person could easily see it?

I wouldn't say HTTPS solves anything in the long run. I've been using it for several years; maybe it had some impact, since it took some time for me to experience log in problems as reported by others, but I don't think so, there are so many other variables in the equation. Anyhow, the other day when we saw, eh, a lockdown, I couldn't login and post a reply at 1-3 AM, nor 9-10 AM. So I agree with Hans. (An un-logged-on person can see all posts, but perhaps not easily, so I agree it's good with information and some tips in a pinned thread.)

Just some passing info…
Using https:// before www.eileenslounge.com sometimes causes other issues

That has also been mentioned earlier, when several started using HTTPS.

[Argus]

phew!! I just got back in, after a 20+ hour lock-out. I missed it here.

Already addicted?
(I assume you didn't run under another nick in the old-old Lounge. )

[Nick Vittum]

Already addicted?

Or an-Nicked-ed

(I assume you didn't run under another nick in the old-old Lounge. )

Same Old Nick. . .

[Roderunner]

I used to be a member of Windows Secret Lounge till it closed down.
Today I got a free newsletter and found this of interest.

https://www.askwoody.com/forums/topic/u ... lp-please/" onclick="window.open(this.href);return false;
An anonymous reader is using the uBlock Origin browser add-on to block ads and filter content. But a prompt to update the tool has this forum guest concerned. Was the installed version of uBlock corrupt? Or was the update's request for permission to access host names and IP addresses legit? Those questions led to a long and interesting discussion.

Could this be affecting logging in to Eileen's???

[HansV]

I don't think uBlock Origin has anything to do with the login problem. The problem affects all browsers on all platforms, regardless of which add-ons have been installed.

[BobArch2]

Up to two days ago, April 8, 2020, I have never had a single issue related to logging in or being logged out by the system. This being on two different platforms ... using FF and Chrome on the PC and Safari on the iPad. And always using the HTTP:// format.

After seeing the reference to https:// and being a brave soul, I changed my 1Password sign on credential for The Lounge to reflect the security format and gave it a whirl. Voila, it worked nicely.

Then I decided to post a note referencing the version of Chrome. When checking for the version, Chrome elected to update itself. Which also required a refresh. After doing the refresh, I tried to log back into The Lounge only to be stymied and I became a member of the illustrious "log-in-problem-group". Tried for the better part of 30 minutes and left to do other things. But refused to go back to old ways.

Using the iPad the next day, all was well ... no issues. Today, Friday, tried on the PC using Chrome and again, no problems.

Perhaps updating Chrome the other day caused a momentary glitch. <shrug>

[HansV]

The problem is very unpredictable!

[Nick Vittum]

I'm glad to see the move to a new server. Recently, it has seemed that I've been locked out more than allowed in. But still— a lot of work for you folks. Your time and work are very much appreciated!

[John Gray]

Moving to a new server? Work of a moment!

PS Might this fix the error messages I get when pressing Submit on a reply in FF 75.0 at the top left of the screen?

Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /big/dom/xeileenslounge/www/includes/utf/utf_tools.php on line 1784 Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /big/dom/xeileenslounge/www/includes/utf/utf_tools.php on line 1784 Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /big/dom/xeileenslounge/www/includes/utf/utf_tools.php on line 1784

[HansV]

Hi John,

You get that (harmless) error message when you use https. The Lounge will be transferred "as is", so I'm afraid it won't get rid of the message.

[Argus]

I'm glad to see the move to a new server. Recently, it has seemed that I've been locked out more than allowed in. But still— a lot of work for you folks. Your time and work are very much appreciated!

Moving to a new server? Work of a moment!

PS Might this fix the error messages I get when pressing Submit on a reply in FF 75.0 at the top left of the screen?

Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /big/dom/xeileenslounge/www/includes/utf/utf_tools.php on line 1784 Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /big/dom/xeileenslounge/www/includes/utf/utf_tools.php on line 1784 Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /big/dom/xeileenslounge/www/includes/utf/utf_tools.php on line 1784

Why would a change of IP address change anything related to how the forum works in these aspects? We have done a couple of moves during the years without anything changing; on the other hand, we have also at other times changed, upgraded or otherwise tweaked the forum software. It has been mentioned that the login problems probably are related to the forum software, and probably in combination with something else.

I know nothing (as Manuel), but I imagine that if we are lucky the forum won't be as slow on the hour, or similar, when emails are sent. That, and perhaps depending on how far it is moved, some might get a bit lower latency.

[John Gray]

Why would a change of IP address change anything related to how the forum works in these aspects?

It's slightly more than a change of IP address! New (virtual) server, perhaps running Linux rather than Windows (maybe, or vice versa) on a different hosting company.

But I agree that no sensible Systems Administrator would even think of changing or updating the Lounge software at the same time as a server move!