M3U tuner: 403 Forbidden despite User-Agent and Referrer

[TeraMan 4]

Same problem with the new version 1.0.36

 

[alex553 3]

With the GSE IPTV application from your mobile everything works! The problem is with Emby.

[dius 4]

1 hour ago, sa2000 said:

@alex553 @dius@vdatanet M3U TV Tuner 1.0.36 has just been released. If you have got it, please restart the server to pick it up. if not, then restart the server to get it checked for and after it is downloaded as seen in the dashboard, please restart the server againn to complete the installation

 

@sk222FYI

Hi, I just updated to the new version and rebooted, and I also get the same error: HTTP Response Status [403] Forbidden

[sa2000 674]

I am continuing to work with user @rcutandain this forum topic to get diagnostics but would love to get from other users to see if there are similarities. Specifically from users for whom Emby was working ok with the m3u tv tuner plugin before 1.0.35.0 and is still not working with 1.0.36.0 after the install and server restart

What I need is wireshark or tcp dump capture of a 403 error plus the raw embyserver log file - sent privately by Private Message in the forum

And if you can also do exactly same stream test with other app where it works eg vlc and again capture the http packets with wireshark or tcpdump and include the zipped pcap file for this as well

Which of you has the problem now in 1.0.36.0 after server restart but did not have it before version 1.0.35.0 of the plugin?

 

Edited January 18, 2025 by sa2000

[alex553 3]

51 minutes ago, sa2000 said:

I am continuing to work with user @rcutandain this forum topic to get diagnostics but would love to get from other users to see if there are similarities. Specifically from users for whom Emby was working ok with the m3u tv tuner plugin before 1.0.35.0 and is still not working with 1.0.36.0 after the install and server restart

What I need is wireshark or tcp dump capture of a 403 error plus the raw embyserver log file - sent privately by Private Message in the forum

And if you can also do exactly same stream test with other app where it works eg vlc and again capture the http packets with wireshark or tcpdump and include the zipped pcap file for this as well

Which of you has the problem now in 1.0.36.0 after server restart but did not have it before version 1.0.35.0 of the plugin?

 

Can't you go back to version 34 settings? Everything was fine there!

It stopped working for me on 35 and 36 doesn't work either.... I've tried other apps like vlc, kodi, gse iptv on mobile, I've talked to my iptv provider and they say they haven't changed anything!

You just have to go back to version 34, it's easy or that's how I see it. I hope it can be fixed as soon as possible because I like emby for its stability. Everything always worked perfectly for me and now there are problems. My rule in computing is if something works, why touch it... hehehehe

 

I really appreciate all the work of the developers, but before releasing updates you have to be very sure that everything is correct for testing, since there are already beta versions. It is a shame not to be sure that something works in the stable versions before releasing them to the public and avoiding these problems.

Greetings.

Edited January 18, 2025 by alex553

[sa2000 674]

1 hour ago, alex553 said:

Can't you go back to version 34 settings? Everything was fine there!

It stopped working for me on 35 and 36 doesn't work either.... I've tried other apps like vlc, kodi, gse iptv on mobile, I've talked to my iptv provider and they say they haven't changed anything!

Need to understand the problem. There may be different issues here for different user configurations. Could you please help getting diagnostics so we understand the issue. I can make 1.0.34 available to you to try. Please tell me what the platform is for your Emby Server and could you provide me details about your m3u setup. The m3u TV Source setup page screenshot in Live TV Setup to see what parameters you have for User Agent and Referer and if on Windows or Mac OS to run wireshark or tcpdump if on linux and capture the http packets and make that available to me privately together with the emby server log from the logs folder.

And if you can do http capture also when jusing vlc - you can pass to me all this in a private message through the forum - zipping the pcap file and log. 

[alex553 3]

28 minutes ago, sa2000 said:

Es necesario comprender el problema. Puede haber diferentes problemas aquí para diferentes configuraciones de usuario. ¿Podrías ayudarme a obtener diagnósticos para que entendamos el problema? Puedo poner a tu disposición la versión 1.0.34 para que la pruebes. Por favor, dime cuál es la plataforma para tu servidor Emby y ¿podrías proporcionarme detalles sobre tu configuración m3u? Captura de pantalla de la página de configuración de la fuente de TV m3u en la configuración de TV en vivo para ver qué parámetros tienes para el agente de usuario y el referente y, si estás en Windows o Mac OS, para ejecutar Wireshark o tcpdump si Estás en Linux y captura los paquetes http y ponlos a mi disposición de forma privada junto con el registro del servidor Emby desde la carpeta de registros.

Y si puedes hacer captura http también cuando solo usas vlc, puedes pasarme todo esto en un mensaje privado a través del foro, comprimiendo el archivo pcap y el registro. 

Mi configuración es la siguiente siempre funciona bien así cargar la lista m3u y todo lo demás en blanco como se ve en la captura, no soy el único usuario con problemas somos varios, no voy a poner registros de mi red por temas de seguridad, uso Emby en un Intel nuc con Windows 10 desde hace unos 6 años todo genial hasta este momento claro, uso licencia de por vida.

En cualquier aplicacion para IPTV que cargo la lista m3u funciona correctamente , ustedes cambiaron algo de la versión 34 a las demás es fácil vuelvan a dejarlo como estaba antes es muy fácil de solucionar no entiendo por qué se está tardando tanto si es solo volver atras , ahora mismo Emby está roto para visualizar IPTV y está es una característica estrella de Emby precisamente.

Un saludo.

Edited January 19, 2025 by alex553

[alex553 3]

Quote

@Luke

Esto debe tener prioridad m3u tunner está roto! Y es una característica muy usada en Emby.

 

Un saludo.

Edited January 19, 2025 by alex553

[sa2000 674]

53 minutes ago, alex553 said:

Mi configuración es la siguiente siempre funciona bien así cargar la lista m3u y todo lo demás en blanco como se ve en la captura, no soy el único usuario con problemas somos varios,

Thanks

@dius@vdatanet@TeraMan Are you also using default settings for User Agent and Referer/Referrer ?

Edited January 19, 2025 by sa2000

[vdatanet 1617]

4 hours ago, sa2000 said:

Are you also using default settings for User Agent and Referer/Referrer ?

Yes

[dius 4]

5 hours ago, sa2000 said:

Thanks

@dius@vdatanet@TeraMan Are you also using default settings for User Agent and Referer/Referrer ?

Yes, and it also worked for me in version 34. In 35 and 36 it doesn't work for me, it gives me the forbidden error.

[vdatanet 1617]

I've noticed that this error only occurs when transcoding is required. Using the Apple TV app with the MPV player selected, playback works.

[dius 4]

Hi, I just installed version 1.0.38 and I restarted the server and I have the same problem. Can I install 1.0.34 to see if the problem is corrected?

[rcutanda 13]

M3UTuner 1.0.38 works for me!

I have tried it both in my real Ubuntu server and in a Windows Sandbox testing environment. Both works.

Great Job, Emby team!

[TeraMan 4]

 

Thank you for your effort and work.
The version 1.0.38 is working perfectly

 

[dius 4]

Yes!!!! version 38 works perfectly on my server. thanks for the speed

[sa2000 674]

Great - Thank you all for the feedback. And thanks you @rcutandafor sticking with me and providing the numerous sets of diagnostics

[sa2000 674]

1 hour ago, vdatanet said:

I've noticed that this error only occurs when transcoding is required. Using the Apple TV app with the MPV player selected, playback works.

Can you see if 1.0.38 resolves your errors. Thanks

[rcutanda 13]

1 hour ago, dius said:

Hi, I just installed version 1.0.38 and I restarted the server and I have the same problem. Can I install 1.0.34 to see if the problem is corrected?

Following sa2000 advice I have just made the following tests with and without the following User agent HTTP header:

VLC/3.0.21 LibVLC/3.0.21

1.0.31 with No headers → Does NOT work

1.0.31 with headers → DOES work

1.0.35 with No headers → Does NOT work

1.0.35 with headers → DOES work

1.0.38 with No headers → DOES work

1.0.38 with headers → DOES work

If you are still having problems 1.0.38, try this user agent HTTP header:

VLC/3.0.21 LibVLC/3.0.21

Edited January 19, 2025 by rcutanda

[sa2000 674]

Thanks. We have now changed the default User-Agent HTTP header - so the problems that affected users were two separate causes - one the User-Agent and the other related to the Referrer spelling change where some providers needed to see Referrer rather than Referer - we now send both.

[sa2000 674]

@alex553Please can you confirm if the update to 1.0.38 resolves your errors

Thanks

[dius 4]

5 minutes ago, rcutanda said:

Siguiendo los consejos de sa2000, acabo de realizar las siguientes pruebas con y sin el siguiente encabezado HTTP del agente de usuario:

VLC/3.0.21 LibVLC/3.0.21

1.0.31 sin encabezados → NO funciona

1.0.31 con encabezados → FUNCIONA

1.0.35 sin encabezados → NO funciona

1.0.35 con encabezados → FUNCIONA

1.0.38 sin encabezados → FUNCIONA

1.0.38 con encabezados → FUNCIONA

Si aún tiene problemas con 1.0.38, pruebe este encabezado HTTP del agente de usuario:

VLC/3.0.21 LibVLC/3.0.21

Thanks!! It works on my server now without changing anything. When I uninstalled and reinstalled 1.0.38 it worked correctly without changing anything on my server. Thanks again for fixing it quickly too.

[sa2000 674]

@sk222Please confirm the current state for your configuration with 1.0.38 in place and what still needs to be addressed

Thanks

[alex553 3]

1 hour ago, sa2000 said:

@alex553Please can you confirm if the update to 1.0.38 resolves your errors

Thanks

it works thanks to everyone! emby is the best for its community without a doubt, thanks to everyone!

[sk222 5]

@sa2000Not sure whether 1.0.36 should have also fixed the problem about the Referer header not being picked up by ffmpeg?

Because I'm still getting a "No compatible streams" error message, logs revealing that neither the "Referer" nor "Referrer" headers are mentioned in the ffmpeg command, despite the RequiredHttpHeaders being {"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0","Referer":"https://teveo.cu/","Referrer":"https://teveo.cu/"}

 

embyserver.txt ffmpeg-transcode-468a02e6-4173-43e4-8f88-2f320c1865a9_1.txt