There's a duplicate thread in the Wanted section, however clicking on it gives an instant Error 500

I get the same result. Also, I did not see the subject duplicate highlighted as a new post.

All fixed.

Just one last reminder about tomorrow's temporary site closure. Read Post 189 for more details.

This may be the longest thread on the site. Hopefully after the shutdown it will trickle off to zero new posts.

It is the longest, yep. I am glad I introduced paging some years ago now, otherwise this page would indeed be very long.

Well, it's a test of paging, too.

It's a pity that clicking on the last updated by only works if there's one page.

Anyway, hopefully hear from everyone in a week.

It's a pity that clicking on the last updated by only works if there's one page.

Yes, an icon (e.g. arrow) that takes you to the latest post both at the thread and sub-forum levels would be a great feature rather than having to page through/scroll down but, given the current parlous state of affairs operationally, I don't hold out for that in the short term.

Yep, the first priority is to regain stability. I am hoping to get back on track with some new features but this won't get a look-in this year.

Guys, I admire that some of you wish to be here to the point where you try to evade the IP block on the front page but it's not helping with the repair work. If you do manage to get in, please do not put anything on the forums before the site re-opens. Your comments will not likely survive the repair process and as previously mentioned, me being the only one here will help with the repairs to the site.

Server Error
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.


Just a few minutes ago.

Brad,

Twice now I have observed that I can instantly clear the timeout problem if I reboot my modem.

I now suspect that the problem may be associated with SSL. (Come to think of it, I don't recall us having these timeouts prior to the site being converted to SSL.)

It would be interesting to see how the site runs without SSL for a period.

If I spend too long on a comment like 20 minutes or so I get a 500 when posting and it may or may not post
Moral: type fast and post!.
Fred.

Diverting all traffic back to port 80 was tried before Christmas but unfortunately without success.

It's all academic now though, as the new forums are under construction. I will be doing further work on the new database this weekend and will pretty much work on the project every second Sunday until we have new working forums.

Bah, I meant to type modem above, not server. I have fixed that.

So, my experience is that establishing a new IP connection to your server releases the lock-up. There must be a clue in that somewhere.