IP blocked

fizzeg · by **fizzeg** » Thu Jan 23, 2020 6:14 pm America/New_York

Hello. Think I have the same problem with blocking. IP of our institute xx.xxx.xx.xx, could you check, please.
I run (for example): wget --user=fizzeg --ask-password --auth-no-challenge=on https://oceandata.sci.gsfc.nasa.gov/cgi/getfile/A2020010.L3m_DAY_IOP_adg_s_giop_4km.nc
and it shows "unknown error". The same issue via browser. All is fine from another networks. Cmd log:
-----------------------------
e:Sat_storagezakachki>"e:Sat_storagezakachkiwget.exe" --user=fizzeg --ask-p
assword --auth-no-challenge=on https://oceandata.sci.gsfc.nasa.gov/cgi/getfile/A
2020010.L3m_DAY_IOP_adg_s_giop_4km.nc
Password for user 'fizzeg':
--2020-01-22 11:24:09-- https://oceandata.sci.gsfc.nasa.gov/cgi/getfile/A202001
0.L3m_DAY_IOP_adg_s_giop_4km.nc
Resolving oceandata.sci.gsfc.nasa.gov (oceandata.sci.gsfc.nasa.gov)... 169.154.1
28.84
Connecting to oceandata.sci.gsfc.nasa.gov (oceandata.sci.gsfc.nasa.gov)|169.154.
128.84|:443... failed: Unknown error.
Retrying.

--2020-01-22 11:24:31-- (try: 2) https://oceandata.sci.gsfc.nasa.gov/cgi/getfi
le/A2020010.L3m_DAY_IOP_adg_s_giop_4km.nc
Connecting to oceandata.sci.gsfc.nasa.gov (oceandata.sci.gsfc.nasa.gov)|169.154.
128.84|:443... failed: Unknown error.
Retrying.

--2020-01-22 11:24:54-- (try: 3) https://oceandata.sci.gsfc.nasa.gov/cgi/getfi
le/A2020010.L3m_DAY_IOP_adg_s_giop_4km.nc
Connecting to oceandata.sci.gsfc.nasa.gov (oceandata.sci.gsfc.nasa.gov)|169.154.
128.84|:443...
----------------------------------------
But no problem with access to oceancolor website. Tracert to oceandata:
-------------------------
1 <1 Ð¼Ñ <1 Ð¼Ñ <1 Ð¼Ñ gulf.poi.dvo.ru [xx.xxx.xx.xx]
2 12 ms 21 ms    8 ms xx.xxx.xx.xx
3    1 ms    1 ms    1 ms xx.xxx.xx.xx
4    1 ms    1 ms    1 ms xx.xxx.xx.xx
5    2 ms    1 ms    1 ms T-2.30040.primorye.net.ru [xx.xxx.xx.xx]
6   136 ms   136 ms   136 ms xx.xxx.xx.xx
7   151 ms   151 ms   151 ms ae15-xcr1.skt.cw.net [xx.xxx.xx.xx]
8   228 ms   232 ms   228 ms ae32-xcr1.att.cw.net [xx.xxx.xx.xx]
9   228 ms   228 ms   228 ms ae33-xcr1.hex.cw.net [xx.xxx.xx.xx]
10   233 ms   235 ms   233 ms ae31-xcr1.ltw.cw.net [xx.xxx.xx.xx]
11   233 ms   233 ms   233 ms et-9-1-0-xcr2.ash.cw.net [xx.xxx.xx.xx]
12   237 ms   232 ms   233 ms ae0-xcr1.ash.cw.net [xx.xxx.xx.xx]
13   244 ms   246 ms   233 ms eqix-ix-dc2.systemsintegration.com [206.126.237.
220]
14   235 ms   235 ms   235 ms xx.xxx.xx.xx
15   235 ms   237 ms   233 ms xx.xxx.xx.xx
16   230 ms   231 ms   230 ms xx.xxx.xx.xx
17   237 ms   234 ms   234 ms rtr-sen-hecn-40g.sci.gsfc.nasa.gov [169.154.192.
153]
18    * * *    Timed out request
19    * * *    Timed out request
------------------------------

gnwiii · by **gnwiii** » Fri Jan 24, 2020 6:14 am America/New_York

Check that the system which is failing has the same or newer version of wget as the ones that work and that they don't use different SSL/TLS libraries.

Some things to try: add " --save-cookies=cookies.txt --load-cookies=cookies.txt --keep-session-cookies ", use "ob" in place of "cgi" and/or adding "-4" (to force use of IPv4) to the wget command-line. If you are getting html login pages instead of data, you may find it helpful to add "--adjust-extension" to html content gets an html extension.

by **OB.DAAC - SeanBailey** » Fri Jan 24, 2020 8:08 am America/New_York

Indeed there was a block on your IP. It has been removed.

fizzeg · by **fizzeg** » Tue Jun 09, 2020 2:28 am America/New_York

Think IP is blocked again. xx.xxx.xx.xx and xx.xxx.xx.xx, could you check, please.

pfsmith · by **pfsmith** » Tue Jun 09, 2020 9:24 am America/New_York

Sorry, no blocks found against those IP addresses.