TURN connectivity check fails in specific network conditions about spreed HOT 3 CLOSED

The issue happens only when the Nextcloud instance is on the same internal network as the TURN server.

The issue is probably that the Nextcloud instance is not able to connect to the TURN server. Please check the logs, there should be a more detailed explanation of what went wrong. Most likely it's the certificate check and either the certificate is not valid (but then connection might not work) or no connection to check the certificate.
Otherwise having the instance on the same networks should not cause any issues.

from spreed.

Thanks @SystemKeeper .

Your analysis is correct:

{
  "reqId": "M6eaNeQQVRAM2OqLhV28",
  "level": 3,
  "time": "2024-06-25T11:30:12+02:00",
  "remoteAddr": "XXX.XXX.XXX.XXX",
  "user": "nc-admin",
  "app": "PHP",
  "method": "GET",
  "url": "/ocs/v2.php/apps/spreed/api/v1/certificate/expiration?host=turn.mydomain.com:443",
  "message": "stream_socket_client(): Unable to connect to ssl://turn.mydomain.com:443 (Connection timed out) at /var/www/nextcloud/apps/spreed/lib/Service/CertificateService.php#107",
  "userAgent": "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:127.0) Gecko/20100101 Firefox/127.0",
  "version": "29.0.2.2",
  "data": {
    "app": "PHP"
  }
}

If Nextcloud instance resolves the turn hostname to its internal IP, both connectivity check and calls work as expected.

from spreed.

Thanks for the info! So this seems to work as intended then.

from spreed.