Seems to be working for me now.
New fault with forum threads over one page
<p><a href="https://www.swinglifestyle.com/profile/lookup.cfm?usercode=18535072">Goodenuff</a>,</p>
<p>This site is 24 years old and has multiple code bases. They did fix it the first time it was reported and what I tested worked. I didn't know about the other sections and I guess the developers missed it as well. After someone reported it again yesterday or the day before, they got it all fixed.</p>
<p>I know the site had issues in the past. We have done extensive work behind the scenes over the last few years to correct those performance issues. So if any of you get any consistent errors, you should report them and if they are not fixed within a few hours, report them again, especially if I say it is working. I'm not a liar. If I say it is working, it is because I am missing something. </p>
"No one told us it was still happening. It took a couple of minutes to fix."
I'm not responding for tbr but 7 days ago you stated the site was working on the issue so I'm guessing people didn't feel the need to report it again. People have been accustomed to this site taking a long time to correct issues- if they do get fixed.
2 days ago you stated it was fixed the day it was reported, that you didn't see the issue and almost immediately others told you it wasn't fixed.
Just sayin'
<p><a href="https://www.swinglifestyle.com/profile/lookup.cfm?usercode=17435002">tbrmskss</a>,</p>
<p>No one told us it was still happening. It took a couple of minutes to fix.</p>
<p>I think what happened is that the pagination of the main forum sections was fixed. I checked that and it was working so I thought the issue was fixed but the pagination of the individual threads was still not working. </p>
<p>If any of you see an actual error message that persists, you need to report it and keep reporting it if it is not corrected.</p>
So it took six days to figure that out and get it fixed?
"What issue? We do not see any issues and no one is reporting any issues. This is a Forum issue? What exactly is happening?"
LOL
<p>Sorry it is still happening. I will follow up with developers tomorrow. It's because those pages have a hard coded port 80 after our domain name. If you remove the :80 from that address, the page will load. </p>
<p>They have always been that way. We made some security updates last week, so port 80 gets blocked.</p>
The error is
This site can’t provide a secure connection we've site name sent an invalid response.
ERR_SSL_PROTOCOL_ERROR
This is on chrome on my mobile
When clicking on a page # in a forum post with multiple pages I get an error. Seems others are too
Still happening here Wayne, same as the day we posted this thread and messaged you. No change.
Yes, I have the same issue here as well, cannot go to page two or beyond.
<p>The issue that <a href="https://www.swinglifestyle.com/profile/lookup.cfm?usercode=31805590">travelers122227</a> reported was fixed the same day they reported it. I just checked again and all the forum pages are working for me.</p>
<p>What issue? We do not see any issues and no one is reporting any issues. This is a Forum issue? What exactly is happening?</p>
I still have the issue. Any ETA?
This website is like an old car...
Eventually it is prudent to spend the money on a new one rather than wonder what you are going to have to spend money on next...
"This website needs new coders, or it needs to shut down."
Is there a John Taffer (or Gordon Ramsay) for websites? I'd get Paramount Network just to watch "Website Rescue".
There were only two things that I came to this website for anymore.
The fora, which is now unusable, and the stories, which are now gone.
This website needs new coders, or it needs to shut down.
<p>We know the issue and are getting it corrected.</p>
Same here
Another new feature to enhance the user's experience...?
Any forum topic I click opens at page one as usual. If I select any other page number like page two or whatever the last page number happens to be,, I get the fault code "Secure Connection Failed". There is more to the fault code, but this site will not allow it here for some reason.

