Posted on 11/15/2020 7:20:03 AM PST by John Robinson
Slow mo it goes. I think you knows.
My exact same problem.
My exact same problem.
Same here.
Sometimes it works, sometimes 504 gateway timeout message.
My exact same problem.
At first, the system was lightning fast.
Now, it's hanging / waiting for "securing connection" whenever I click a link on FR. Whether I'm going back to the Comments page, Forums page or just going to the next group of posts in a thread. Looks like an issue with SSL, but I could be wrong. I don't know what security/authentication methods are behind each link.
Not SSL, but likely resource starvation behind the proxy. Load balancing prolly still in progress regarding the migration.
The HTTP response says “securing connection” ... I could be wrong, I don’t think that’s resource starvation behind a proxy. Wouldn’t it just time-out if it were a resource starvation issue?
A “traceroute” (Linux/MacOS) or “tracert” (Windows) reveals a lot of hops for me (from the West coast) via Cogent Comm. to DFW and then to a “Cloud Host” (”Linode”)....not the usual FR co-located server hardware.
HERE IN illinois FR running VERY slow! Get 504 Gateway Errors. I can ping IP adr ok.
Yep, it's slow. I'm not getting the Gateway Errors you are, I'm just getting timeout messages. (Same thing.)
John may be planning a return to a co-located private server in a data center in the near future...the Linode cloud host may be just temporary.
Hi guys. I appreciate all you have to do to help us meet with fellow conservatives. I’m sure this seemed a sudden tough scramble to have to change quickly.
Since I’ve been trying this on my iPad, it seems I have to wait about 20 seconds for loading every single link I ever select. Doesn’t matter what kind. Never had a quick switch to any page. The last link I tried (last page of replies to this thread), I stopped counting at 35 seconds and quit.
>> “securing connection”
That represents (from the browser’s perspective) the phase of the connection which is initially the SSL/TLS stuff. It’s not like the proxy negotiates the security with the browser independently of the services being proxied. It’s effectively a single request all the way to the service endpoint, and likewise a response all the way back to the browser — where the proxy translates the secured data to & from clear.
And the SSL/TLS could also be handled by a firewall, and not a proxy. Or a firewall with the proxy providing load balancing.
I have no idea how the system is setup, but just describing various scenarios where the protected service endpoint is possibly maxed out causing the proxy to timeout.
All I can say is this:
i'm getting "This site can't be reached."
"freerepublic.com took too long to respond."
Try
* Checking the connection
* checking the proxy and firewall
ERR_TIMED_OUT
HELLINOIS! To think this was once a conservative state.
Yes Im getting the 504 Gateway Timeout errors. Wonder if all the route servers havent been updated??
The 30 second refresh rate is problematic.
I glossed over the security negotiation details. The browser first requests the domain certificate which is validated at the client. That step could have failed — the delivery of the certificate. But once validated (relying on known authorities/roots), the browser encrypts the data and then transmits to the domain. If the cert isn’t being provided, then unlikely it’s being provisioned by the proxy/firewall, but instead being provided by the web server directly.
Charsets are definitely whacked especially when posting comments.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.