Closed knarou34 closed 6 years ago
The problem is that the certificate served by your reverse proxy to synapse (when attempting to talk to mxisd) is not valid. Why it's not valid is not said, but the most likely causes are:
That part is out of scope of mxisd and for you to find out I'm afraid.
Many thanks for you answer.
I don't understand because my hostname has a good certificate with let's encrypt it's not a self-signed.
my question, what's the good configuration to have synapse and mxisd on the same server and same domain ....
Have a nice day.
Hello,
I have resolved this by this one.
sudo vi /etc/nginx/conf.d/matrix.conf
change the line :
ssl_certificate /etc/letsencrypt/live/www.xxxxx.com/cert.pem;
by the line
ssl_certificate /etc/letsencrypt/live/www.xxxxx.com/fullchain.pem;
service nginx restart
and it's work like a charm ;-)
Many Thanks for your support ps : may be interesting for somebody
K
Hello,
I can't use mxisd with matrix correctly. this is a fresh install of today with debian 9. mxisd and matrix are on the same system and same domain
after couple of hours to debug, i don't understand.
Many thanks for you help K