Horrible conditions tonight!!!

Slow,timeouts and for about 5 mins "Connection refused"

Im sorry but this host blows......... The one we were on before was MUCH BETTER!!!

Im sorry they lied to you TJ. You should call them up and threaten to leave if they dont give you better service LIKE YOU HAD BEFORE THIS "GOOD DEAL" they gave you...

Im sorry but its nothing good!!

I never have any issues. So it may be more than just the host.

I have experienced intermittent connection issues as well, at least three times this week between 11 and 11:30 PM each time.

What I've noticed is after composing a post and hitting the "reply" button, at times the little "roundy-round" thing just keeps going, and after a very long tome you get a "connection time out" message instead of the standard screen promising to take you to your post.

TJ in the past has mentioned that "dual post" problems are caused by "impatient posters", but my experience is that patience is no guarantee of a "pay out", either.

Frequently I notice this problem when some other member has made a reply to the same thread that my reply is composed for, with nearly identical post time. So it appears that some sort of collision is taking place.

Perhaps it's that age old ~pre-emptive vs cooperative~ multi-tasking dilemma?

Whatever it is, it blows.

No this site was quite fast and reliable before the host wanted to move this site to a different computer......

They always lie to people to make it sound like they are getting a bargain when in fact they are getting crap.......

The server was rebooting at the time this thread was created. That's the reason for the connection refused message. It takes 10-15 minutes for it to fully come back online sometimes. Those connection refused message aren't always related to the server. I see them on various sites I visit when my connection drops.

I filled out a trouble ticket today to see what they could do to improve things. They upgraded the RAM from 3 GB to 6 GB, so it should be in theory twice as fast with more memory. They rebooted and tweaked it several times, so that's the reason for the downtime and database errors earlier.

It feels a bit faster right now. The server load is good. When I clicked on View Today's Active threads, it displays them in 0.22 seconds. It used to take 3-5 seconds at times.

My main issues are with the time it takes for posts to make it in the database, editing thread titles and posts, moving/merging threads and the search engine.

Is anyone able to successfully complete a search across all forums? It seems like there is a 120 seconds timeout somewhere. I'm getting a 500 Internal Server error.

I did a search for Saturday Night Live on just the General Sitcoms board and it times out after 120 seconds.

Search General Sitcoms:
https://www.sitcomsonline.com/boards/search.php?f=27

Search all forums:
https://www.sitcomsonline.com/boards/search.php

running that search on General Sitcoms, after about 50 seconds of waiting, it threw up the "your search is in progress, please wait" advisory, and then immediately kicked out these results

https://i.imgur.com/ehapt6U.png

It seems like the search must have been underway during the long wait, and the "please wait" message came up only after the search had been complete... meaning there was about 50 seconds of not knowing if anything was working, until the "please wait" message appeared for all of one second, then the results appeared (fwiw)

What browser are you using? I've tested it in Google Chrome, Firefox and Edge with the same 500 error.

It's good the search is working if it's completed within 120 seconds. Anything that takes longer is still timing out.

...My main issues are with the time it takes for posts to make it in the database, editing thread titles and posts, moving/merging threads and the search engine...

Right, yesterday around 8am I tried to merge a thread, and got the Request Timeout 500 Server Error message after a long wait.

When I checked later, it had done the merge but didn't change the original thread to a redirect.

I'm thinking some database/server work may go on early in the morning.

What browser are you using? I've tested it in Google Chrome, Firefox and Edge with the same 500 error.

It's good the search is working if it's completed within 120 seconds. Anything that takes longer is still timing out.


The following presentation has been edited for content, to be able to fit in the screen, as well as in the timeslot allotted:


Sorry for the tardy reply, I got sidetracked with visitors.