GeoWebCache (with vectortiles) does not return tiles

gannebamm commented 2 months ago

Expected Behavior

I download plugins like described here https://github.com/Thuenen-GeoNode-Development/thuenen_atlas/tree/thuenen_4.x/docker/geoserver#plugins and build the GeoServer container. Now I can serve and fetch vectortiles via the integrated GWC. I can use the TMS service in QGIS to get vectortiles and I can use them in web-applications (like openlayers). The web application should work like this:

2024-09-26-382-LPIT40174-BS

Actual Behavior

The data is not fetched properly. I can neither use them in QGIS nor in web-applications.

Steps to Reproduce the Problem

Try to load this as vector tiles into QGIS: https://atlas.thuenen.de/geoserver/gwc/service/tms/1.0.0/aa_at_geoserver_99_20:rlevl_uaa_2020_bkr@EPSG%3A900913@pbf/{z}/{x}/{-y}.pbf
There is no data

or

open external application https://atlas.thuenen.de/webspace/agraratlas/agraratlas/index.html?LP=2
The WMS data is fetched you see this:

grafik

But you can not click on other municipalities to get new diagrams because the vectortiles are not fetched.

grafik

Specifications

GeoNode version: https://github.com/Thuenen-GeoNode-Development/thuenen_atlas/releases/tag/v4.2.5

Additional information

We have a similar GeoServer setup with GWC and vectortiles but without GeoNode here: https://geoserver-bw.thuenen.de/atlas_thuenen_rs/index.html

Which serves vectortiles in scales under 1:94242 like:

https://geoserver-bw.thuenen.de/geoserver/gwc/service/tms/1.0.0/rs_v201:ctm_ger_2023_lsm_hex_v201@EPSG%3A900913@pbf/{z}/{x}/{-y}.pbf

which can be used in QGIS.

The GeoWebCache Demo on atlas.thuenen.de does render the tiles. logged in as GeoServer admin the link https://atlas.thuenen.de/geoserver/gwc/demo/aa_at_geoserver_99_20:rlevl_uaa_2020_bkr?gridSet=EPSG:900913&format=application/vnd.mapbox-vector-tile does show the tiles. For anonymous the tiles will not get displayed.
If I am logged into GeoServer with OAuth and the GeoNode admin account I will be able to load new diagrams and the vector tiles are fetched for the web application listed above. It works as expected (see gif above).

The filterchain was already changed in our instance to gwc | /gwc/rest/**

gannebamm commented 1 month ago

ridoo commented 1 month ago

An additional observation: On Firefox I can see the first charts as you mentioned (Chrome misses this from time to time):

There is a deprecation note on the console:

MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. [Util.js:15:3](https://atlas.thuenen.de/webspace/agraratlas/agraratlas/src/core/Util.js)
MouseEvent.mozInputSource is deprecated. Use PointerEvent.pointerType instead. [Util.js:15:3](https://atlas.thuenen.de/webspace/agraratlas/agraratlas/src/core/Util.js)

Both Firefox and Chrome are logging 400 (Bad Request):

GET https://atlas.thuenen.de/geoserver/gwc/service/tms/1.0.0/aa_at_geoserver_99_20:rlevl_uaa_2020_lau2@EPSG%3A900913@pbf/7/67/85.pbf 400 (Bad Request)

gannebamm commented 5 days ago

there are changes on GeoServer. See https://github.com/GeoNode/geoserver-geonode-ext/commit/1e36104a11355e131d437bafd7555a5d5b3d2475#commitcomment-146374544

@ridoo This (https://github.com/GeoNode/geoserver-geonode-ext/pull/190) will likely trigger an overwrite of 2.24.4 image? This should create a new 2.24.5 (https://github.com/GeoNode/geoserver-geonode-ext/pull/190). Maybe as 2.24-v2? We need to check this after they are finished.

gannebamm commented 5 days ago

@ridoo

GeoSolutions told me:

Hi Florian, all the artifacts and Docker images for the GeoServer 2.24.2 data directory have been updated.

This means recreating the 52North ones and tagging them accordingly, right?

ridoo commented 2 days ago

This means recreating the 52North ones and tagging them accordingly, right?

@gannebamm actually, there is only a customized thuenen GeoNode image we reference. You should be ok with updating the versions in the .env file. I will do an update for those anyway when starting the 4.4.x update. However, I will have to investigate what has changed to evaluate the update there. The updates in the data dir were always a bit intransparent TBH

gannebamm commented 2 days ago

Just changing the env was enough since we built from geonode https://github.com/Thuenen-GeoNode-Development/thuenen_atlas/blob/thuenen_4.x/docker/geoserver/Dockerfile#L2 & https://github.com/Thuenen-GeoNode-Development/thuenen_atlas/blob/thuenen_4.x/docker/geoserver_data/Dockerfile#L2 deployed on geonode-demo.thuenen.de

After taking a look the update shall close the isse #42 and not this one, though.

gannebamm commented 1 day ago

rebuild the images which fixed the time series error, but this one persists.

Thuenen-GeoNode-Development / thuenen_atlas