Welcome to the Earthdata Forum! Here, the scientific user community and subject matter experts from NASA Distributed Active Archive Centers (DAACs), and other contributors, discuss research needs, data, and data applications.
by ndeewong » Thu Aug 11, 2022 2:46 pm America/New_York
Hi, aside from server speed issue, there seems to be a glitch on LPDAAC with user authentication. The glitch allows python requests to return metadata content without authentication, and return 401 error when authentication info is provided. Here is a code to replicate the issue, if auth_info = None, content can be retrieve (after 1-5 mins of waiting), if auth_info = (USERNAME, PASSWORD), a 401 error return. Please help resolve the issue, and thank you so much for all the hard work on building and maintaining this database.
This error might be caused from the LP DAAC who has been experiencing high volumes of user traffic. This has been impacting data downloads for some users and causing timeouts. We have been implementing fixes for this issue. Please try to clear your cache one more time and access the data again. We have found that things are spiking upward again now, but these tend to relate to times users begin their day. You might want to try during off busy hours for best chance of success.
I got the same error using the edge browser, however after a few minutes on Firefox and entered username and password the metadata file was available.
I will forward your inquiry to a subject matter expert for assistance.
I checked with our subject matter expert who advised the instructions are still valid and should run just fine.
Please be advised the LP DAAC is experiencing high volumes of user traffic. This has been impacting data downloads for some users and causing timeouts. Please contact email@example.com if you continue to have issues.
Hi @piyush It looks like we are still experiencing issues and are now looking into other solutions. At this time the best advice I have received is to try and download data half an hour after the top of the hour (i.e. 1:30, 2:30, 3:30, etc) as this is when we are manually refreshing connections until we have a better solution. Apologies for the delay, thank you for your patience while we work through this.