Stream from outside the network breaks off - Issue solved?

[TheDreadPirate]

No. you have to change your caddy settings so that it listens on a different port. whatever port you pick you have to change your port forwarding settings in your router to use that port.

[Burkhazad]

Sorry, I've been very busy at work this week.

Hadn't managed it yet. I messed something up, I'll try changing the port again tomorrow morning.

I've now got the playback problem on the Android TV under control. Had to set the WAN stream on the client down to 5 MBps at 15 Mbit.

The other one is desperate, even at 4 MBps it hangs. Here it runs in the device's own Panasonic browser via a "GigaCube". So always via transcoding.

The log always says with:
[2024-01-06 16:20:31.907 +01:00] [INF] FFmpeg exited with code 0

From time to time:
[2024-01-06 16:07:43.565 +01:00] [INF] Sending ForceKeepAlive message to 1 inactive WebSockets.
[2024-01-06 16:07:55.569 +01:00] [INF] Lost 1 WebSockets.

I'll get back to the port change tomorrow and try again here. But for my personal understanding, what i have to do - Screenshots attached to this post. (at last point, switching Caddy from Domain to Port)

Perhaps you have some instructions?
Or would it be better for Jellyfin to switch to Apache for use as a reverse proxy?


Or would it be even better:
Router incoming port 80 - forwarding to 8096
Router incoming port 443 - forwarding to port 8920

However, I am probably facing the problem with the SSL certificate again in order to integrate or obtain this correctly. But I think I have a free one at No-IP and would just have to apply for it.

Is it better to use software or hardware encoding with the Ryzen 7 - 5700G?

Last Edit:
SHould it be, that my problem is the same like?
https://github.com/jellyfin/jellyfin/issues/10449

[TheDreadPirate]

Are you connecting with http or https? Why are you redirecting from 80 to 8080 via your DNS provider?

[Burkhazad]

Hello,

so the browser switches to https when I just enter the domain.

No, at the moment everything is running on the standard ports 80 and 443, but since you said I should change the port because my ISP might be causing a problem on that port, it was more a question of whether I need to change it there.

The first was the DNS provider, the second was the port forwarding in the router. If I just set Caddy to a different port, won't it also arrive at port 80/443 via the ISP? That's exactly what I didn't understand about your statement.

[TheDreadPirate]

If you use a non-standard port you would need to type that into the address bar.

https://jellyfin.domain.tld:40443

or something like that.

Change the caddy config so that the remote port is not port 80 or 443.
Change your port forwarding rule.
Make sure to include that port when you type in the address.

[DaneO]

Jellyfins,

everyone is getting hung up on the network and Caddy setup - but per OP everything was working fine *before* they performed a hardware upgrade.

We know that they had to go to a different Ethernet card due to driver issues, I think starting there would be a better plan.

I am assuming Jellyfin has some kind of handshake with the client during playback to ensure it won't continue to transcode or stream a file which is no longer needed - what conditions need to exist during this continual handshake for Jellyfin to break off and stop processing/transcoding/streaming the file?

OP - you're in Germany and mentioned connecting thru a GigaCube below - are you streaming your whole setup over cellular?  Or was that just a client?

Thanks,
 Dane

Good evening, everyone,

I upgraded my hardware and updated to v10.8.13 at the same time.

Since then I've had the problem that the stream stops after a while when it runs via the dynamic DNS. When exactly is different.
It didn't matter whether it was "Direct Play" or transcoding (audio only or complete)

Hardware:
MSI B550A-Pro
AMD Ryzen 7 5700G
32 GB RAM
BrosTrend 2.5GBase-T PCIe network card (due to driver problems)

Internet:
250Mbit downstream, 40-45Mbit upstream

System:
Ubuntu Server 22.04 LTS
Linux 5.15.0-91-generic on x86_64
Webmin 2.105
Jellyfin 10.08.13 (installation via repository - automatic)
Caddy as reverse proxy via Caddyfile - works

Clients:
AndroidTV 0.16.1
Jellyfin Web 10.8.13 via Chrome on PanasonicTV

Unfortunately I don't know what is meant by logs on debug level (English not my native language)

SystemLog entries:
Slow HTTP Response from "https://***/Sessions/Playing/Progress" to "109.42.***.***" in 0:00:00.8038239 with Status Code 204
AuthenticationScheme: "CustomAuthentication" was forbidden (flooding)

Transcoding runs through and is finished before the client suddenly stops. Hardware acceleration does not matter, happens both with and without it.

Is it me, a setting, the Jellyfin version? Before the upgrade (hardware) and the update (JellyFin) everything ran without any problems.

I'm wondering if I should switch to Windows to maybe fix the problem.

[Burkhazad]

Jellyfins,

everyone is getting hung up on the network and Caddy setup - but per OP everything was working fine *before* they performed a hardware upgrade.

We know that they had to go to a different Ethernet card due to driver issues, I think starting there would be a better plan.

I am assuming Jellyfin has some kind of handshake with the client during playback to ensure it won't continue to transcode or stream a file which is no longer needed - what conditions need to exist during this continual handshake for Jellyfin to break off and stop processing/transcoding/streaming the file?

OP - you're in Germany and mentioned connecting thru a GigaCube below - are you streaming your whole setup over cellular?  Or was that just a client?

Thanks,
 Dane

Hello Dane

The GigaCube is only at the client. Full reception and sufficient speed are probably also available here. I will receive the Cube this week to test it myself and to rule out the possibility that the WLAN connection from the Cube to the Panasonic TV is the problem.

The server itself is connected to a "fixed" Internet connection. Speedport Smart 4 is the router and I use the 2.5 Gbit socket on this.  With my ISP I have a 250Mbit/40-45 Mbit connection. I set a maximum of 15 Mbit per client in the settings

The FireTV client has a 50 Mbit line, TV is connected via cable and I still had to set it to 5Mbit stream.

Regarding the network connection, Linux and the mainboard B550A-Pro have some problems with the chip, hence the card for the PCIexp slot. The mainboard network is completely deactivated in the bios. Chip is Realtek RTL8111H Gigabit LAN

However, I have to say that everything works on the internal network. I have MagentaTV One, but so far it has played everything in DirectPlay.

[Burkhazad]

Hello, so no matter how I do it, I just can't get it with other ports to access Jellyfin at all.
Apparently too stupid.

I had the GigaCube here for a short time and tried it on a freshly installed notebook without any additional software. Here it worked without any problems. However, the transcoding was not yet finished.

In addition, I have now integrated the r8168 driver, blacklisted the r8169 and am currently back on the on-board network connection.

Slowly I don't know what to do and as I said, I can't get other ports to work.

I'm thinking about switching to Windows or setting up an Unraid system.

[Burkhazad]

I have now checked the box for throttling transcoding as a test. After an initial hang, where the client speed was set from 5 Mbps to 10/15 Mbps, everything went through without any further stops/interruptions or aborts.

Perhaps that was the sticking point, even if I don't fully understand or comprehend it.
The hardware is more powerful and normally it is better if the file to be played is already transcoded.

Does anyone have an explanation for this?

[TheDreadPirate]

Aliens? Nothing about your problem makes sense, honestly.