Matrix - synapse

Howto
141

is that the port your are using on your case?

was it adjuested on the confi when installing?

8448 is whats defined for matrix vhost

142

Yes on both questions

Michel-André

143

i am afraid in this case i am not sure how to assist.

meanwhile, try using the default defined parameters to re-deploy and see if it work. if it does,
use that to identify where the problem might be, and share. we might encounter a similar problem.

With that said, i think the install instructions need to now go to the wiki.

1 Like
144

I couldn’t reproduce it, inviting matrix.org members to local rooms and community is working here with the new element version.

In your github issue post you wrote

I redirected all chat.example.org and all its CNAME to LOCAL VM

I use port forwarding for redirecting from the router to the local VM with matrix installed.
If you use reverse proxy for forwarding to your local VM then you may need to add nocanon to your reverse proxy config.

145

Hi @mrmarkuz,

Here is the line I am using:

        ProxyPass /_matrix http://127.0.0.1:8008/_matrix nocanon

Can you see or join one of your room from https://riot.im/app/# ?

Michel-André

146

I assume that this is the line on your VM where matrix is running and it’s ok but if you use reverse proxy from your router to your local VM you may add the nocanon option on your router.

147

I use my main NS server and redirect to my LOCAL VM

Michel-André

148

OK, so you directly reverse proxy from the NS server to your local VM. That should be ok.

I’m going to test it


149

You can look at the Federation check:

https://federationtester.matrix.org/api/report?server_name=chat.micronator-dev.org

Michel-André

150

It’s working here. I created a public room on my matrix server.
On riot.im I needed to enter the complete room name to find my created room.
Additionally I needed to log in to riot.im because guests were not allowed to my room.

There are some differences in our federation test reports, here is the report of my installation:

My Addrs shows port 8448 whereas yours shows 443. Did you test the delegation?

EDIT:

Maybe you just need to port forward port 8448 to your local VM?

151

If I put 8448, the Federation check loop and loop for ever wihout result.

I forwarded 8008, 8443 and 8448 to LOCAL

Michel-André

152

I have forwarded 80, 443 and 8448 to my local VM.

153

I just found a typo, 8048 instead of 8448 :frowning:

I will test again


Michel-André

154

Same thing.

I guess the best is to start all over


Michel-André

155

Did you forward 443 to your local VM?

I’ve gone through the howto today and it seems still working, good luck!

1 Like
156

after fixing the typo, did you restart synapse

157

@mrmarkuz have you attempted delegation using Nethserver, i would love to do it, but i guess my knwoledge of reverse proxy and dns is limited.
not sure how or where to start.

would love to also add that on the tutorial.

158

It seems delegation is just to avoid port 8448, see delegation FAQ.
I’m going to test it and report.

159

Yes after clearing the station and browser caches.

Michel-André

160

Hi @mrmarkuz,

With .well-known delegation, federating servers will check for a valid TLS certificate for the delegated hostname (in our example: synapse.example.com ).

I suspect that the federating servers will check the TLS cerificate I required with my main server in the name of the LOCAL server which is different from the TLS certificate I required with acme.sh from the LOCAL server.

I wonder if it will be better to copy the TLS certificate from the main server to the LOCAL server ?

Michel-André