VIIRS L1B issue (SNPP, JP1, JP2)

[earthdata_synmax]

Hello,

I use the suite of VIIRs L1B products in a monitoring project. Since the 7th each granule I download via the LAADs API returns a 200 status code with html of the login page. I am using the same token to query the API -which works- so I don't believe it's a token error. Additionally, when I try to download a granule via EarthSearch, I am redirected to a 404 file not found page.

Anyone know whats up? I know the SNPP has issues currently but is that affecting the JP1 and JP2 products?


An example is VJ102DNB.A2024312.0036.021.2024314124938.nc,
https://search.earthdata.nasa.gov/search/granules?p=C2105083756-LAADS!C2105083756-LAADS&pg[1][v]=t&pg[1][id]=VJ102DNB.A2024312.0036.021.2024314124938.nc&pg[1][gsk]=-start_date&pg[1][m]=download&pg[1][cd]=f&g=G3286588872-LAADS&q=VJ102DNB&fi=VIIRS&as[instrument][0]=VIIRS&tl=1731361986!3!!&lat=-5.625&long=-149.90625&zoom=0

[LAADSx_UserServices_M]

No, SNPP issue is not affecting VJ1 (NOAA20) or VJ2(NOAA21) products, those are available.
While we are looking into download via Earthdata search issue, you can use following wget command to download files:

wget -e robots=off -m -np -R .html,.tmp -nH --cut-dirs=3 "https://ladsweb.modaps.eosdis.nasa.gov/archive/allData/5201/VJ102DNB/2024/312/" --header "Authorization: Bearer INSERT_EDL_TOKEN_HERE" -P .
Or, you can go to LAADS archive and access files directly:
https://ladsweb.modaps.eosdis.nasa.gov/archive/allData/5201/VJ102DNB/2024/312

[earthdata_synmax]

Thanks for the quick reply! I am still having issues and I think it may be my bearer token. Recently I used the EarthData Token API to rotate my token, is it possible the token isn't syncing with LAADs backend?

When I try to download using wget and my main token I get an unauthorized error. When I use the same main token for querying the API-V2 I get the correct response but it seems I can query it with a bad header. When I generate a new token manually on my main account i get the same errors.

When I use another EarthData Account I am able to download correctly using the same code.

[LAADSx_UserServices_M]

The EDL token expires every sixty days. Also, the issue with that particular file (VJ102DNB.A2024312.0036.021.2024314124938.nc) is resolved and it is working now via EarthSearch.

[jdilgersynmax]

I am aware of the 60 day expiration time for each token. I am testing against newly generated tokens which I created via the Generate Token page.

Newly generated tokens on this account are not working. On my personal account I have deleted all of my tokens yet the token remains valid and new token's appear to work as well.

At this point I think my solution will be to create a new account with a proper email. For anyone with a similar problem when I created my second account I was using the gmail '+' trick to create an additional account using the same email (e.g. emailaddress+earthdata@gmail.com). This is the only difference I can see between my two accounts.

[LAADSx_UserServices_M]

You may want to contact Earthdata Support by filling out the form at the bottom of the page (https://urs.earthdata.nasa.gov/).