Page 2 of 2

Re: An update on what has been going on...

PostPosted: Fri 31 May 2019 02:53
by Elminster
Cralis wrote:Can anyone else confirm?

So far logged in for more than 3 hours on Chrome, even without deleting cookies.

Edit: Still logged in after 12 hours.

Re: An update on what has been going on...

PostPosted: Sat 01 Jun 2019 02:43
by Elminster
Automated login also working fine.

Re: An update on what has been going on...

PostPosted: Sat 01 Jun 2019 12:17
by aramis
Cralis wrote:I think that the login issue has been fixed!

I ran into a bug report for phpbb relatibg to secure cookies, looked at the code and verified we had the bug... and fixed it! I have remained logged in for 12+ hours now on Chrome and Firefox.

You may have to clear the cookies if you have multiple windows with separate sid values; but then it should work normally.

Can anyone else confirm?

P.S. I don’t think this will impact the SSL protocol errors a few of you are getting... I am still working on that.

Nope. Not fixed.

Happened again, same as before. the same cannot deliver a secure connection

And no, it doesn't auto-swap back to HTTPS.

Re: An update on what has been going on...

PostPosted: Sat 01 Jun 2019 20:23
by Cralis
It seems like the changes over the last week have fixed almost everyone's problem. Aramis and one other guy who has emailed me are getting SSL PROTOCOL errors. Both of you are using Chrome, although he's in Win8.

I did some looking into that specific error and there are some settings on your local machine that could interfere. This guide seems to be the most comprehensive and easiest to understand. I sent it to the other guy; Aramis, could you try these changes and see if they help in your case?

https://www.drivereasy.com/knowledge/so ... or-chrome/

Re: An update on what has been going on...

PostPosted: Sun 02 Jun 2019 16:02
by aramis
Can't follow them, Cralis - things aren't in the same spaces.

No certs stored. No sites set in the hosts file.

I am, however, getting HTTPS today... but note that the link on the login success to go back to previous page hung. No specific SSL errors, but the URL specified port 80.... it's unusual to specify a port. And, of course, it timed out.

Re: An update on what has been going on...

PostPosted: Sun 02 Jun 2019 16:04
by aramis
and, posting the previous, I got...
Server error!
The server encountered an internal error and was unable to complete your request.

Error message:
Premature end of script headers: posting.php

If you think this is a server error, please contact the webmaster.

Error 500
www.starfiredesign.com
Mon Jun 3 00:02:40 2019
Apache


Can't blame server errors on Chrome.

Re: An update on what has been going on...

PostPosted: Sun 02 Jun 2019 23:36
by Cralis
I was out today but I did post a ticket with the host for the 500 server errors, I started getting them this morning about once every 10 times I hit the site.

They are equivocating... but we'll keep on it.

Re: An update on what has been going on...

PostPosted: Sun 07 Jul 2019 23:34
by Cralis
Interesting, those errors went away and now they came back in the last couple of days. I am working with IT personnel from our host. I do give them props for being nice and actively trying to figure out the issue.

But it's been inconsistent. Has anyone else been having 500 errors in the last few days? Are you still? Can I get a screenshot or two immediately after you get it? (need the timestamp in a screenshot) ... also is anyone getting slow downs at certain points in the forum? Where?

Re: An update on what has been going on...

PostPosted: Mon 08 Jul 2019 02:26
by aramis
I've not seen the 500's this weekend...

The port 80 error didn't recur on tonight's login. but I used the bottom login link sunday afternoon, and the header one just now.