The Lemon Fool

It is dreadful right now
practically unusable

I an thoroughly frustrated about the slow or no response on the site. Once again this morning after many attempts I have managed to get the site to open but I cannot get it to open the second page to find the original thread on this matter hence this new thread. Could someone please fix this?

Dod

No access 6:55am to 7:35am

AiY(D)

No access 6:55am to 7:35am. This post not being registered

AiY(D)

Normal 7:55am

AiY(D)

It's up and down like a yo-yo

Very slow response. 8:45am May 3rd and the occasional

"This site can’t be reachedThe web page at search.php?search_id=newposts might be temporarily down or it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR"

monabri wrote:Very slow response. 8:45am May 3rd and the occasional

"This site can’t be reachedThe web page at search.php?search_id=newposts might be temporarily down or it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR"

Here too. Lately this website has been close to unusable for periods. Occasionally I get a timed out error. If the website is on a shared server, the owner might have to consider subscribing to a dedicated server. I had to that when I was admin for a very popular website. It outgrew the shared server subscription. One snag is on shared web servers it is often other websites bad code consuming server resources but it affects other perfectly good websites hosted on the same server.

monabri wrote:Very slow response. 8:45am May 3rd and the occasional

"This site can’t be reachedThe web page at search.php?search_id=newposts might be temporarily down or it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR"

It's slow again

AiY(D)

Fluctuating between 20 seconds and 30 seconds to open a page now for me now.

Site is effectively unusable.

About 30 seconds to come onto the site or flip a page.

V8

I said on the other thread, if the TLF website is hosted on a shared server, the best fix IMO is to move it onto it's own dedicated server. I had to do that myself when I ran a popular website as you're a hostage to fortune on a shared server. Of course, if TLF is already on it's own server, it needs a good course of looking at.

I won't be using it very much today
WHAT is wrong with it

pje16 wrote:I won't be using it very much today
WHAT is wrong with it

I agree again. Why are the owners not apologising at at least advising us what they are doing about it? They must read posts from time to time surely ?

Dod

Dod101 wrote:

pje16 wrote:I won't be using it very much today
WHAT is wrong with it

I agree again. Why are the owners not apologising at at least advising us what they are doing about it? They must read posts from time to time surely ?

Dod

Remember the owners set this up as a part-time hobby and a service to the ex Motley Fool community. It's not as if it's run by a company taking our subscription fees.
It's been good for the vast majority of the time, so I think we should cut them some slack at the moment, and thank them for all the time the site has run flawlessly
doolally

doolally wrote:

Dod101 wrote:
I agree again. Why are the owners not apologising at at least advising us what they are doing about it? They must read posts from time to time surely ?

Dod

Remember the owners set this up as a part-time hobby and a service to the ex Motley Fool community. It's not as if it's run by a company taking our subscription fees.
It's been good for the vast majority of the time, so I think we should cut them some slack at the moment, and thank them for all the time the site has run flawlessly
doolally

Agreed but there now ads all over it and some of us do pay voluntarily to have those removed. It is in the owner's interests to get the site up and running properly again or the number of hits will drop off and probably have already which will affect the advertising rates n the longer run.

Anyway, even if no apology (which is not important) I would have thought that the owners might have told us what is going on.

Dod

Dod101 wrote:

doolally wrote:Remember the owners set this up as a part-time hobby and a service to the ex Motley Fool community. It's not as if it's run by a company taking our subscription fees.
It's been good for the vast majority of the time, so I think we should cut them some slack at the moment, and thank them for all the time the site has run flawlessly
doolally

Agreed but there now ads all over it and some of us do pay voluntarily to have those removed. It is in the owner's interests to get the site up and running properly again or the number of hits will drop off and probably have already which will affect the advertising rates n the longer run.

Anyway, even if no apology (which is not important) I would have thought that the owners might have told us what is going on.

Dod

Seems very intermittent, whatever the issue is. This loaded lightning fast.

monabri wrote:Very slow response. 8:45am May 3rd and the occasional

"This site can’t be reachedThe web page at search.php?search_id=newposts might be temporarily down or it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR"

Seems ok now at 12:05

BullDog wrote:

Dod101 wrote:
Agreed but there now ads all over it and some of us do pay voluntarily to have those removed. It is in the owner's interests to get the site up and running properly again or the number of hits will drop off and probably have already which will affect the advertising rates n the longer run.

Anyway, even if no apology (which is not important) I would have thought that the owners might have told us what is going on.

Dod

Seems very intermittent, whatever the issue is. This loaded lightning fast.

Yep. Site is blisteringly quick for me too again now.

I'll report this post next, just to draw the attention of Team Mod to the thread.

Mike4 wrote:

BullDog wrote:Seems very intermittent, whatever the issue is. This loaded lightning fast.

Yep. Site is blisteringly quick for me too again now.

I'll report this post next, just to draw the attention of Team Mod to the thread.

Yes, I'd also say it was now quicker than usual! Strange!