I had similar experience with live video. It worked in a way that peertube gets a stream and the live video is started and stopped if I stop the stream. I used OBS for streaming as mentioned in the peertube documentation.
But I never saw a running video, just the loading circle forever as you reported.
I added a custom firewall rule because I saw entries in firewall log, in this case I copied the example mysql rule fragment (this could be optimized like using an own fragment)
mkdir -p /etc/e-smith/templates-custom/etc/shorewall/rules/
cp /etc/e-smith/templates/etc/shorewall/rules/65aqua /etc/e-smith/templates-custom/etc/shorewall/rules/
nano /etc/e-smith/templates-custom/etc/shorewall/rules/65aqua
Added following line:
ACCEPT aqua $FW tcp - 9000
After that I had no new entries regarding peertube in firewall.log anymore.
It’s autoconfigured and allowed from green because the ports are used in docker.
I hope it’s just a cosmetic issue.
Maybe it’s from the .env configuration:
PEERTUBE_WEBSERVER_PORT=80
I’m going to test some more the next days…