<![CDATA[One of my Peertubes is in an error state since updating to Cloudron 8.2.3]]>It's telling me that port 1936 is already in use, but I'm not sure what by. My other Peertube is on 1934 and my OwnCast is on 1938

Bind for 0.0.0.0:1936 failed: port is already allocated

Although I note the Peertube docs say:

Bear in mind that enabling live streaming will make your server listen on port 1935/TCP (and 1936/TCP if RTMPS is enabled), which is required for incoming RTMP by your streamers. The listening port can be changed in the PeerTube configuration file.

So maybe my other Peertube is using 1936 automatically.

The thing is, I can't even try changing the port on the non working instance as it's in an error state and so it won't let me do anything to it? 🤔

And looking in the File Manager to see if I can do anything re The listening port can be changed in the PeerTube configuration file. I don't see any values the the files there I could change.

Help!

]]>https://forum.cloudron.io/topic/13100/one-of-my-peertubes-is-in-an-error-state-since-updating-to-cloudron-8-2-3RSS for NodeTue, 19 May 2026 09:14:14 GMTSun, 12 Jan 2025 19:09:48 GMT60<![CDATA[Reply to One of my Peertubes is in an error state since updating to Cloudron 8.2.3 on Sun, 12 Jan 2025 22:00:03 GMT]]>I think this issue was somehow resolved by rebooting my server 🤷

]]>https://forum.cloudron.io/post/99813https://forum.cloudron.io/post/99813Sun, 12 Jan 2025 22:00:03 GMT<![CDATA[Reply to One of my Peertubes is in an error state since updating to Cloudron 8.2.3 on Sun, 12 Jan 2025 19:41:37 GMT]]>Out of interest I stopped the other instance of Peertube to see if that would help. It didn't. Nor did additionally stopping Owncast.

How can I find out which app is using 1936?

]]>https://forum.cloudron.io/post/99802https://forum.cloudron.io/post/99802Sun, 12 Jan 2025 19:41:37 GMT