Posted on 11/15/2020 10:28:43 AM PST by al baby
John thank you and Jim so much if I would have slept in I would never had know free republic was done Great job get her up and running
I am so thankful for Free Republic.
Me too
Thanks for the hard work, I was lost this mornging without FR.
Sentiments echo’d and ditto’d all OVAH FReepahland !
Agreed!
Yes, thanks!
For a while there, I thought we had been deplatformed.
Thank God. it was just a moving issue.
You Robinsons are the lifeline of true conservatives
Free republic is hands-down the best website on the entire planet!!!
You have to think about our buddy in that movie saying “you can’t handle the truth!â€
Ditto that...up all night awaiting the real news.
You can say that again!!
I am so thankful for Free Republic!God Bless all those who make it possible.
I’m glad you are back up, too. BUT, it is running very, very slow.
Will that improve??
Ditto...running VERY slow.
VERY slow. Getting 504 gateway timeout messages.
has there been an address change???
It will fix itself in time. The domain name is the same but has a new IP address due to relocating the http server. All websites actually have a numerical IP address. When you type in a url, eg freerepblic.com, your browser sends a request. That request goes through many Domain Name Servers to locate the http server that holds the website’s files. These DNS servers are specialized and do nothing but route web traffic and the servers are all over the world. There could be several DNS servers involved in a request that aims your browsers to the final hosting server and they all take time to get their records updated when a website moves to a new final server with a new numerical IP address. Those requests can also take many different routes through the various DNS servers. Your individual location and internet service provider play a part in what path and dns servers will be used. Sometimes the request hits a server that hasn’t been updated yet when the request fails, it will try another server and another and another until it finds the website server. After a certain amount of time, it gives up. That’s when you get 503, 504, 404 etc errors.
Should be fine by tomorrow sometime. 12-36 hours these days. Used to be 24-72 hours but computers and servers have gotten faster and greater in number.
If you saw a chart of the servers onvolved, it would look like the dem’s non-profits $$$$$$ connections. The ones that usually have one or several Soros connections.
(and now I shall copy this before hitting the Post button, in case it gets lost in cyber space so I don’t have to retype it)
“The domain name is the same but has a new IP address due to relocating the http server.”
Thanks! Good to know. Does it make any sense to publish the IP address in the meantime??
Good explanation.
I’m getting the same, server not found or connection timed out messages. Tried 6 or 8 times to open another thread, took over 5 minutes. When it does open, takes 2 1/2 minutes or so.
I can’t remember how, haven’t done it in 15 years or more, you can use DOS or a DOS prompt to find out the website IP address. I think you just ping that address.
at a command prompt type:
ping www.freerepublic.com
make sure you do put a space after the word “ping”. If it doesn’t give you the IP, it will still tell you how lonv it takes to ping the site, I think it lists tbe IP addresses it goes through too. (routing)
Wouldn’t help because the new numerical IP address is exactly what needs to propagate among the various dns servers.
VERY SLOOOOOW
As a reference, I’ve a 100MB internet service with typically120-130MB speed.
Up until possibly now, since things are going faster, you wouldn’t know for sure if you’re getting the old IP address or the new one.
I've got Gig-E and it's pretty slow right now.
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.