Fapzilla errors and a workaround

[grover92000]

I did a little digging this morning and found the cause of the errors fapzilla is getting. The problem is a DNS issue. There are 2 address records for my.wildblue.net:

[root~]# nslookup my.wildblue.net

Name:   my.wildblue.net
Address: 12.109.229.94
Name:   my.wildblue.net
Address: 216.126.204.65

12.109.229.94 is the bad server that doesn't have the .asp script so you get an error 404. A work around is to add this entry to your hosts file:
216.126.204.65 my.wildblue.net

For Linux/MAC users it's /etc/hosts
For Windows XP/Vista it's C:\WINDOWS\SYSTEM32\DRIVERS\ETC\hosts

Since I made the change I haven't had a single error.
Before:

3/15/2008 09:00:02 252,807 135,957
3/15/2008 09:15:01 ERROR,ERROR 135,958
3/15/2008 09:30:01 252,807 135,958
3/15/2008 09:45:01 ERROR,ERROR 135,958
3/15/2008 10:00:01 ERROR,ERROR 135,958
3/15/2008 10:15:01 252,807 135,959
3/15/2008 10:30:02 ERROR,ERROR 135,959

After:

3/15/2008 10:45:02 252,807 135,960
3/15/2008 11:00:02 252,807 135,960
3/15/2008 11:15:02 252,807 135,960
3/15/2008 11:30:02 252,807 135,961
3/15/2008 11:45:01 252,807 135,961
3/15/2008 12:00:01 252,808 135,961
3/15/2008 12:15:02 252,808 137,1000
3/15/2008 12:30:01 252,846 137,1000

Hope this helps.

[Spice300]

A DNS error is exactly what my trace routes show in wildblue customer service: Post 18. I missed it, and you caught it. Good going Grover

[equivocal]

I can't change hosts on the system I run fapzilla, but I changed $url to use the IP address and...still got errors (both IPs).

Coincidentally, just recently ran into the same problem with jigdo.fedoraunity.org with the twist that for a period using the WB proxy worked but direct access got a 404.

[grover92000]

Originally Posted by equivocal

I changed $url to use the IP address and...still got errors (both IPs).

Using the IP address won't work because it's a virtual domain on the web server. The server doesn't know which domain the request belongs to. Here's a modified script that should work for you.

[Spice300]

Since putting the entry in my hosts file, Fapzilla no longer returns errors. After more than 40 reads, it is returning results on the first attempt

[equivocal]

Originally Posted by grover92000

Using the IP address won't work because it's a virtual domain on the web server. The server doesn't know which domain the request belongs to. Here's a modified script that should work for you.

Near as I can tell, my hack was identical. To deal with virtual hosting I added a header with a Host field. That seems to have done the trick.

[AES]

Thanks. That took care of it.

[mkbilbo]

Originally Posted by grover92000

I did a little digging this morning and found the cause of the errors fapzilla is getting. The problem is a DNS issue. There are 2 address records for my.wildblue.net:

[root~]# nslookup my.wildblue.net

Name:   my.wildblue.net
Address: 12.109.229.94
Name:   my.wildblue.net
Address: 216.126.204.65

Get this. For about a hour this morning I was getting the reverse. 216.126.204.65 was coming up first. Now it isn't.

Yeesh.

Anyway... Fapzilla is alive! Dish customers should try using their full Dishmail email address. You know, "username@dishmail.net". It's working fine for me after I did the /etc/hosts entry.

Near as I can tell, Fapzilla no longer needs to "accomodate" Dish WB users. The same link works for me long as I used my full Dishmail address. That is:

http://my.wildblue.net/content/fap-sso/proxy_username.asp?user_name=

From Fapzilla works flawlessly both in my browser and Fapzilla with "mkbilbo@dishmail.net".

The URLs you had to put in to accommodate Dish WB users appear to have been shut down. I can't even get connections to them now. So near as I can tell, they've switched to differentiating between Dish and direct WB folk by @dishmail.net and @wildblue.net.

Which makes things a lot simpler really...

[MAKAKA]

Originally Posted by mkbilbo

So near as I can tell, they've switched to differentiating between Dish and direct WB folk by @dishmail.net and @wildblue.net.

Just for the record, there is also @attwb.net for the AT&T folk.

[mkbilbo]

Originally Posted by MAKAKA

Just for the record, there is also @attwb.net for the AT&T folk.

At least for now. The whole thing seems to be in flux with the change to Google. I guess we'll see.

Anywho, interesting side bit I ran into. In Safari, go to your Google start page. Right-click the Googly FAP meter and you get a menu with the option:

"Open in Dashboard..."

You get a box that you can drag around or just move the mouse to the graph of the widget and click to select. There's an "Add" button that has appeared in at the top of the browser window. Click it and, zoink, Dashboard sucks in the FAP meter.

I did not know I could do this.

I had to try a couple of times to get the selection of the Googly FAP meter right but when I hit the right selection, it put the graphs on my Dashboard.

I have no idea if you have to be logged in or not for it to work but I thought this was just kinda cool.

[lahazard]

I don't know what happened during the past 24 hours when I could not get online, but this morning I went back and reset everything to the pre-google settings and then started over with the changes to my hosts file, as well as adding both myaccount.dishmail.net and myaccount.wildblue.net to my trusted sites and making sure that I was using my email address rather than my dish account number and........for the first time since the switch to Google I have the bandwidth gadget on the start page and (more importantly to me) I am not getting errors from fapzilla.

(Prior to this none of the above changes accomplished the same for me. I could get fewer errors with Fapzilla, but could not get the bandwidth gadget up and running. I am of the mind that I was not doing something quite right, but I remain open to it being more on the part of Wildblue making changes - or more likely some combination of both.)

I wanted to thank everyone who has been putting in time and energy to find solutions and workarounds. I don't know if everything will still be working later today or tomorrow, (all is indeed flux!) but for now all seems to be settling a bit.

[opus74]

Adding the line to the etc/hosts file fixed mine.

I'm on NRTC.

Thanks !!!!

[Cadrat]

Originally Posted by grover92000

Using the IP address won't work because it's a virtual domain on the web server. The server doesn't know which domain the request belongs to. Here's a modified script that should work for you.

Need a bit of help here guys. Running win xp but still getting error reports trying to get fapzilla to work? Will this script work for windows and if so can you explain where to extract it? Does it replace the original file or do I need to change something?
wb since 3-2006 riverside beam 21 user

[Spice300]

Originally Posted by Cadrat

Running win xp but still getting error reports trying to get fapzilla to work?

The script was for Equivocal who could not put the entry into his hosts file. Do you have the same problem? Can you get Fapzilla to work at the Command Prompt?

[Cadrat]

Originally Posted by Spice300

The script was for Equivocal who could not put the entry into his hosts file. Do you have the same problem? Can you get Fapzilla to work at the Command Prompt?

No. At command prompt I get error error. That is my current status. I did put in my primary email in the cfg file like instructed Thanks for the reply.