Could there be a second package with Live-streaming configured?

[nebulon]

We have just published a new app package which has livestreaming support (the previous didn't have that), however this is still for testing, so please let us know if there is any difference now.

[doodlemania2]

Hey there @nebulon - great work on the bump. I still don't see a change - I peaked at the nginx config and see a websocket port opened, but I think we're still missing something. From https://docs.pixelfed.org/running-pixelfed/optional-features/livestreaming/ it looks like we need an HLS port open as well?

[girish]

@doodlemania2 It's in the manifest :

  "tcpPorts": {
    "HLS_LIVE_PORT": {
      "title": "Live streaming port",
      "description": "Live streaming port (only default works)", 
      "containerPort": 1935,
      "defaultValue": 1935
    }
  },

Can you check the Location section of the app?

[doodlemania2]

Ah - doink, sorry about that. Okay, I ticked the box to turn that on. Still not seeing any changes in the app despite the configs being set. We're still missing something, but not sure what it is. Could be my upstream proxy, will try to route around it to test.

[girish]

@doodlemania2 Spent some time with the android app yesterday but there is no option to enable Live Streaming as such. Are you on iOS or the Android app?

[jdaviescoates]

Sounds like the official apps will be in the apps stores in a month of so.

https://mastodon.social/@pixelfed/110312061392315948

Perhaps those are what is needed to use this?

Presumably everything mentioned in the docs here are now included in the package?

https://docs.pixelfed.org/running-pixelfed/optional-features/livestreaming/

[girish]

@jdaviescoates ah, that's great news. Yes, we have integrated all that's possible. Now, we need something to test it with.

[doodlemania2]

I was hoping the testflight (ios) app just started working when the app is configured. I also set the web app to be a broadcaster (it was an option in the configs) but that didn't change anything either. Perhaps he's holding the code back for the next release or something

[nebulon]

Maybe you could ask upstream what the status is and how it is supposed to work? Otherwise we might look into the entirely wrong corner.

[jaschaezra]

Sorry for my absence - I will go through this thread tomorrow and see what needs to be done because so already was able to stream (on another instance)

[girish]

@jaschaezra Is that instance public for us to test/understand how this feature works ? Also, does one need to enable any option in the mobile app? Where in the mobile app can one stream? Any screenshots will help.

[jaschaezra]

@girish At the moment you need the Pixelfed Live App to stream. Get the apk here: https://dl.apps.pixelcdn.net/pixelfed-live/android/pixelfed-live-v1.0.1-release.apk

As far as I know it should be merged into the iOS and Android App but I do not know the status at the moment. I asked upstream to provide some more info.

[doodlemania2]

@jaschaezra OH! Booooooooo.....

[doodlemania2]

Update:

[LoudLemur]

Port 1935 is the question for me.

Pixelfed wants to use this port by default for livestreaming, and there is a notification saying that only the default works.

However, a couple of other Cloudron packages want Port 1935, too:

PeerTube (and apparently port 1935 is/was hardcoded into it, so you can't/couldn't change it.)
OwnCast (which will work on port 1936 to allow PeerTube to keep port 1935)

So, would Pixelfed livestreams work if you had PeerTube on 1935?

[mhgcic]

Why is it the Pixel App can't just all use the same port, surely the server recognises by URL or similar.

[nebulon]

URL and hostnames are only available depending on the used protocol. Since we are talking about TCP ports here, this usually does not apply. On Linux only one process can listen on a TCP port.

In the more common HTTP case, a reverse proxy will listen on the port and since it understands the protocol, which has a concept of for example hostnames, it can then proxy the traffic accordingly, but that is rather special to HTTP and thus does not apply to other use-cases, which are not HTTP.

[mhgcic]

So am I right in thinking that for the moment I should host pixelfed apps on their own server as only one install of the app can use the default port at a time?

[girish]

@mhgcic What do you mean by "Pixelfed Apps" ? You want to host multiple instances of pixelfed on the server?

[mhgcic]

@girish We asked for more licenses because we wanted to separate our services on separate servers, but when we asked for this we got asked why? And to explain how this would be a benefit to us?

For example, we have a server for our websites like this https://www.mhgresource.directory/

But we have websites like this https://www.landingstrip.social that we would like to keep this websites apps on one server to keep them running at all times, and so that it is not interfered with by other apps or server issues.

We wanted to separate mastodons, discourse etc on servers only for that type of app, to help better manage them and so that not all apps are affected by a server issue.

Also got told to upscale servers to compensate by adding more apps, never getting a reply to my answers to the questions I was asked, so we did not chase it up.

But to answer your question no not really, I want to be able to host multiple Pixelfed apps on one Cloudron server.

But if Pixelfed is locked to using the default port only like in the setup instructions,

I don't understand why it says "only default works" and then shows a port range "1024-65535" when Pixelfed says the default port is 1935. It says to the novice that you can use any port between 1024-65535 even though it says about the default being the only one to work.

And can not use other ports or the same port for all Pixlefed apps then it seems like we would have to host each Pixelfed app on a separate server.

Hope this all make sense.