Posted on 06/21/2010 12:21:21 AM PDT by chuck_the_tv_out
Probably not many people noticed, but FR changed its IP address over the weekend, from 209.157.64.201 to 209.157.64.200.
I only noticed because I had hard coded the address to my HOSTS file.
I just wanted to remind the admins that there are many links to 209.157.64.201 out there. Search any search engine for site:209.157.64.201 to see.
You’ve hit upon part of FR’s unique presence in the online world. I’ve had posts or replies turn up on Google in less than a minute.
We could sway Google Trends all by our lonesome, if we cared to do so, not to mention routine searches. Already do, actually, but it’s not likely to have been a conscious thing with most.
Politicians who are unloved here just have to hate it. Watch certain trolls, and certain trollish FReepers, repeatedly namedrop combined with obvious combinations of keywords like mad whenever things are coming to a head. It happens on both pro and con.
“sway Google Trends all by our lonesome, if we cared to do so”
See here:
http://www.freerepublic.com/focus/f-chat/2512697/posts
In 15 minutes after the post, which included a link to search google for ‘obama social security number’, ‘obama social security number’ went from 7th to 3rd top search. It had been 7th for a long time.
Do you understand the recent troubles at FR, as far as pages coming up blank? I’m occasionally able to get around it by clearing cache, history and cookies.
Maybe I’ve got a vivid imagination, but it seems to happen whenever a particularly damning topic begins to get attention on FR.
No I haven’t been seeing any pages come up blank.
I saw one woman complain that she was getting garbled text. That sounded very strange.
Prior to yesterday’s protracted absence, that was the most frequent form of “outage” in my experience, having happened at least four times over the month prior.
I think some of the most controversial recent topics were the Arizona lawsuit from Obama, the organization of landowners forming up like a state militia in Arizona for border security, and the censorship of unsavory news coming out of the Gulf of the massive killoff of marine life both in the water and the air.
In politics, nothing happens by accident. If it happens, you can bet it was planned that way.
Franklin D. Roosevelt
And just imagine what we could do if only a small percentage contributed a measly 10 dollars a month on automatic payment plan.
Btw, a little off topic....but I always wondered how one can see how many “views” an individual thread gets?
Thanks!
Here’s the reason you couldn’t connect...
I often just do google search for FR, figure it helps bump it up in google search software.
One of our primary servers crashed. We now have the main system running on a secondary server until John repairs or replaces the one that fried. We have several servers at FR all performing various functions. Each server has its own IP address so that’s why you may now be seeing a different IP. It was not a DOS attack. Nothing nefarious. Just a hardware crash. We usually have two servers serving web pages and two serving the database and others doing various tasks. Usually a server going off line wouldn’t crash the entire system but this time it did and John had a bit of a problem getting it all running again.
Don’t know where those stats are from but we get well over a million page views per day average.
book marked
Currently, freerepiblic.com (.200) works, and the fried server www.freerepublic.com (.201) is out of commission. If there is a way to tell people (on “alternative” sites?) to remove www. they won’t have to go through FR withdrawal.
If you use a front load balancer / failover switch for both servers, that may prevent “outages” for some users, but probably will slow things down since only one server will be in use until second server is back online.
If you do an NSLookup on www.freerepublic.com you’ll see that both the .200 and .201 addresses come up. This means that either one can respond to hits on that name. For some reason both servers went down. One of them appears to still be down, and since you had it hard-coded in your hosts file, it couldn’t work on the other one once it became available again. It wasn’t a change in IP addresses.
Nice link - thanks
When I couldn’t get in and all of you could, I remembered that new IP addresses took a while to go out and come back and work. But, when my laptop worked and desktop did not, I thought maybe I was crazy.
Very, very late I googled and saw the #s and tried them. The got me to FR, BUT would not allow me to log in.
I am in now.....hope it holds up. Thanks for the help/ping.
I thought something might be going on.
I was having trouble getting onto FR a couple of nights ago. In troubleshooting, I could reach FR from my work computer, but not from my home machine.
From work, I pinged FR’s domain, and received an address in the reply. I then minimized my RDP session to get back onto my home computer, and typed http://(ip address), and got right on. I then knew it was a DNS issue of some sort. I flushed the DNS cache on my home machine, and all has been well since.
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.