Open sci92bior opened 2 years ago
It sounds like something to do with SSL certificate chain verification between Dimension/Etherpad. It seems like you're manually managing certificates. Perhaps you're using some sort of self-signed certificates that Dimension doesn't trust?
I have ganerated certificate from internal network CA for matrix, element and dimension. Looks like etherpad outside docker network have the same ceritificate as dimension (dimension.domain/etherpad). I can easly open Etherpad from browser via dimension.domain/etherpad with SSL so connection from outside works well. So etherpad should also have own SSL cerificate?
I have no clue, as I don't use any of these services. My guess is that Dimension wants to access Etherpad and the Dimension HTTP stack does not trust your self-signed certificates for https://dimension.domain/etherpad
or whatever. Not sure how it's all wired together and which services tries to access which other service and when.
Playbook Configuration:
My
vars.yml
file looks like this:Matrix Server:
Ansible: If your problem appears to be with Ansible, tell us:
Problem description:
I try to run etherpad share dockuments in Element. After ansible deployment I receive error UNABLE_TO_VERYFI_LEAF_SIGNATURE on matrix-dimension server when i try to open etherpad widget in room. I reach dimension/etherpad page from browser in which I run element with https.
Client (please complete the following information):