Is the DVA setup for SSL as this is required for GW web to be able to use it, you can use this TID to create a certificate 

Thanks  yes it was setup for ssl, and if I look in the GDVA log it shows :

04-09-24 09:27:47 HTTP: Establish SSL connection with ::ffff:192.168.168.11 on socket 6

So setup for ssl, and working. It also converts, but does not show in the gwweb.

So I hope 192.168.168.11 is your web client server, isn't it?

Do you use "-e GWSOAP_SSL_VERIFY=off " in your web client startup script?

What do you see if you run docker logs gwweb and try to render?

Docker logs gwweb shows :

[error] 779#779: *519 upstream SSL certificate does not match "localhost.com" while SSL handshaking to upstream, client: 192.168.168.14, server: groupwise.***.nl, request: "POST /dva HTTP/1.1", upstream: "">192.168.168.12:8301/dva", host: "groupwise.****.nl", referrer: "">groupwise.****.nl/.../default"
192.168.168.14 - - [10/Apr/2024:22:36:32 +0000] "POST /dva HTTP/1.1" 502 150 "192.168.168.12:8301" "">groupwise.*****.nl/.../default" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:124.0) Gecko/20100101 Firefox/124.0" "**7.**2.**2.**2"

So groupwise server is 192.168.168.12, gwweb is running on 192.168.168.11, and the 192.168.168.14 is the Nginx in front.

- So as I see it the SSL forward on nginx is not working the way it should be, am I correct ?

- Any tips on this ?

This indicates the SubjectAlternativeName in the certificate is not matching the hostname so please go over the TID as I mentioned in the previous post and use the correct hostname etc when creating the certificate used by the DVA. The current certificate seems to have localhost.com which is not the same as hostname -f returns on the server the DVA runs

Followed your TID

- yes now it has an Subject Alternative Name:

- no it still does not work

Same error. But my guts are on the nginx server, since it mentions connecting upstream and the ip adress of the nginx server.

The SAN is there but the point was the name in the SAN is not correct, the error indicates this as well. If this is the same error still like you reported "upstream SSL certificate does not match "localhost.com" 

All certificates DVA and POA must have the SAN on a valid hostname so it must match the hostname -f and this must be a FQDN i assume looking at the original error non of the servers have (or should have ) the name localhost.com as this is not  FQDN 

Yes still the upstream error. And I can open all mails and attachments, only not view the documents inline.
I think this is because of the NGINX server I have put in front of my servers, this is proxy-ing the traffic.
But somewhere this messes up the DVA stream.

Update ; took the Nginx server out of the equation, but even when I connect directly to the docker image, and try to render an attachment, it still throughs this error. So it is not the NGINX.
Any clues where to check for this "localhost.com" ?

Or shall I re-do the config of the docker gwweb image ?

Try to run a 'docker logs gwweb' (I assume your container uses this name ).