astral0pitek's blog

Yesterday I had a need to show a person how the game Armored Core 6 is played with the help of a stream (and I myself wanted to show this game). Of course, I wouldn’t go to “Twitch” or “YouTube”, I wouldn’t go because I hating these platforms, and “Glimesh” streaming platform on which I settled is still quite unstable, I decided to use my PeerTube instance, which I have deployed for all my friends and communities in which I actively participate (1-2 communities. Yes, very few, but nevertheless I am ready to provide them with my resources of my modest home nas server). And I ran into a problem that I didn’t want to solve for a very long time, because I didn’t need it and no one uses my services except me. Stream categorically refused to start. As it turned out after almost the whole day, my service simply did not support the codec in which I tried to stream it and because of this an error occurred (I just spent a day to finally learn how to watch PeerTube logs). Also, during the stream, in addition, it turned out that my server was so weak that it was not able to render a live broadcast in the required resolution for a long time, and after a while, due to overload, it dropped the connection and flatly refused any streams for a couple of minutes until it cleared all the previous ones frames. As a result, I turned off rendering for broadcasts and my broadcast server began to feel much better. Plus, while searching for the first problem, I corrected a couple of proxy settings (removed this setting despite the fact that I have a docker container in the bridge through my server's proxy) and now my PeerTube instance again sees external IP addresses from which people come in, which brought back the possibility of analytics on the instance.