Slow again. Getting 25 sec server response, if I waited long enough. Server looks to be swamped with requests. Time: 22:45 hours EDT U.S. Tuesday night, Indiana.
Slow again. Getting 25 sec server response, if I waited long enough. Server looks to be swamped with requests. Time: 22:45 hours EDT U.S. Tuesday night, Indiana.
me too. on firefox, it show as TLS handshake taking forever. Same prob using IE or Android.. Helluva lot longer wait, about 5 sec than just a ping delay
Is this a DDS attack?
it show as TLS handshake taking forever
THANK YOU!
I've been going nuts all afternoon and evening trying to get the servers to go back to normal speed again.
A bunch of certificates needed renewal and when I did that, the site went back to normal speed again it seems!
Site is running slow this morning. Getting warning of invalid certificates.
Site is running slow this morning. Getting warning of invalid certificates.
I have been having issues since last night. It seems to be taking forever. I have have had timeout from Firefox. I just tried pinging after loading this page and I had 278 packets transmitted and lost.
Pat
10:58AM EST
It seems to be a problem with our SSL certificates. I'm working on getting new certificates and hopefully that will fix this problem.
Until we have a fix for this vexing issue (which seems to be originating with third party servers) I've re-allowed non-https traffic.
Remove the 's' from https in the site's domain name for a normal performance.
Be aware that non-https (http) is unencrypted. Read up on it before using it, for example http-vs-https-what-difference-does-it-make-to-security
I don't if you're addressing me in your message, or the general audience of the site.
http is currently much faster.
Until we figure out this stupid problem (which I have no clue what started it or how it got triggered) opting for https will cause major slow down and causes an unpleasant experience. I even replaced storiesonline's security certificate from the free letsencrypt one to a commercial one and it didn't make any difference.
I was addressing the general audience. I'm very sure you know the differences ;) It was not meant as criticism but considering the contents of SOL users should be aware of the risks (especially in some countries). As a temporary solution it's a great service. Me, I'll stick to https and being patient.
Until we figure out this stupid problem
SoL has been very slow or worse for the last 24 hours, now (time of post less 6 mins) it's almost blindingly fast.... Something fixed..??
ETA Using https
Something fixed..??
Something, definitely.
We have no idea what started this SSL handshake problem nor what fixed it!
We stripped the SOL/FS/SFS servers down to the bone trying to remove any possible factors. I replaced SOL's certificate with a commercial one, moved all other sites off those servers and nothing helped. Suddenly, it's fast again.
https remain slow for me.
Blocked: 8731 ms
DNS resolution: 0 ms
Connecting: 97 ms
TLS setup: 8629 ms
Sending: 0 ms
Waiting: 95 ms
Receiving: 0 ms
You are probably hiting the max_client of your apache config.
It could be a slow poke attack again.
Ditch the Apache crap and switch to ngnix.
*edit*: the above timing is for a static resource.
and of course only https request are affected.
Obviously, you are hitting max_client (hence the blocking) Cause of max client could be:
- A DNS issue at your cache or on your http server
but it would affect non SSL trafic too.
- Firewall issue (do not block 127.x.x.x)
but it would affect non SSL trafic too.
- Bandwidth starvation. (not here)
- Slow poke attack.
- max_client set too low.
On the some previous slow down, the receiving timing too was extended to seconds clearly indicative of bandwidth issue.
This time, there is no reception slow down (0 to 16ms), so you have bandwith to spare. I bet your cpu usage is low and ram usage is minimal.
There is just that blocking and handshake delay so probably an Apache issue.
There is just that blocking and handshake delay so probably an Apache issue.
We're rebuilding apache tonight with some extra mods and upgrading PHP. We'll see. For now, when I move most of traffic from https, everything is quick. Hopefully we switch back to https tomorrow.
Response time is still slow for me, and now I cannot "Bookmark next".All the other hyperlinks work(albeit slowly)but that one just doesn't.
Good luck sorting it out.
Response time is now back to normal and "Bookmark next" button is working as it should.
Thanks
Well it was [https] fast this AM but the 'slows' have returned this PM of 08/15/19. Wish I could send you a magic bean or two. After 45+ years in IT, I'm letting you youngsters fix it!