[Bob Kuczewski]

This time I got in with one try so I guess I'm getting better at hitting "Board Index" at just the right moment.

Frank

That's been what I've done. Unfortunately, I've adapted so well that I forget that it's a real problem to others. I am working on it today. Because it's a potentially critical setting that may need to be changed, I am trying to ensure that I can recover quickly if something goes wrong.

Thanks for everyone's patience.

[Bob Kuczewski]

Well ...
... let's see what happens ... again ... and again ... and again.

Moderators note: This post was used to continually test
whether various settings would fix the problem. With each
change of settings, the post was modified with another
"again" clause. None of these attempts worked, but
eventually the right combination was found a few
days later (see below).

[KaiMartin]

Just a quick note:
I don't experience any issues with logging in.
My browsers are firefox 60.8.0esr, waterfox 56.2.14 and chromium 76.0.3809.100 running on Debian/Linux Bullseye/testing.

Hope this helps,

---<)kaimartin(>---

[wingspan33]

Kai, Have you tried letting 2-3 seconds go by after you log in, but before you click to go somewhere on the forum? I've learned that a quick click on the "Active Topics" tab somehow prevents the problem. It could be you are a natural "quick clicker" and for that reason don't experience the problem.

I also experience the problem just after submitting a post. But, again, if I click quickly the error doesn't occur. Same deal when I log out. In that case I hit the "back" button and hit "log out" again - then quickly hit a link to some other part of the forum. Oddly, I have noticed that once I have hit the back button, if I refresh the page it actually indicates that I HAVE logged out.

The confusing thing about this issue is that it began right after Bob made the site https. That implies that the issue is buried somewhere in some detail of that change.

But if some members have no problems, then there are even more .

One simple possibility is that you and others are still gaining access to the site via the http address. I didn't know for a while that Bob had made the change and had no problems at all while my bookmark led me to the http version of the US Hawks. Everything worked fine. It wasn't till I switched over that the odd things began to happen. Obviously, Bob has also noticed the problems.

[KaiMartin]

Kai, Have you tried letting 2-3 seconds go by after you log in, but before you click to go somewhere on the forum? I've learned that a quick click on the "Active Topics" tab somehow prevents the problem. It could be you are a natural "quick clicker" and for that reason don't experience the problem.

I also experience the problem just after submitting a post. But, again, if I click quickly the error doesn't occur. Same deal when I log out. In that case I hit the "back" button and hit "log out" again - then quickly hit a link to some other part of the forum. Oddly, I have noticed that once I have hit the back button, if I refresh the page it actually indicates that I HAVE logged out.

The confusing thing about this issue is that it began right after Bob made the site https. That implies that the issue is buried somewhere in some detail of that change.

But if some members have no problems, then there are even more .

One simple possibility is that you and others are still gaining access to the site via the http address. I didn't know for a while that Bob had made the change and had no problems at all while my bookmark led me to the http version of the US Hawks. Everything worked fine. It wasn't till I switched over that the odd things began to happen. Obviously, Bob has also noticed the problems.

I experimented a little can confirm all of the above. Specifically:

• No problems at all if I use http as opposed to https. (The rest of the items refers to use of https URLs)
• After the login I get to a page that announces to send me to wherever the site thinks I was before. If I just wait it out, I get an error page.
• Everything is fine if I click on one of the buttons on top of the page within about 3 seconds.

The exact error messages depends on the browser.

Firefox:
Secure Connection Failed
An error occurred during a connection to ushawks.org:80.
SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

Chromium:
This site can’t provide a secure connection
ushawks.org sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

---<)kaimartin(>---

[Frank Colver]

Bob just called me and said he thinks he has it fixed. I just logged in and it worked

Frank

[Bob Kuczewski]

Bob just called me and said he thinks he has it fixed. I just logged in and it worked

Frank

I want to give huge credit to Scott for this fix.

Scott not only kept bugging me, but he put me in touch with an expert who helped me diagnose and solve the problem. Once again, the U.S. Hawks benefits from our great team of dedicated members.

Thanks to Scott for going the extra mile and then some!!







     Thanks Scott!

[wingspan33]

First I want to say thanks to Kai! You did some research that helped pin point the problem.

As far as Bob's, "THANK YOU", . . . Well, . . . You're Welcome!

But I must say I felt a bit like one of those guys with an electric cattle prod! I kept having to "zap" Bob it get him going. Then I had to bring in a cute heifer (the phpbb trouble shooter) to get Bob to go the last few yards.

In all fairness, Bob has lots on his plate right now, so it's probably great that this issue got fixed this quick.

BTW - In logging in I no longer have a problem. But when I go to submit this post I'll still have to see how that goes!

[wingspan33]

YEA! No problem in posting!

Hey, is that the Sun I see shining through the clouds?

[Frank Colver]

Now i can even click on the link in my email when I get one of those "someone has replied to your post" messages from Bob. Before it just sent me to the "no secure access" message.

Thanks Bob and those who helped along the way.

Frank