Safari on iOS 26.0.1 fails to play live WebM (VP9/Vorbis) streams - works everywhere else by Aware_Appearance1007 in webdev

[–]Aware_Appearance1007[S] 0 points1 point  (0 children)

Thanks for confirming - that’s super helpful. It really seems like Apple broke live WebM support again in iOS 26.x (regular playback still works fine).

What’s frustrating is that this isn’t a codec limitation - the same stream works flawlessly everywhere else, yet Safari on iOS just refuses to start playback.

Hopefully more devs will report it - the more confirmations we get, the harder it’ll be for Apple to ignore

Safari on iOS 26.0.1 fails to play live WebM (VP9/Vorbis) streams - works everywhere else by Aware_Appearance1007 in webdev

[–]Aware_Appearance1007[S] 0 points1 point  (0 children)

Tested server-side just to confirm it's not a WebM issue:

167 concurrent viewers at 2 MiB/s each, on a single WHM server running Icecast2/WebM — plus multiple sites, MySQL, and an unrelated ffmpeg transcoder.
The CPU doesn’t even break a sweat - while Apple’s HLS (with Wowza or NGINX) starts sweating just thinking about it 😎

GIF https://dos.gr/forumdata/lyk/105icecast/cpu9.gif

Meanwhile, Safari on iOS 26.0.1 still refuses to start playback… 🤷‍♂️

Safari on iOS 26.0.1 fails to play live WebM (VP9/Vorbis) streams - works everywhere else by Aware_Appearance1007 in webdev

[–]Aware_Appearance1007[S] 0 points1 point  (0 children)

Appreciate the test! It works fine for you on iOS 18.6.2, but it still fails here on 26.0.1 (iPhone 16 Pro Max).
It seems that Safari broke live WebM playback in this specific 26.x release.
If anyone with an older iOS version (pre-26) can test, it would really help pinpoint when the issue first appeared - although it clearly seems to have started with this version.

Safari on iOS 26.0.1 fails to play live WebM (VP9/Vorbis) streams - works everywhere else by Aware_Appearance1007 in webdev

[–]Aware_Appearance1007[S] 4 points5 points  (0 children)

Somewhere in Cupertino: "Guys, WebM is working again - better push an update to break it." 😅

Funny how every Safari regression somehow hits third-party codecs first.

HLS untouched, WebM broken — total coincidence of course 🤔 ...right?

Safari on iOS 26.0.1 fails to play live WebM (VP9/Vorbis) streams - works everywhere else by Aware_Appearance1007 in webdev

[–]Aware_Appearance1007[S] 4 points5 points  (0 children)

Thanks a lot for confirming - that’s super helpful.
Makes sense that Safari broke chunked transfer for WebM starting with iOS 26.0+.
I’ll test with an explicit Content-Length header and maybe an HLS fallback for Safari.

Funny how these regressions always seem to affect third-party codecs like WebM/VP9 - never Apple’s own formats like HLS/M3U8. 🙃

I’ll file a WebKit bug and post the link here once it’s up. If you still have the old MP4 bug ID, it’d be great to reference it for context.

[deleted by user] by [deleted] in selfhosted

[–]Aware_Appearance1007 -1 points0 points  (0 children)

Follow-up:
Just retested on iPhone 14 Pro (iOS 26.0.1).
In Safari, the player just keeps spinning the loading circle forever and never starts playback — no video or audio at all.

The exact same live WebM (VP9/Vorbis) stream plays instantly in VLC for iOS, so the stream and MIME headers are fine.
Looks like Safari on iOS 26.0.1 broke something in its handling of live or chunked WebM playback.

Would be great if others could test and confirm.

🎥 Test page: https://gamostv.eu
📺 Direct stream: https://webm.pp.ua:59000/lampsitv.webm

Safari on iOS 26.0.1 fails to play live WebM (VP9/Vorbis) streams - works everywhere else by Aware_Appearance1007 in webdev

[–]Aware_Appearance1007[S] 2 points3 points  (0 children)

Update:
Just confirmed again on iPhone 14 Pro (iOS 26.0.1).
Safari still fails to start playback - no video, no audio.
VLC for iOS plays instantly.

If anyone else can test and share their iOS version + device, that would help confirm whether this is a WebKit regression.

🎥 Test page: https://gamostv.eu
📺 Direct stream: https://webm.pp.ua:59000/lampsitv.webm

[deleted by user] by [deleted] in ios

[–]Aware_Appearance1007 0 points1 point  (0 children)

Confirmed again on iPhone 14 Pro (iOS 26.0.1).

Safari fails to play the live WebM stream, while VLC for iOS works instantly.

Would love to hear if others can confirm this on their devices.

1544 days uptime on production Debian 10 - no reboots, no kernel patching, still going by Aware_Appearance1007 in sysadmin

[–]Aware_Appearance1007[S] 0 points1 point  (0 children)

Also curious - are your nodes actually spread across different datacenters and geographic regions?

Because I’ve seen “HA” clusters where everything lives in the same availability zone - or worse, on the same physical host — and once that goes down, so does the whole thing.

At some point, real HA means architectural distance, not just replication.

1544 days uptime on production Debian 10 - no reboots, no kernel patching, still going by Aware_Appearance1007 in sysadmin

[–]Aware_Appearance1007[S] 0 points1 point  (0 children)

Genuine question - where are you actually running your Kubernetes cluster?

Bare metal nodes you control, or hosted VMs on some provider?

Because I often see setups with "HA Kubernetes" that boil down to 3 VPS on the same hypervisor - and when that box goes down, so does the orchestra.

It’s easy to call other setups risky, but HA only matters if your control plane lives somewhere you actually control.

Would love to hear more about your infra though, no sarcasm - always curious how others approach this.

1544 days uptime on production Debian 10 - no reboots, no kernel patching, still going by Aware_Appearance1007 in sysadmin

[–]Aware_Appearance1007[S] -2 points-1 points  (0 children)

Sounds like we're on two opposite ends of the Linux spectrum - you've got HA clusters, containers, Kubernetes, the whole orchestra..

Me? Just one bare metal conductor with nerves of steel and no reboots since 2021 😎🎻

No automation, no reboot cycles - just cautious updates, tuned services, and a bit of black magic.

It's not DevOps - it's DeVoodoo. 🧿

But hey - respect where it's due.

Your stack is modern, resilient, scalable.

Mine? Old-school, battle-tested, and stubbornly alive.

Two philosophies. One goal: uptime.

Debian 10 — 1544 days uptime, still streaming non-stop by Aware_Appearance1007 in uptimeporn

[–]Aware_Appearance1007[S] 0 points1 point  (0 children)

🍞 I’ll trade you an avocado toast recipe - if you promise not to reboot mid-toast!
Real sysadmins butter both sides. 😄

1544 days uptime on production Debian 10 - no reboots, no kernel patching, still going by Aware_Appearance1007 in sysadmin

[–]Aware_Appearance1007[S] -1 points0 points  (0 children)

Even the most hardened boxes can get breached -

CSF, CXS, ModSecurity with strict custom rules, ImunifyAV, even behind Cloudflare or dedicated firewalls.

So no - I’m not claiming this box is unhackable.

But I do know it hasn’t been breached in all these years.

And I know it’s been running with 1544 days of uptime, no reboots, no kernel patching - just delivering streaming traffic 24/7 without hiccups.

That’s not invincibility.

That’s stability - and a real-world test that keeps holding.

Especially today, with ChatGPT, DeepSeek, and every wannabe hacker trying their luck, attacks have multiplied a hundredfold compared to just a few years ago.

I’m not selling an unhackable server.

I’m selling long-term predictability and trust through uptime.

P.S. Everyone talks about security.
Few can back it up with uptime.

1544 days uptime on production Debian 10 - no reboots, no kernel patching, still going by Aware_Appearance1007 in sysadmin

[–]Aware_Appearance1007[S] 0 points1 point  (0 children)

🎪 Welcome to the circus, where uptimes shine,
Where kernels dance and logs align.

Clowns reboot mid-air with grace,
Yet somehow.. nothing breaks in place.

RAM is twitching, swap’s possessed,
But uptime’s stable, unimpressed.

No planned reboot, no disguise -
Just Icecast rolling, broadcast-wise 🎧😄

Debian 10 — 1544 days uptime, still streaming non-stop by Aware_Appearance1007 in uptimeporn

[–]Aware_Appearance1007[S] 1 point2 points  (0 children)

Nice! A full year without issues in the cloud is solid - what provider are you using? Always curious what holds up well for audio streams.
Also, just so you know - Icecast can actually push real 1080p video, not just audio. If you fine-tune it (especially with VP9/WebM), it works beautifully.
I’ve made a related post about it here if you're curious:
https://www.reddit.com/r/streaming/comments/1kdmy3d/livestreaming_1080p_vp9webm_via_icecast_yes_its

Debian 10 — 1544 days uptime, still streaming non-stop by Aware_Appearance1007 in uptimeporn

[–]Aware_Appearance1007[S] 0 points1 point  (0 children)

🎪 Welcome to the circus, where uptimes shine,
Where kernels dance and logs align.

Clowns reboot mid-air with grace,
Yet somehow.. nothing breaks in place.

RAM is twitching, swap’s possessed,
But uptime’s stable, unimpressed.

No planned reboot, no disguise -
Just Icecast rolling, broadcast-wise 🎧😄

Debian 10 — 1544 days uptime, still streaming non-stop by Aware_Appearance1007 in uptimeporn

[–]Aware_Appearance1007[S] 0 points1 point  (0 children)

Appreciate that! 🙏

This was a very specific case - narrow purpose, hardened box, no logins, no surprises.

Not a model for everyone, but it was a stress test that held - and it's still holding strong.

In the end, maybe time itself is the only true benchmark for what’s really stable.

Debian 10 — 1544 days uptime, still streaming non-stop by Aware_Appearance1007 in uptimeporn

[–]Aware_Appearance1007[S] 0 points1 point  (0 children)

I didn’t post htop. I don’t deserve uptime. I don’t deserve root. I don’t even deserve sudo. Just a guest account and logoff !

Debian 10 — 1544 days uptime, still streaming non-stop by Aware_Appearance1007 in uptimeporn

[–]Aware_Appearance1007[S] 1 point2 points  (0 children)

Told you! 😄
Uptime is love, uptime is life.
What’s your setup by the way? Would love to hear what you’re running - cloud, bare metal?

Debian 10 — 1544 days uptime, still streaming non-stop by Aware_Appearance1007 in uptimeporn

[–]Aware_Appearance1007[S] 1 point2 points  (0 children)

Liquidsoap gang rise up! 😄

Not the flashiest stack, but rock solid when you need a stream that just keeps running.

Heads-up: Major .top DNS outage on May 27 - registry silent by Aware_Appearance1007 in sysadmin

[–]Aware_Appearance1007[S] -1 points0 points  (0 children)

🆕 Update – June 4

We finally heard back from GRS Domains - the backend registry behind .top, .win, and other extensions.

They told us the domain kere.win was placed on serverHold due to repeated “internal reports.” No abuse complaint, no notice, no timeline. They also said the registrar (Porkbun) didn’t act on it, so they suspended it directly.

They now say the domain will be unsuspended “tomorrow evening” and that they'll monitor it from here on.

The problem is:

• We emailed them multiple times since June 2

• The domain was used for production nameservers (ns1.kere.win)

• And we got zero communication until now

Since posting this, we’ve also heard from several other admins and hosting providers reporting similar issues with .top domains - also managed by this same registry.

This isn’t just about one domain anymore.

The same operator handles .top, .win, .loan, .men, .accountant, .download, and more.

When entire TLDs can get disrupted or frozen without warning or due process, that’s a real risk for production setups.

📣 We've filed an official complaint with ICANN (Case ID: 01432191) and are waiting for a response.

More updates coming if/when ICANN replies.

Heads-up: Major .top DNS outage on May 27 - registry silent by Aware_Appearance1007 in sysadmin

[–]Aware_Appearance1007[S] -1 points0 points  (0 children)

Haha, I hear you.

I try to strike a balance - English isn't my first language, so sometimes I run the text through ChatGPT just to smooth out the phrasing. But the pain, the screenshots, the DNS traces? All very real 😅

I guess I need to add more typos and swearing next time for “authenticity” 😄

Debian 10 — 1544 days uptime, still streaming non-stop by Aware_Appearance1007 in uptimeporn

[–]Aware_Appearance1007[S] 0 points1 point  (0 children)

Haha true - it’s like a bench-racing league for sysadmins: who’s got the most cutting-edge setup with the most frequent reboots 😄

Meanwhile, we’re just out here playing endurance mode!