Error #01: illegal base64 data at input byte 15 when certain clients try to download EPG

[dancorrigan1]

IPTV Smarters Pro for PC and occasionally for iPhone will error when trying to download the EPG and some other services on a certain iptv service.

Tivi Mate on Firestick errors sometimes also.
Tivi Mate on nVidia Shield does not error.

[GIN] 2023/10/24 - 11:24:26 | 200 | 202.987777ms | 192.168.1.111| GET "/player_api.php?username=dan3&password=dan3&action=get_short_epg&stream_id=41312"
Error #1: illegal base64 data at input byte 15

[xxn4]

Hi, I've got the same problem and want to add some further information, maybe it will help to fix the problem, because missing epg is annoying. :(

I don't think that the problem is depending on the client. Perhaps the Tivimate on the nvidia shield is accessing directly or using the m3u? The issue can be reproduces with every client including postman. Tivimate on the shield will not use any other url.

The number of the byte (in your example 15) is not static. It depends on the JSON that should be served as answer. In the JSON the "title" and "description" are base64 encoded. I think the shown byte depends on the position of the first "title" or "description".

When the error occurs, the iptv-proxy itself does not log anything. If there are no EPG data for the channel, no error occurs.
OK, two lines:

[GIN] 2023/11/06 - 15:20:10 | 200 | 804.609135ms | x.x.x.x | GET "/player_api.php?username=xxx&password=xxx&action=get_short_epg&stream_id=xxx"
2023/11/06 - 15:20:10 [iptv-proxy] 2023/11/06 - 15:20:10 | x.x.x.x |Action get_short_epg

Error, 1 line plus error:

[GIN] 2023/11/06 - 15:19:10 | 200 | 594.306336ms | x.x.x.x | GET "/player_api.php?username=xxx&password=xxx&action=get_short_epg&stream_id=xxx"
Error #01: illegal base64 data at input byte 203

I found hints that the cause could be the difference of functions base64.RawStdEncoding and base64.StdEncoding where the "raw"-Version should be used if no padding is added. But unfortunately I'm not a developer so I don't know how I can investigate this further.

[xxn4]

Just looked at the older issues and this has been reported already in #115

So this duplicate could be closed.