Posts by Da Flex

    Thanks but it had nothing to do with the dns service, i use a vpn which i disable when i am testing new builds.

    Hmm, I'm still reading VPN messages in your latest log:

    Code
    2025-12-20 09:35:08.570 T:1572    error <general>: VPN Mgr : (service.py) VPN monitor service detected VPN connection  is not running when it should be
    ...
    2025-12-20 09:35:12.416 T:1572     info <general>: VPN Mgr : (service.py) VPN connected to de-fra.prod.surfshark.comsurfshark_openvpn_udp
    ...
    2025-12-20 09:43:16.922 T:1572    debug <CAddonSettings[[email protected]]>: trying to load setting definitions from old format...

    I would uninstall all VPN-related stuff to test Waipu, just to get clean logs. chewitt knows more about VPN...

    The developer of the Waipu add-on is your target person, but most add-on devs are at Kodi forum. They aren't here.

    Try a different DNS service:

    Code
    2025-12-20 09:35:06.904 T:1581    error <general>: CCurlFile::CReadState::FillBuffer - (0x7f176c003fc0) Failed: Could not resolve hostname(6)
    2025-12-20 09:35:06.904 T:1581    error <general>: CCurlFile::Open - <https://auth.waipu.tv/oauth/token> Failed with code 0:
                                                       
    2025-12-20 09:35:06.904 T:1581    error <pvr.waipu>: [Http-GET-Request] error. status: -1, body: 
    2025-12-20 09:35:06.904 T:1581    error <pvr.waipu>: [OAuthRequest] no network connection
    2025-12-20 09:35:07.104 T:1581    error <general>: CCurlFile::CReadState::FillBuffer - (0x18002600) Failed: Could not resolve hostname(6)
    2025-12-20 09:35:07.104 T:1581    error <general>: CCurlFile::Open - <https://auth.waipu.tv/oauth/token> Failed with code 0:
                                                       
    2025-12-20 09:35:07.104 T:1581    error <pvr.waipu>: [Http-GET-Request] error. status: -1, body: 
    2025-12-20 09:35:07.104 T:1581    error <pvr.waipu>: [OAuthRequest] no network connection

    Which log files i need to paste? Got couple of them.

    Debug log.

    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. Generate a log URL (do not post/upload logs to the forum)

    use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

    daniel712 If you need a cheap Netflix box, get an Amazon device (Fire TV, Cube etc.). Netflix isn't well-supported on Kodi (limited resolution). Amazon delivers updates for many years.

    The Nvidia Shield is pretty much the king of all set-top boxes. If affordable, get it.

    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. Generate a log URL (do not post/upload logs to the forum)

    use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

    JonnyGators I understand your wishes, but you're asking for a professional solution. LE is made by hobbyists for many different devices. Even if users would be able to answer all setup questions, a bad HDMI cable, or a wrongly selected HDMI port on TV can still destroy the setup.

    It's like on all Linux systems: LE is powerful and extremely configurable, but the perfect GUI setup is a truckload of work.

    OK, I've concluded - I think - my problem isn't just with tvheadend-related add-ons. As far as I have noticed, I simply can't install add-ons from the LE repository. I get the aforementioned "couldn't connect to server(7)". I can't say I understand how this all works, but I've noticed that the URL for the files to be downloaded starts with "https://addons.libreelec.tv". If I understand, the portion addons.libreelec.tv needs to resolve to a valid IP addr., which according to the DNS server I'm using, it does not. This would explain why LE can't connect. Is this close to correct? I don't exactly understand why I'm apparently the only one who has run across this issue.

    You're not the only one:

    Seems like a DNS problem, because it works for other users.

    Please test those commands on SSH:

    Code
    nslookup addons.libreelec.tv
    wget https://addons.libreelec.tv/12.2.0/ARMv7/arm/addons.xml.gz

    I can access the Kodi add-on repository, but not the LibreELEC add-ons repo ("could not connect to repository" - timeout?) Happened on both builds.

    Also reported by another user. Could be a problem with our LE repo:

    zeke2135
    March 10, 2026 at 6:50 PM

    2 - What is your opinion on this TechnoTrend Connect S2-3650 CI satellite card?

    I think the card will work with your TechnoTrend receiver, but you need a different CAM.

    A CAM is an own little computer with its own little menu. So it's possible that the CAM can read some data (keys, card number, IKE?) from the inserted card. However, that still doesn't mean that CAM and card work together, so you could watch TV.

    You have to find the right CAM for your card. Normally CAM and card work together without any setup or menu diving. Ask the people, who gave you the card, which CAM you should use with it. Here in Germany it's possible to buy or rent a CAM. Maybe you also have those options in Yemen.

    Thats the log I've been able to retrieve from Kodi. Any Idea?

    https://paste.libreelec.tv/tight-anteater.log

    Thanks. The error is visible in the log. It could be an LE 13 bug.

    Code
    2026-03-09 17:49:16.170 T:1313    debug <samba>: int XFILE::CSMBDirectory::OpenDir(const CURL&, std::string&): Using authentication url smb://USERNAME:[email protected]/
    2026-03-09 17:49:16.170 T:1313    debug <general>: smb: parsed path: fname='smb://USERNAME:[email protected]' server='192.168.1.2' share='' path='' options=''
    2026-03-09 17:49:16.170 T:1313    debug <general>: smb: SMBC_check_options(): server='192.168.1.2' share='' path='' options=''
    2026-03-09 17:49:16.170 T:1313    debug <general>: smb: SMBC_server: server_n=[192.168.1.2] server=[192.168.1.2]
    2026-03-09 17:49:16.170 T:1313    debug <general>: smb:  -> server_n=[192.168.1.2] server=[192.168.1.2]
    2026-03-09 17:49:16.170 T:1313    debug <general>: smb: Connecting to 192.168.1.2 at port 139
    2026-03-09 17:49:16.636 T:1313    debug <general>: smb: socket options: SO_KEEPALIVE=0, SO_REUSEADDR=0, SO_BROADCAST=0, TCP_NODELAY=1, TCP_KEEPCNT=9, TCP_KEEPIDLE=7200, TCP_KEEPINTVL=75, IPTOS_LOWDELAY=0, IPTOS_THROUGHPUT=0, SO_REUSEPORT=0, SO_SNDBUF=87040, SO_RCVBUF=131072, SO_SNDLOWAT=1, SO_RCVLOWAT=1, SO_SNDTIMEO=0, SO_RCVTIMEO=0, TCP_QUICKACK=1, TCP_DEFER_ACCEPT=0, TCP_USER_TIMEOUT=0
    2026-03-09 17:49:16.636 T:1313    debug <general>: smb: cli_set_timeout: Changing connection timeout for server '192.168.1.2' from 20000 (ms) to 30000 (ms).
    2026-03-09 17:49:16.638 T:1313    error <general>: int XFILE::CSMBDirectory::OpenDir(const CURL&, std::string&): Unable to open directory : 'smb://USERNAME:[email protected]/'
                                                       unix_err:'16' error : 'Invalid argument'