summary refs log tree commit diff
path: root/docs/turn-howto.md
diff options
context:
space:
mode:
authorPatrick Cloke <clokep@users.noreply.github.com>2023-09-08 09:47:36 -0400
committerGitHub <noreply@github.com>2023-09-08 09:47:36 -0400
commit5c8870cb28cc98d0b7a310b5dd2fade7ff45743d (patch)
treef8a8392b2f04e764daa3a7170078496087e4e147 /docs/turn-howto.md
parentFix bug with new task scheduler using lots of CPU. (#16278) (diff)
downloadsynapse-5c8870cb28cc98d0b7a310b5dd2fade7ff45743d.tar.xz
Fix-up incorrect spellings in docs. (#16282)
Diffstat (limited to 'docs/turn-howto.md')
-rw-r--r--docs/turn-howto.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/turn-howto.md b/docs/turn-howto.md

index 4e9e4117cd..9c1c6f4777 100644 --- a/docs/turn-howto.md +++ b/docs/turn-howto.md
@@ -18,7 +18,7 @@ This documentation provides two TURN server configuration examples: For TURN relaying to work, the TURN service must be hosted on a server/endpoint with a public IP. -Hosting TURN behind NAT requires port forwaring and for the NAT gateway to have a public IP. +Hosting TURN behind NAT requires port forwarding and for the NAT gateway to have a public IP. However, even with appropriate configuration, NAT is known to cause issues and to often not work. Afterwards, the homeserver needs some further configuration.