Not access to FSairlines site

[TSL1]

I use the firefox. I cannot access the fsairlines site without proxy. When i select a proxyserver
for example [proxy.vivodi.gr] at network adjustments then i have access.
How can i solve this problem? Thank you very much TSL1 Z.D

[DaKurt]

Where are you from? Godaddy blocks certain countries from visiting their servers...

[TSL1]

I am from Greece Athens.
For inform you the problem doesnot exist since 20:00 today
Thank you very much for your attention.
TSL1 Z.D

[Konny]

Hm, if that happens again, can you please run 'tracert fsairlines.net' from a command prompt and send us the result?

[PAV101]

Hi all ...

We have this problem in Iran from transfer from flynet to fsairlines due to Godaddy deprivals against Iranian IP's . All Iranian pilots must use proxy changers to connect to fsairlines .

From 3 day ago we have a big problem ...
We ( over 90% of Iranian guys ) generally had use Ultrasurf program to connect to the network . There was no problem between ultrasurf and FSA client 1.2.1 . but unfortunatelly new FSA client (v 2.0.0) is not able to use Ultrasurf to send the PIREPs and from 3 days ago , we are seriously grounded ...

Now we need your help to debug the client and let us back to our flights ...

Remember ...
My airline , Parmiss Airlines , one of the most active FSA VAs , is going to STOP due to this problem ...

Regards ...
Kh. Talebzadeh , Parmiss Airlines CEO

[Konny]

Hm, we changed the transmission method in the v2.0 release which probably caused your problems. We're sorry for the inconveniences and will try to fix that as soon as possible.
We also contacted GoDaddy.com and they deny that they're blocking IPs from Iran. Can you please tell your pilots to run 'tracert fsairlines.net' from a command prompt and send us the results next time they can't access the site?

[ar_hnazari]

Hi dear Kenny

I talk you first as Data Center Site designer in real life, then as a FSA pilot.
This is my trace log :

Tracing route to fsairlines.net [97.74.200.113]
over a maximum of 60 hops:

1 2 ms 1 ms 1 ms 192.168.94.254
2 29 ms 27 ms 33 ms 85-15-0-195.rasana.net [85.15.0.195]
3 26 ms 46 ms 40 ms 85-15-0-193.rasana.net [85.15.0.193]
4 * * * Request timed out.
5 29 ms 29 ms 29 ms 85-15-0-58.rasana.net [85.15.0.58]
6 28 ms 31 ms 29 ms 78.38.255.89
7 33 ms 27 ms 31 ms 78.38.255.213
8 164 ms 183 ms 176 ms 195.175.5.21
9 156 ms 158 ms 158 ms uls-t1-1-erz-t2-x.turktelekom.com.tr [212.156.109.25]
10 160 ms 170 ms 158 ms acb-t1-1-uls-t1-1.turktelekom.com.tr [212.156.117.33]
11 168 ms 163 ms 166 ms static.turktelekom.com.tr [212.156.117.146]
12 303 ms 238 ms 213 ms amsterdam-1--acb-t2-1.turktelekom.com.tr [212.156.102.9]
13 158 ms 155 ms 153 ms 146.82.55.17
14 301 ms 303 ms 299 ms 64.210.13.110
15 300 ms 300 ms 301 ms ip-208-109-112-198.ip.secureserver.net [208.109.112.198]
16 303 ms 300 ms 301 ms ip-216-69-188-106.ip.secureserver.net [216.69.188.106]
17 301 ms 299 ms 303 ms ip-208-109-113-157.ip.secureserver.net [208.109.113.157]
18 330 ms 505 ms 378 ms ip-208-109-113-170.ip.secureserver.net [208.109.113.170]
19 316 ms 311 ms 312 ms ip-97-74-200-113.ip.secureserver.net [97.74.200.113]

Trace complete.

And now via a VPN connection:

Tracing route to fsairlines.net [97.74.200.113]
over a maximum of 30 hops:

1 253 ms 307 ms 362 ms 192.168.33.1
2 263 ms 220 ms 195 ms gw.giga-dns.com [91.194.90.1]
3 232 ms 209 ms 200 ms host-93-104-204-33.customer.m-online.net [93.104.204.33]
4 290 ms 310 ms 277 ms 82.135.16.209
5 294 ms 369 ms 370 ms 62.140.24.49
6 249 ms 334 ms 276 ms ae-4-4.ebr1.Frankfurt1.Level3.net [4.69.134.2]
7 262 ms 256 ms 199 ms ae-71-71.csw2.Frankfurt1.Level3.net [4.69.140.6]
8 371 ms 322 ms 250 ms ae-72-72.ebr2.Frankfurt1.Level3.net [4.69.140.21]
9 390 ms 472 ms * ae-41-41.ebr2.Washington1.Level3.net [4.69.137.50]
10 341 ms 369 ms 307 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.150]
11 375 ms 349 ms 400 ms ae-71-71.ebr1.Washington1.Level3.net [4.69.134.133]
12 399 ms 441 ms * ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
13 423 ms 423 ms 379 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21]
14 451 ms 400 ms 476 ms ae-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]
15 414 ms 433 ms 453 ms ae-4-4.car2.Phoenix1.Level3.net [4.69.133.37]
16 504 ms 496 ms 517 ms THE-GO-DADD.car2.Phoenix1.Level3.net [4.53.106.2]
17 559 ms 384 ms 377 ms ip-208-109-112-142.ip.secureserver.net [208.109.112.142]
18 438 ms 450 ms 427 ms ip-208-109-113-161.ip.secureserver.net [208.109.113.161]
19 468 ms 508 ms 519 ms ip-208-109-113-165.ip.secureserver.net [208.109.113.165]
20 383 ms 430 ms 496 ms ip-208-109-113-170.ip.secureserver.net [208.109.113.170]
21 562 ms 358 ms 578 ms ip-97-74-200-113.ip.secureserver.net [97.74.200.113]

Trace complete.

As you can see, the PING request is not blocked by the firewalls and routers of your host.
But as I have used softwares that generate HTTP traffic to a server, all HTTP traffic is blocked from certain ranges of IPs from the reply side.
Now please inform us, will be a trick or solution that we can access the site without using VPN or PROXY servers over the world or not?
I have even offered Claudio a very professional DC in germany which costs much less that GoDadd for very professional DEDICATED SERVERS and also offered to pay the difference of price yo pay to GoDadd...but... I don't understand why not...
Will watch for a reply from you

Regards

Amir Reza Hadji Nazari

[Sorush]

hi konny ... We also have this problem to use the Fsairlines Website like our friends in Simorgh Air and Parmiss Air
if possible check the problem :

here the track :
C:\>tracert fsairlines.net

Tracing route to fsairlines.net [97.74.200.113]
over a maximum of 30 hops:

1 * 2682 ms 1632 ms 172.16.6.19
2 210 ms 1066 ms 601 ms 80.75.1.20
3 1132 ms 526 ms 1097 ms 217.11.30.251
4 277 ms 183 ms 2050 ms 217.11.31.1
5 991 ms 179 ms 973 ms 78.38.255.213
6 906 ms 1172 ms 668 ms ldn-b1-link.telia.net [213.248.76.41]
7 911 ms 353 ms 333 ms ldn-bb2-link.telia.net [80.91.248.94]
8 607 ms 339 ms 339 ms ldn-b3-link.telia.net [80.91.247.27]
9 412 ms 334 ms 324 ms abovenet-ic-126798-ldn-b3.c.telia.net [213.248.101.106]
10 619 ms 1206 ms 325 ms so-0-0-0.mpr1.lhr2.uk.above.net [64.125.27.225]
11 890 ms 627 ms 631 ms so-1-1-0.mpr1.dca2.us.above.net [64.125.31.186]
12 596 ms 942 ms 3082 ms so-1-0-0.mpr3.iah1.us.above.net [64.125.29.37]
13 1305 ms 1262 ms 562 ms xe-1-1-0.mpr4.phx2.us.above.net [64.125.28.73]
14 554 ms 499 ms 529 ms xe-1-0-0.mpr3.phx2.us.above.net [64.125.27.97]
15 3154 ms 845 ms 1350 ms 64.124.196.38.allocated.above.net [64.124.196.38]
16 629 ms 1253 ms 502 ms ip-208-109-112-137.ip.secureserver.net
[208.109.112.137]
17 488 ms 511 ms 500 ms ip-208-109-112-161.ip.secureserver.net [208.109.112.161]
18 481 ms 501 ms 498 ms ip-208-109-113-157.ip.secureserver.net [208.109.113.157]
19 543 ms 517 ms 503 ms ip-208-109-113-170.ip.secureserver.net [208.109.113.170]
20 1305 ms 780 ms 929 ms ip-97-74-200-113.ip.secureserver.net [97.74.200.113]

Trace complete

Regards,
Sorush Salahshour

We are waiting for your reply

[Konny]

Ok, thanks, we already have set up a relay server which will probably solve your problems. Unfortunately everything's coming together at the moment ( we have to get the integration pack online and I had to rewrite a lot of Client code to make it portable to Mac and Linux which still hasn't been tested enough ). I'll try to release a beta version of the Client which connects to the relay server soon ( probably next week ).

[PAV101]

Dear Konny ...

After 2 weeks, many of our pilots are still waiting for new client to resolve the problem with ULTRASURF IP Changer ...
As I said before , we must use Ultrasurf to access to the site and send our PIREPs (Due to Internet limitations in Iran) . Present Client (V2.0.0) is not able to send the PIREP via Ultrasurf ( There was no such problem with previouse versions ).

I Know you are working hard on remote system and many other things . but this problem is the most seriose problem for Iranian users ...
Help us back to our flights ...

Tnx ...
Kh. Talebzadeh
IPV CEO

[Konny]

Sorry for the delay, but we really had to concentrate on the website integration pack. I just made a v2.0.0 release for you which is able to connect to the relay server. You can download it here: http://fsairlines.net/downloads/FSAirli ... altsrv.zip
Just overwrite the existing FSAirlines.exe and fsairlines.ini with the files in the zip. The relay server is located in the UK, please tell me if it helps.

[PAV101]

Dear Konny ...
Its EXCELLENT !!!

We still need to run IP changers for access to the web site ( n/p ... we can handle it ! ) from Iran . But now, my client is working very good and smooth.
So ... We can back to flight again ...

Thanks ...
Kh. Talebzadeh

[Konny]

Great