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.
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='oceandata.sci.gsfc.nasa.gov', port=443): Max retries exceeded with url: /directdataaccess/Ancillary/LUTs/common/?format=json (Caused by ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')))
Error: trying to run = /home/optics/SeaDAS/ocssw/bin/ocssw_runner --ocsswroot /home/optics/SeaDAS/ocssw update_luts common
Additionally, when I try to access the URL directly from my browser, I get the following error message:
ERR_HTTP2_PROTOCOL_ERROR: The website may be temporarily unavailable, or it may have permanently moved to a new URL.
I have already tried checking my network connection and verified that my proxy settings are correct, but the issue persists. Has anyone else faced this problem or have any suggestions on how to resolve it?
Hello, Some of us tested the location you're trying to access. I'm not able to recreate the issue on my end. Are you still encountering this error? If so, you may need to add the base of the URL to your attempt: *https://oceandata.sci.gsfc.nasa.gov*/directdataaccess/Ancillary/LUTs/common/
Otherwise, if you are still getting this error please share the command you tried to run that resulted in the error shown.
by niglas_cas » Mon Jan 12, 2026 5:27 am America/New_York
OB ODPS - towens wrote: ↑Wed Jan 07, 2026 1:53 pm America/New_York
That command:
/home/optics/SeaDAS/ocssw/bin/ocssw_runner --ocsswroot /home/optics/SeaDAS/ocssw update_luts common
is working for me, so the server is responding as expected, but I am inside the NASA firewall.
If it is still failing for you, please provide your IP address so we can check the block list.
Tommy
Thank you very much for the clarification.
The issue has been resolved on my side. The server was temporarily inaccessible to me for approximately one hour, after which access returned to normal. The update_luts common command is now working correctly without any issues.
It appears that the problem was transient, and no further action is needed at this time.