Closed swainn closed 2 years ago
Hi @swainn - Try editing the content/thredds/wmsConfig.xml
file and changing line 2.
I believe it is currently this
<!DOCTYPE wmsConfig SYSTEM "https://www.unidata.ucar.edu/schemas/thredds/dtd/ncwms/wmsConfig.dtd">
and should instead be
<!DOCTYPE wmsConfig SYSTEM "https://schemas.unidata.ucar.edu/thredds/dtd/ncwms/wmsConfig.dtd">
With TDS 4.6, I don't think you will even have to restart the TDS. A restart is needed for TDS 5.
If that doesn't work, we'll have to dig deeper. But I'm pretty sure that will work.
Cheers,
Ethan
That did the trick. Thank you for your rapid response.
To report a non-security related issue, please provide:
unidata/thredds-docker:4.6.20-SNAPSHOT
Docker:
Description: WMS Endpoints respond with 404 when using
unidata/thredds-docker:4.6.20-SNAPSHOT
. This issue does not occur if we revert back to the previous version we were using:unidata/thredds-docker:4.6.16.1
. No changes were made to the catalog configurations or data.Reproduce: This dataset is accessible and should support WMS: https://tethys-staging.byu.edu/thredds/catalog/data/groundwater/4/Cordillera_Central/catalog.html?dataset=testDatasetScan/groundwater/4/Cordillera_Central/Cordillera_Central_2_drinterpolation_1637544972.6278963.nc
However, the GetCapabilities requests respond with 404: https://tethys-staging.byu.edu/thredds/wms/data/groundwater/4/Cordillera_Central/Cordillera_Central_2_drinterpolation_1637544972.6278963.nc?service=WMS&version=1.3.0&request=GetCapabilities
GetMap requests also respond with 404: https://tethys-staging.byu.edu/thredds/wms/data/groundwater/4/Cordillera_Central/Cordillera_Central_2_drinterpolation_1637544972.6278963.nc?service=WMS&request=GetMap&layers=tsvalue&styles=boxfill%2Frainbow&format=image%2Fpng&transparent=true&version=1.3.0&colorscalerange=-119.935%2C1043.237&time=1996-12-31T00%3A00%3A00.000Z&width=256&height=256&crs=EPSG%3A3857&bbox=-7983694.730330091,2035059.4410645345,-7827151.69640205,2191602.474992575
Note: I will likely revert back to 4.6.16.1 until this issue is resolved, so the links above may function fine.
The following error is logged when this happens: