[Bug]: Playback stops at 49 seconds #3336

Open
opened 2025-05-09 02:17:57 +00:00 by deathblade666 · 9 comments
deathblade666 commented 2025-05-09 02:17:57 +00:00 (Migrated from github.com)

Preflight Checklist

  • I use the latest version of YouTube Music (Application).
  • I have searched the issue tracker for a bug report that matches the one I want to file, without success.
  • I understand that th-ch/youtube-music has NO affiliation with Google or YouTube

YouTube Music (Application) Version

3.9.0

Checklists

What operating system are you using?

Other Linux

Operating System Version

Fedora 42

What CPU architecture are you using?

x64

Last Known Working YouTube Music (Application) version

No response

Reproduction steps

  1. open app
  2. select song
  3. let play till it stops at 49 seconds

Expected Behavior

to play full song

Actual Behavior

stops at 49 seconds

Enabled plugins

default

Additional Information

tested with latest appimage

### Preflight Checklist - [x] I use the latest version of YouTube Music (Application). - [x] I have searched the [issue tracker](https://github.com/th-ch/youtube-music/issues) for a bug report that matches the one I want to file, without success. - [x] I understand that **th-ch/youtube-music has NO affiliation with Google or YouTube** ### YouTube Music (Application) Version 3.9.0 ### Checklists - [ ] I use the portable version of the YouTube Music Application. - [ ] I can reproduce this issue in the [official version of (WEB) YTM](https://music.youtube.com). ### What operating system are you using? Other Linux ### Operating System Version Fedora 42 ### What CPU architecture are you using? x64 ### Last Known Working YouTube Music (Application) version _No response_ ### Reproduction steps 1. open app 2. select song 3. let play till it stops at 49 seconds ### Expected Behavior to play full song ### Actual Behavior stops at 49 seconds ### Enabled plugins default ### Additional Information tested with latest appimage
JellyBrick commented 2025-05-10 13:39:50 +00:00 (Migrated from github.com)

Could you disable the adblocker plugin and try again?

Could you disable the adblocker plugin and try again?
deathblade666 commented 2025-05-11 00:27:30 +00:00 (Migrated from github.com)

Could you disable the adblocker plugin and try again?

same thing, i did notice while testing (this is with and without adblock) that while most of the time its stuck at 49 seconds, sometimes it'll load up to 1minute, but overall it hasn't loaded a full song yet. the ads load fine without adblocker.

Not sure if it matters or not but I havent been logged in.

Update: just testing using an alternate network, seems to work there. Though tested the official site on my home network and it works fine so not sure what might be the difference here.

> Could you disable the adblocker plugin and try again? same thing, i did notice while testing (this is with and without adblock) that while most of the time its stuck at 49 seconds, sometimes it'll load up to 1minute, but overall it hasn't loaded a full song yet. the ads load fine without adblocker. Not sure if it matters or not but I havent been logged in. Update: just testing using an alternate network, seems to work there. Though tested the official site on my home network and it works fine so not sure what might be the difference here.
thisislocospeaking commented 2025-06-14 10:40:26 +00:00 (Migrated from github.com)

I first thought it was my DNS server doing this but I changed the AdBlock plugin from "In Player" to "with blocklist" and now it plays the full songs. Haven't encountered any ads yet but this seems to have fixed the problem.

I first thought it was my DNS server doing this but I changed the AdBlock plugin from "In Player" to "with blocklist" and now it plays the full songs. Haven't encountered any ads yet but this seems to have fixed the problem.
Owner

Why would a DNS server by at fault in the first place?

Why would a DNS server by at fault in the first place?
thisislocospeaking commented 2025-06-14 12:56:40 +00:00 (Migrated from github.com)

Why would a DNS server by at fault in the first place?

I run AdGuard Home on my network, it's not uncommon for large blocklists like the one I use to block a whole ton of services, including YouTube videos and other stuff

> Why would a DNS server by at fault in the first place? I run AdGuard Home on my network, it's not uncommon for large blocklists like the one I use to block a whole ton of services, including YouTube videos and other stuff
Owner

Do you understand how the DNS protocol works?

Do you understand how the DNS protocol works?
thisislocospeaking commented 2025-06-14 13:29:37 +00:00 (Migrated from github.com)

Do you understand how the DNS protocol works?

Do you know how DNS filtering works? AdGuard does that. It can filter or entirely block DNS queries. If you've ever used something like AdGuard Home or PiHole you'd know that it can break a ton of services by blocking their DNS queries. You don't have to talk down on me for this, it's out of topic anyways.

> Do you understand how the DNS protocol works? Do you know how DNS filtering works? AdGuard does that. It can filter or entirely block DNS queries. If you've ever used something like AdGuard Home or PiHole you'd know that it can break a ton of services by blocking their DNS queries. You don't have to talk down on me for this, it's out of topic anyways.
Owner

I have written a DNS server from scratch, and I have been an Adguard user for many years.
If a DNS is going to block a domain, it will do so at the start.

It can't block a domain after it has loaded.
That's just how DNS works, your browser says "hey, what is the IPv4 address for music.youtube.com" and the DNS replies with "music.youtube.com is a CNAME for youtube-ui.l.google.com, and an IPv4 for youtube-ui.l.google.com is 172.217.169.174".

After that, your browser directly communicates with the IP given, it can't communicate with the domain name.

Edit: One way for this to not work, is when the browser doesn't remember what IP a domain resolves to.
If your browser makes the DNS request every time you make a request to a domain, then it could make sense for Adguard to have the ability of blocking a domain even after it has already loaded.
But why would Adguard consistently block the domain not the first time you load it, but after 49 seconds of playing a song?

I have written a DNS server from scratch, and I have been an Adguard user for many years. If a DNS is going to block a domain, it will do so at the start. It can't block a domain after it has loaded. That's just how DNS works, your browser says "hey, what is the IPv4 address for music.youtube.com" and the DNS replies with "music.youtube.com is a CNAME for youtube-ui.l.google.com, and an IPv4 for youtube-ui.l.google.com is 172.217.169.174". After that, your browser directly communicates with the IP given, it can't communicate with the domain name. Edit: One way for this to not work, is when the browser doesn't remember what IP a domain resolves to. If your browser makes the DNS request every time you make a request to a domain, then it could make sense for Adguard to have the ability of blocking a domain even after it has already loaded. But why would Adguard consistently block the domain not the first time you load it, but after 49 seconds of playing a song?
thisislocospeaking commented 2025-06-15 03:32:17 +00:00 (Migrated from github.com)

But why would Adguard consistently block the domain not the first time you load it, but after 49 seconds of playing a song?

I don't know, hence why I tried disabling it to check if it does work afterwards. It didn't appear to fix the problem so I tried different troubleshooting steps.

And to add to my original comment where switching the adblock from "in player" to "with blocklists" fixed the issue, it didn't, worked for some time and then stopped again, it is incredibly inconsistent

> But why would Adguard consistently block the domain not the first time you load it, but after 49 seconds of playing a song? I don't know, hence why I tried disabling it to check if it does work afterwards. It didn't appear to fix the problem so I tried different troubleshooting steps. And to add to my original comment where switching the adblock from "in player" to "with blocklists" fixed the issue, it didn't, worked for some time and then stopped again, it is incredibly inconsistent
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: YTMD/youtube-music#3336
No description provided.