Posts by Lululla

  • Vavoo Proxy Stream Live - New discussion & support

    Quote from Panda555

    DNS box and DNS out must be the same ( 1.1.1.1 ). Check again your network settings in image. If you use , untick IPv6 .


    What is this DNS box address ?


    [2026-05-09 13:29:18] [INFO] [VUTILS] ===== Vavoo session start =====
    [2026-05-09 13:29:18] [INFO] [VUTILS] Vavoo Version: 1.71
    [2026-05-09 13:29:18] [INFO] [VUTILS] DNS box: fdc3:5b9f:fe5:0:9a9b:cbff:fe13:a361
    [2026-05-09 13:29:18] [INFO] [VUTILS] DNS out: 1.1.1.1

    [2026-05-09 13:29:18] [INFO] [VUTILS] [INFO] Initial aspect ratio: 2
    [2026-05-09 13:29:18] [INFO] [PROXY] Python 3 detected
    [2026-05-09 13:29:18] [INFO] [PROXY] Token monitor started


    Increase timeout ..

    BEFORE

    The user is experiencing a problem with the Vavoo plugin. When a VPN connection is active, it hangs on "checking proxy..." and then restarts Enigma2. Analyzing the logs he sent, it appears that the local proxy (http://127.0.0.1:4323) isn't responding immediately because it's still loading the channel catalog (over 9,500 channels), and the VPN is further slowing down requests to the Vavoo servers (vavoo.to, lokke.app).


    After 60 seconds, the plugin's watchdog thinks the proxy is dead and attempts to restart, but the proxy is actually still working. This causes conflicts, and Enigma2 eventually crashes or restarts.


    NOW

    Please read carefully what I wrote in the release release; you should use the plugin menu and increase the timeout.

    In the log, the user set proxy_startup_timeout to 30 seconds (it says "waiting up to 30 seconds..."), but loading the catalog takes longer than 60 seconds. Therefore, the value should be increased to 120 seconds or more.



    The problem you're experiencing—the plugin gets stuck on "checking proxy..." and then restarts Enigma2—is because the VPN connection significantly slows down the HTTP requests the internal proxy (http://127.0.0.1:4323) must make to the Vavoo servers (vavoo.to, lokke.app) to download the channel catalog (over 9,500 channels). The proxy needs more time to complete this operation, but the plugin's internal timers (watchdog, waiting for response) start running first and assume the proxy is dead, attempting a restart that ultimately crashes Enigma2.


    What has already been improved in version 1.71

    A configurable Proxy startup timeout (seconds) option has been added (default 30, max 120) that controls how long the plugin waits for the proxy to become operational before declaring failure.


    The watchdog (which checks every 60 seconds to see if the proxy is alive) now also checks for the presence of the /tmp/vavoo_proxy_booting file and doesn't attempt a restart if the proxy is still booting.


    Why isn't it still working for you?

    Analyzing your log, I see that:

    The proxy starts at 1:30:50 PM and begins loading the catalog (fetching page 1...).

    After 60 seconds (1:31:50 PM), the main plugin still loads the country list from the original source (fallback), and the watchdog fires (1:31:51 PM) because the proxy is still not responding.

    The proxy had just finished the first page (1:31:51 PM), but obviously it's not ready yet.

    A restart is attempted, but the proxy responds "Another proxy is booting," and the situation gets complicated.


    The critical point: loading the full catalog takes more than 60 seconds (perhaps even 2-3 minutes) on your VPN connection.

    The watchdog goes off too early.


    EXCEPT...
    don't use vpn ..

    try and feedback.. but i don't have solution for your problem
    -I don't have line iptv
    -i don't have vpn
    -i don't have nothing, I can only use the little time I have left to read you

  • [Plugin] Vavoo Stream Live.

    Release v1.71

    in this release

    • v.1.71 (9800bef)
    • Update translations via workflow (730a2c4)
    • Apply auto PEP8 aggressive fixes (318b968)
    • Proxy startup timeout (seconds)
    • Increase if proxy takes long due to VPN or slow connection.

  • Vavoo Proxy Stream Live - New discussion & support

    Install the new version 1.71 of the plugin with these changes.

    Go to the Vavoo configuration menu and increase the Proxy startup timeout (e.g., to 60 or 90 seconds).

    Restart Enigma2 or reopen the plugin.


    • Proxy startup timeout (seconds)
    • Increase if proxy takes long due to VPN or slow connection.

  • Vavoo Proxy Stream Live - New discussion & support

    Please.. read this post and try suggestions first of other reply ;)


    Post
    RE: Vavoo Proxy Stream Live - New discussion & support
    ---->>>>>>>>>>>>> START PROXY<<<<<<<<<----------
    • Menu config
    • On proxy
    • Save
    • Reopen plugin.
    This System it’s good for enigma2 thread.
    Box now it’s very speed if proxy off.
    Lululla




    Post
    RE: Vavoo Proxy Stream Live - New discussion & support
    To avoid confusion and lengthy searches, let's start here ;)

    Last version it's on Linuxsatpanel..

    README HELPERS..
    vavoo/README.md at main · OwnerPlugins/vavoo


    Before you write...
    Check these steps:


    1. Verify that the proxy is running:
    2. from Telnet (open telnet with putty or other software.. and digits this code and put output here
      (Code, 3 lines)

    3. and put output here
    ------------------------
    1. Open browser on pc and digit
    2. IP_BOX:4323/status
    3. if show status is json fotmar type:
      {"initialized": true,
    …
    Lululla

  • Vavoo Proxy Stream Live - New discussion & support

    i s wrong..


    this it's ok


    Code
    wget -qO- http://127.0.0.1:4323/status

{"initialized": true, "channels_count": 9568, "addon_sig_valid": true, "addon_sig_age": 45, "local_ip": "127.0.0.1", "port": 4323}



    Code
     wget -qO- http://127.0.0.1:4323/countries
["Albania", "Arabia", "Balkans", "Bulgaria", "Croatia", "France", "France Sport", "Germany", "Italy", "Netherlands", "Poland", "Portugal", "Romania", "Russia", "Spain", "Turkey", "United Kingdom"]


    Code
    wget -qO- http://127.0.0.1:4323/refresh_token
{"status": "success", "message": "Token refreshed"}



    ALL COMMANDS

  • OpenSkin Designer (OSD)

    New test today v.4.2.3.0


    FeatureStatusLocation
    selectionZoom for listbox✅ DonesGraphicListbox.cs – selected item zoom
    New eSlider widget✅ DonesAttributeSlider.cs + sGraphicSlider.cs + integration in sAttributeWidget and sGraphicWidget
    scrollbarBackgroundGradient✅ DonesAttributeListbox.cs (property) + rendering in sGraphicListbox
    Gradients for any widget✅ DoneBase sAttribute with BackgroundGradient, ForegroundGradient, helper
    Extended ClockToText✅ Donestrftime.ToString + ClockToText.getText with %l, %I, %e, %p, %P, lowerAmpm
    Extended ServiceName✅ DoneAdded ChannelNumber, ChannelNumberAndName, PiconName, ReferenceName



    Example:


    On github

    "- Added 2560x1440 and 3840x2160 options in fResolution (selection available, automatic scaling not implemented)"


    "- **Known Limitations"

    "- Resolution changes in `fResolution` correctly update the `output` attribute in the `skin.xml` file,"

    "- but they do not automatically resize coordinates, dimensions, and fonts of the elements."

    "- To convert an existing skin from one resolution to another, it is recommended to use the external tool **Enigma2 Skin Converter** (by @KiddaC)."

  • OpenSkin Designer (OSD)

    Quote from Lululla

    I compared the 2 readme.. and there are some things that can be updated in both projects to unify them if you want


    Features (from the README)


    In the meantime that oldem2014 finishes all the new features, let's see how this test behaves?



    removed all old error on root structure.


    Release v4.2.1.0 MOD by Lululla · OwnerPlugins/OpenSkin-Designer


    and added

    Release v4.2.2.0 MOD by Lululla · OwnerPlugins/OpenSkin-Designer


    preview4.jpg?raw=true

  • OpenSkin Designer (OSD)

    I compared the 2 readme.. and there are some things that can be updated in both projects to unify them if you want


    Features (from the README)