-
Hello. I'm trying to stream on my Peertube instance and I get this error. Do you know where it comes from?
Aug 12 20:40:48 [peertube.cocamserverguild.com:443] 2024-08-12 18:40:48.339 info: Live session ended. { Aug 12 20:40:48 "sessionId": "N50A77VF" Aug 12 20:40:48 } Aug 12 20:40:49 172.18.0.1 - - [12/Aug/2024:18:40:49 +0000] "GET /api/v1/search/videos?start=0&count=7&skipCount=true&nsfw=both&tagsOneOf=Ancenis&tagsOneOf=Coll%C3%A8ge%20Cadou&tagsOneOf=SEGPA&tagsOneOf=ULIS&sort=-publishedAt&searchTarget=local HTTP/1.1" 200 11 "https://peertube.cocamserverguild.com/w/abY4fUwHWfQCgLwUCJEgaG" "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.6478.182 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" Aug 12 20:40:49 [peertube.cocamserverguild.com:443] 2024-08-12 18:40:49.310 info: 66.249.66.32 - - [12/Aug/2024:18:40:49 +0000] "GET /api/v1/search/videos?start=0&count=7&skipCount=true&nsfw=both&tagsOneOf=Ancenis&tagsOneOf=Coll%C3%A8ge%20Cadou&tagsOneOf=SEGPA&tagsOneOf=ULIS&sort=-publishedAt&searchTarget=local HTTP/1.0" 200 11 "https://peertube.cocamserverguild.com/w/abY4fUwHWfQCgLwUCJEgaG" "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.6478.182 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" Aug 12 20:40:49 [peertube.cocamserverguild.com:443] 2024-08-12 18:40:49.651 error: Client log: HLS.js error: mediaError - fatal: true - manifestIncompatibleCodecsError { Aug 12 20:40:49 "userAgent": "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.6478.182 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", Aug 12 20:40:49 "meta": "{"currentTime":0,"data":{"type":"mediaError","details":"manifestIncompatibleCodecsError","fatal":true,"url":"https://tube-arts-lettres-sciences-humaines.apps.education.fr/static/streaming-playlists/hls/4a6a3b41-ceeb-4f68-828a-de820064da5e/ba26b32b-a261-4d92-977e-ab8648c5070e-master.m3u8","error":{},"reason":"no level with compatible codecs found in manifest"}}", Aug 12 20:40:49 "url": "https://peertube.cocamserverguild.com/w/abY4fUwHWfQCgLwUCJEgaG" Aug 12 20:40:49 } Aug 12 20:40:49 [peertube.cocamserverguild.com:443] 2024-08-12 18:40:49.653 info: 66.249.66.32 - - [12/Aug/2024:18:40:49 +0000] "POST /api/v1/server/logs/client HTTP/1.0" 204 - "https://peertube.cocamserverguild.com/w/abY4fUwHWfQCgLwUCJEgaG" "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.6478.182 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" Aug 12 20:40:49 172.18.0.1 - - [12/Aug/2024:18:40:49 +0000] "POST /api/v1/server/logs/client HTTP/1.1" 204 0 "https://peertube.cocamserverguild.com/w/abY4fUwHWfQCgLwUCJEgaG" "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.6478.182 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" Aug 12 20:40:50 172.18.0.1 - - [12/Aug/2024:18:40:50 +0000] "GET / HTTP/1.1" 200 6496 "-" "Mozilla (CloudronHealth)" Aug 12 20:40:50 [peertube.cocamserverguild.com:443] 2024-08-12 18:40:50.027 info: 172.18.0.1 - - [12/Aug/2024:18:40:50 +0000] "GET / HTTP/1.0" 200 17552 "-" "Mozilla (CloudronHealth)" Aug 12 20:40:54 [peertube.cocamserverguild.com:443] 2024-08-12 18:40:54.294 info: Cleanup TMP live files from object storage for c05f0808-61f6-48b8-9739-8a4cce5e3aac. Aug 12 20:41:00 [peertube.cocamserverguild.com:443] 2024-08-12 18:41:00.044 info: 172.18.0.1 - - [12/Aug/2024:18:41:00 +0000] "GET / HTTP/1.0" 200 17552 "-" "Mozilla (CloudronHealth)" Aug 12 20:41:00 172.18.0.1 - - [12/Aug/2024:18:41:00 +0000] "GET / HTTP/1.1" 200 6496 "-" "Mozilla (CloudronHealth)" Aug 12 20:41:04 [peertube.cocamserverguild.com:443] 2024-08-12 18:41:04.687 info: Receiving inbox requests for 1 activities by https://peervideo.club/accounts/peertube. Aug 12 20:41:04 172.18.0.1 - - [12/Aug/2024:18:41:04 +0000] "POST /inbox HTTP/1.1" 204 0 "-" "PeerTube/6.2.1 (+https://peervideo.club)" Aug 12 20:41:04 [peertube.cocamserverguild.com:443] 2024-08-12 18:41:04.693 info: 38.242.212.101 - - [12/Aug/2024:18:41:04 +0000] "POST /inbox HTTP/1.0" 204 - "-" "PeerTube/6.2.1 (+https://peervideo.club)" Aug 12 20:41:06 [peertube.cocamserverguild.com:443] 2024-08-12 18:41:06.070 error: Cannot handle session { Aug 12 20:41:06 "err": { Aug 12 20:41:06 "stack": "AggregateError [ETIMEDOUT]: \n at internalConnectMultiple (node:net:1117:18)\n at afterConnectMultiple (node:net:1684:7)", Aug 12 20:41:06 "errors": [ Aug 12 20:41:06 { Aug 12 20:41:06 "stack": "Error: connect ETIMEDOUT 172.233.64.160:443\n at createConnectionError (node:net:1647:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1706:38)\n at listOnTimeout (node:internal/timers:575:11)\n at process.processTimers (node:internal/timers:514:7)", Aug 12 20:41:06 "message": "connect ETIMEDOUT 172.233.64.160:443", Aug 12 20:41:06 "errno": -110, Aug 12 20:41:06 "code": "ETIMEDOUT", Aug 12 20:41:06 "syscall": "connect", Aug 12 20:41:06 "address": "172.233.64.160", Aug 12 20:41:06 "port": 443 Aug 12 20:41:06 }, Aug 12 20:41:06 { Aug 12 20:41:06 "stack": "Error: connect ETIMEDOUT 2400:8905::f03c:93ff:fe9a:239b:443\n at createConnectionError (node:net:1647:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1706:38)\n at listOnTimeout (node:internal/timers:575:11)\n at process.processTimers (node:internal/timers:514:7)", Aug 12 20:41:06 "message": "connect ETIMEDOUT 2400:8905::f03c:93ff:fe9a:239b:443", Aug 12 20:41:06 "errno": -110, Aug 12 20:41:06 "code": "ETIMEDOUT", Aug 12 20:41:06 "syscall": "connect", Aug 12 20:41:06 "address": "2400:8905::f03c:93ff:fe9a:239b", Aug 12 20:41:06 "port": 443 Aug 12 20:41:06 }, Aug 12 20:41:06 { Aug 12 20:41:06 "stack": "Error: connect ETIMEDOUT 172.233.64.157:443\n at createConnectionError (node:net:1647:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1706:38)\n at listOnTimeout (node:internal/timers:575:11)\n at process.processTimers (node:internal/timers:514:7)", Aug 12 20:41:06 "message": "connect ETIMEDOUT 172.233.64.157:443", Aug 12 20:41:06 "errno": -110, Aug 12 20:41:06 "code": "ETIMEDOUT", Aug 12 20:41:06 "syscall": "connect", Aug 12 20:41:06 "address": "172.233.64.157", Aug 12 20:41:06 "port": 443 Aug 12 20:41:06 }, Aug 12 20:41:06 { Aug 12 20:41:06 "stack": "Error: connect ETIMEDOUT 2400:8905::f03c:93ff:fe9a:2375:443\n at createConnectionError (node:net:1647:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1706:38)\n at listOnTimeout (node:internal/timers:575:11)\n at process.processTimers (node:internal/timers:514:7)", Aug 12 20:41:06 "message": "connect ETIMEDOUT 2400:8905::f03c:93ff:fe9a:2375:443", Aug 12 20:41:06 "errno": -110, Aug 12 20:41:06 "code": "ETIMEDOUT", Aug 12 20:41:06 "syscall": "connect", Aug 12 20:41:06 "address": "2400:8905::f03c:93ff:fe9a:2375", Aug 12 20:41:06 "port": 443 Aug 12 20:41:06 }, Aug 12 20:41:06 { Aug 12 20:41:06 "stack": "Error: connect ETIMEDOUT 172.233.64.156:443\n at createConnectionError (node:net:1647:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1706:38)\n at listOnTimeout (node:internal/timers:575:11)\n at process.processTimers (node:internal/timers:514:7)", Aug 12 20:41:06 "message": "connect ETIMEDOUT 172.233.64.156:443", Aug 12 20:41:06 "errno": -110, Aug 12 20:41:06 "code": "ETIMEDOUT", Aug 12 20:41:06 "syscall": "connect", Aug 12 20:41:06 "address": "172.233.64.156", Aug 12 20:41:06 "port": 443 Aug 12 20:41:06 }, Aug 12 20:41:06 { Aug 12 20:41:06 "stack": "Error: connect ETIMEDOUT 2400:8905::f03c:93ff:fe9a:239e:443\n at createConnectionError (node:net:1647:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1706:38)\n at listOnTimeout (node:internal/timers:575:11)\n at process.processTimers (node:internal/timers:514:7)", Aug 12 20:41:06 "message": "connect ETIMEDOUT 2400:8905::f03c:93ff:fe9a:239e:443", Aug 12 20:41:06 "errno": -110, Aug 12 20:41:06 "code": "ETIMEDOUT", Aug 12 20:41:06 "syscall": "connect", Aug 12 20:41:06 "address": "2400:8905::f03c:93ff:fe9a:239e", Aug 12 20:41:06 "port": 443 Aug 12 20:41:06 }, Aug 12 20:41:06 { Aug 12 20:41:06 "stack": "Error: connect ETIMEDOUT 172.233.64.158:443\n at createConnectionError (node:net:1647:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1706:38)\n at listOnTimeout (node:internal/timers:575:11)\n at process.processTimers (node:internal/timers:514:7)", Aug 12 20:41:06 "message": "connect ETIMEDOUT 172.233.64.158:443", Aug 12 20:41:06 "errno": -110, Aug 12 20:41:06 "code": "ETIMEDOUT", Aug 12 20:41:06 "syscall": "connect", Aug 12 20:41:06 "address": "172.233.64.158", Aug 12 20:41:06 "port": 443 Aug 12 20:41:06 }, Aug 12 20:41:06 { Aug 12 20:41:06 "stack": "Error: connect ETIMEDOUT 2400:8905::f03c:93ff:fe9a:230e:443\n at createConnectionError (node:net:1647:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1706:38)\n at listOnTimeout (node:internal/timers:575:11)\n at process.processTimers (node:internal/timers:514:7)", Aug 12 20:41:06 "message": "connect ETIMEDOUT 2400:8905::f03c:93ff:fe9a:230e:443", Aug 12 20:41:06 "errno": -110, Aug 12 20:41:06 "code": "ETIMEDOUT", Aug 12 20:41:06 "syscall": "connect", Aug 12 20:41:06 "address": "2400:8905::f03c:93ff:fe9a:230e", Aug 12 20:41:06 "port": 443 Aug 12 20:41:06 }, Aug 12 20:41:06 { Aug 12 20:41:06 "stack": "Error: connect ETIMEDOUT 172.233.64.159:443\n at createConnectionError (node:net:1647:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1706:38)\n at listOnTimeout (node:internal/timers:575:11)\n at process.processTimers (node:internal/timers:514:7)", Aug 12 20:41:06 "message": "connect ETIMEDOUT 172.233.64.159:443", Aug 12 20:41:06 "errno": -110, Aug 12 20:41:06 "code": "ETIMEDOUT", Aug 12 20:41:06 "syscall": "connect", Aug 12 20:41:06 "address": "172.233.64.159", Aug 12 20:41:06 "port": 443 Aug 12 20:41:06 }, Aug 12 20:41:06 { Aug 12 20:41:06 "stack": "Error: connect ETIMEDOUT 2400:8905::f03c:93ff:fe9a:2304:443\n at createConnectionError (node:net:1647:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1706:38)\n at listOnTimeout (node:internal/timers:575:11)\n at process.processTimers (node:internal/timers:514:7)", Aug 12 20:41:06 "message": "connect ETIMEDOUT 2400:8905::f03c:93ff:fe9a:2304:443", Aug 12 20:41:06 "errno": -110, Aug 12 20:41:06 "code": "ETIMEDOUT", Aug 12 20:41:06 "syscall": "connect", Aug 12 20:41:06 "address": "2400:8905::f03c:93ff:fe9a:2304", Aug 12 20:41:06 "port": 443 Aug 12 20:41:06 }, Aug 12 20:41:06 { Aug 12 20:41:06 "stack": "Error: connect ETIMEDOUT 172.233.64.155:443\n at createConnectionError (node:net:1647:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1706:38)\n at listOnTimeout (node:internal/timers:575:11)\n at process.processTimers (node:internal/timers:514:7)", Aug 12 20:41:06 "message": "connect ETIMEDOUT 172.233.64.155:443", Aug 12 20:41:06 "errno": -110, Aug 12 20:41:06 "code": "ETIMEDOUT", Aug 12 20:41:06 "syscall": "connect", Aug 12 20:41:06 "address": "172.233.64.155", Aug 12 20:41:06 "port": 443 Aug 12 20:41:06 }, Aug 12 20:41:06 { Aug 12 20:41:06 "stack": "Error: connect EHOSTUNREACH 2400:8905::f03c:93ff:fe9a:2315:443\n at createConnectionError (node:net:1647:14)\n at afterConnectMultiple (node:net:1677:16)", Aug 12 20:41:06 "message": "connect EHOSTUNREACH 2400:8905::f03c:93ff:fe9a:2315:443", Aug 12 20:41:06 "errno": -113, Aug 12 20:41:06 "code": "EHOSTUNREACH", Aug 12 20:41:06 "syscall": "connect", Aug 12 20:41:06 "address": "2400:8905::f03c:93ff:fe9a:2315", Aug 12 20:41:06 "port": 443 Aug 12 20:41:06 } Aug 12 20:41:06 ], Aug 12 20:41:06 "code": "ETIMEDOUT", Aug 12 20:41:06 "name": "TimeoutError", Aug 12 20:41:06 "$metadata": { Aug 12 20:41:06 "attempts": 3, Aug 12 20:41:06 "totalRetryDelay": 246 Aug 12 20:41:06 } Aug 12 20:41:06 } Aug 12 20:41:06 } -
N nebulon moved this topic from Support on
-
N nebulon marked this topic as a question on
-
N nebulon has marked this topic as solved on
-
J joseph has marked this topic as unsolved on
-
@cocam123 Are you getting the same errors you posted initially ?
Aug 12 20:41:06 "message": "connect ETIMEDOUT 172.233.64.155:443",
Assuming the above is your IP, maybe loopback connection is not working on your server. Can you run
cloudron-support --troubleshooton your server and see if hairpin NAT works? -
I did it and everything seems okay
[OK] node version is correct
[OK] docker is running
[OK] MySQL is running
[OK] nginx is running
[OK] dashboard cert is valid
[OK] dashboard is reachable via loopback
Service 'box' just started 3 secs ago, checking health again in 10s
[OK] box v8.0.3 is running
[OK] netplan is good
[OK] DNS is resolving via systemd-resolved
[OK] Dashboard is reachable via domain name
[OK] Domain (my domain) is valid and has not expired
[OK] unbound is running -
Basic question:
- Which server parameters and which provider?
- Which provider of object storage?
- How much memory and processor limit allocated?
-
well, to be honest, I don't understand it anymore, because the problem reappears all over again
@cocam123 said in Impossible to stream:
the problem
also, what exactly is the problem? no videos will play? or something to do with live streaming?
do my Peertube sites work OK for you? uniteddiversity.tv bridport.tv
-
This post is deleted!
-
Basic question:
- Which server parameters and which provider?
- Which provider of object storage?
- How much memory and processor limit allocated?
@matix131997 4 CPU, 8 GB RAM and 90 GB SSD for the storage (90 GB just in case). My connection doesn't support IPv6 yet so it's disabled. At least, on the system (I don't know if Cloudron has anything specific on this)
For the object storage, my provider is Akamai
I think that should answer all your questions?
-
@cocam123 said in Impossible to stream:
the problem
also, what exactly is the problem? no videos will play? or something to do with live streaming?
do my Peertube sites work OK for you? uniteddiversity.tv bridport.tv
-
@matix131997 4 CPU, 8 GB RAM and 90 GB SSD for the storage (90 GB just in case). My connection doesn't support IPv6 yet so it's disabled. At least, on the system (I don't know if Cloudron has anything specific on this)
For the object storage, my provider is Akamai
I think that should answer all your questions?
@cocam123 said in Impossible to stream:
4 CPU, 8 GB RAM
that is very little power, could be part of the problem. Most smart phones are more powerful these days. I'd say 16GB RAM is prob the bare minimum you need these days.
-
@jdaviescoates The object storage is not responding (and every time it works, after a few days it doesn't work again)
@cocam123 said in Impossible to stream:
@jdaviescoates The object storage is not responding (and every time it works, after a few days it doesn't work again)
Odd. Perhaps try another object storage provider? Mine keeps working using Scaleway object storage buckets.
-
@cocam123 said in Impossible to stream:
4 CPU, 8 GB RAM
that is very little power, could be part of the problem. Most smart phones are more powerful these days. I'd say 16GB RAM is prob the bare minimum you need these days.
@jdaviescoates It's not the server itself but rather a vps I created to run peertube only on it (so I don't use more than what's required). Cloudron and peertube require about 3 GB of RAM (so I'm using 8 GB)
-
@cocam123 said in Impossible to stream:
@jdaviescoates The object storage is not responding (and every time it works, after a few days it doesn't work again)
Odd. Perhaps try another object storage provider? Mine keeps working using Scaleway object storage buckets.
@jdaviescoates I'll try to request data transfer from one server to another before changing (if this really continues
-
@cocam123
And could you specify the VPS provider ? -
@cocam123
And could you specify the VPS provider ?@matix131997 It's myself directly (dedicated server with proxmox on it) and my connection is always online (the firewall accept connections towards the server)
