Diagnosis: Port 5350 related to coturn-synapse is not reachable from outside

Hello everybody. I’m fairly new to this having only been running a Yunohost server for a couple of months. I’m mostly very happy but I’m getting a problem described below. Hope someone can help.
Thanks

My YunoHost server

Hardware: Acer Aspire Revo 3700

YunoHost version: 4.0.4

I have access to my server : Through SSH & through the webadmin & direct access via keyboard / screen
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : yes
If yes, please explain:

I updated & migrated to current version after which PostgreSQL was broken. Uninstalled it and also Mastodon & Synapse. Reinstalled all of these.

Description of my issue

Diagnosis reports Port 5350 is not reachable from outside. although the firewall reports this port is open for TCP & UDP. I would like to know if the diagnosis is reporting correctly and, if so, what I can do to rectify the situation. I have tried closing and reopening the ports through the firewall. The server is in the DMZ so I don’t think port forwarding on the router should be necessary. Please correct me if I’m wrong.

Do you know if that port is related to a specific app/service ?

Yes, it’s the coturn-synapse service.

I have this exact issue, but only after the last synapse update. Synapse seems to be working fine and the port is open according to firewall.

I have this exact issue, but only after the last synapse update. Synapse seems to be working fine and the port is open according to firewall.

i have the same issue

ping @Josue : maybe you have some more clue about this … I see that it’s in fact related to the “alt” port so maybe there isn’t any service listening to it by default if the first port does work …?

Edit : i see the doc says :

# Alternative listening port for TLS and DTLS protocols.
# Default (or zero) value means "TLS listening port plus one".
#
#alt-tls-listening-port=0

So maybe keeping the default / zero value would be good enough ? :confused:

Fwiw:

root@nicofrand:/etc/apt/sources.list.d# netstat -plnt | grep 5349
tcp        0      0 172.17.0.1:5349         0.0.0.0:*               LISTEN      10309/turnserver
tcp        0      0 monip:5349      0.0.0.0:*               LISTEN      10309/turnserver
tcp        0      0 127.0.0.1:5349          0.0.0.0:*               LISTEN      10309/turnserver
tcp        0      0 172.17.0.1:5349         0.0.0.0:*               LISTEN      10309/turnserver
tcp        0      0 monip:5349      0.0.0.0:*               LISTEN      10309/turnserver
tcp        0      0 127.0.0.1:5349          0.0.0.0:*               LISTEN      10309/turnserver
tcp        0      0 172.17.0.1:5349         0.0.0.0:*               LISTEN      10309/turnserver
tcp        0      0 monip:5349      0.0.0.0:*               LISTEN      10309/turnserver
tcp        0      0 172.17.0.1:5349         0.0.0.0:*               LISTEN      10309/turnserver
tcp        0      0 127.0.0.1:5349          0.0.0.0:*               LISTEN      10309/turnserver
tcp        0      0 monip:5349      0.0.0.0:*               LISTEN      10309/turnserver
tcp        0      0 127.0.0.1:5349          0.0.0.0:*               LISTEN      10309/turnserver
tcp6       0      0 ::1:5349                :::*                    LISTEN      10309/turnserver
tcp6       0      0 monipv6:::5349 :::*                    LISTEN      10309/turnserver
tcp6       0      0 ::1:5349                :::*                    LISTEN      10309/turnserver
tcp6       0      0 monipv6:::5349 :::*                    LISTEN      10309/turnserver
tcp6       0      0 ::1:5349                :::*                    LISTEN      10309/turnserver
tcp6       0      0 monipv6:::5349 :::*                    LISTEN      10309/turnserver
tcp6       0      0 ::1:5349                :::*                    LISTEN      10309/turnserver
tcp6       0      0 monipv6:::5349 :::*                    LISTEN      10309/turnserver
root@nicofrand:/etc/apt/sources.list.d# netstat -plnt | grep 5350
root@nicofrand:/etc/apt/sources.list.d#

what can we do about this problem ? - Port 5350 is still marked as not reachable from outside

I believe it’s in fact expected that it’s not reachable from the outside (or more precisely that there’s no process listening/answering on that port) so I would just click the Ignore button for this specific report

OK Thanks

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.