Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by binhex

  1. On 7/10/2022 at 7:58 PM, bwnautilus said:

    After upgrading to 6.10.3 I'm getting this popup error (see attached pic).  The Intellij window starts fine but if I close it I cannot open it again.  I have to restart the docker.  Is there a workaround for this or do I have to wait for the next docker update?  FYI this happens with the Pycharm docker also.  Thanks. 

    2022-07-10 14_55_41-IntelliJ - noVNC.png

    possibly related:-



    • Thanks 1
  2. 1 hour ago, Rweng009 said:

    Plex working fine this morning - Just updated to the latest version and now dont have a media server.

    Plex opens - the library list is there but no content (apart from Plex online stuff)


    "Something went wrong

    An unexpected error occurred"


    Had the same error when updating my Synology last week to 1.28 which never got resolved - now both it and my unraid plex dont work.

    Any ideas??


     Server logs attached.

    Plex Media Server 3.33 MB · 0 downloads

    from your logs:-


    Aug 03, 2022 15:34:25.816 [0x14bb95686380] INFO - Analyzing database.
    Aug 03, 2022 15:34:26.860 [0x14bb95686380] ERROR - SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
    Aug 03, 2022 15:34:26.860 [0x14bb95686380] ERROR - SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
    Aug 03, 2022 15:34:26.860 [0x14bb95686380] ERROR - SQLITE3:0x80000001, 11, statement aborts at 3072: [ANALYZE] database disk image is malformed
    Aug 03, 2022 15:34:26.864 [0x14bb95686380] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: database disk image is malformed

    see q5:-

  3. On 7/8/2022 at 10:05 AM, SliMat said:

    Hi all,


    I have been using Binhex-PrivoxyVPN for a number of years using privateinternetaccess... with no issues :)


    However a few weeks ago I noticed some dockers were failing (Sonarr/Radarr, etc). When I looked into it, Binhex-PrivoxyVPN was showing as stopped... so I tried restarting and it starts then immediately stops again. I have checked my PIA credentials and they all seem correct (working in built in Windows VPN client), but I just cant get the docker to start. I have even deleted the whole docker + image and done a fresh install... the only way I can get the docker to start is by setting VPN_ENABLED to "no".


    I could have sworn there was a SpaceInvaderOne tut on setting this up - but for the life of me cant find it :(


    Can anyone help, or point me in the direction of an idiots guide?


    Thanks in advance

    lets start with some logs, do this:-

  4. 4 minutes ago, wgstarks said:

    He didn’t create an env var. He created a port for WEBUI_PORT.

    indeed!, i spotted that in the screenshot:-

    7 minutes ago, binhex said:

    from your screenshot it looks like you defined the 'Name' of the port incorrectly, its not 'WEBUI PORT' its 'WEBUI_PORT' and the type is wrong, its a variable NOT a port.


  5. 32 minutes ago, ArxKnight said:

    I though I had done the correct method by deleting the default "WEBUI" port and making it again to set the host and container ports both to 8088?

    from your screenshot it looks like you defined the 'Name' of the port incorrectly, its not 'WEBUI PORT' its 'WEBUI_PORT' and the type is wrong, its a variable NOT a port.


    @Squid you are quite right, the user should not be redefining the container port - however qbittorrent is an exception to the case here, here are my notes from the qbittorrent (geared more towards non unraid users, but you get the gist):-



    Due to issues with CSRF and port mapping, should you require to alter the port for the webui you need to change both sides of the -p 8080 switch AND set the WEBUI_PORT variable to the new port.

    For example, to set the port to 8090 you need to set -p 8090:8090 and -e WEBUI_PORT=8090

    so for unraid users that means setting WEBUI_PORT to the port you want and then re-creating the port to match (host and container side being the same).


    i then have some code to pick up the env var WEBUI_PORT to set the port for the running application (qbittorrent in this case).

    • Like 1
  6. 20 hours ago, NLS said:

    EDIT: Actually the problem is the session.lock file remaining. Needs manual delete. Probably the stop (or restart) container process, should look for this file to delete after some timeout?

    should be simple enough to fix, delete file on startup of the container, where is the lock file located?


    found it and the fix is in, please pull down the latest image.

    • Like 1
  7. 11 hours ago, storagehound said:

    My setup.  I have DelugeVPN setup with several containers connected to it by adding "--net=container:binhex-delugevpn" to extra parameters.  I setup ADDITIONAL_PORTS for the containers.  To allow the containers that needed to communicate with each other I  added those container port numbers to VPN_OUTPUT_PORTS for DelugeVPN.

    so containers talking to each other in the SAME network can be done via localhost and the port the application uses, you should not be defining ports in VPN_OUTPUT_PORTS unless you want an application using the VPN network to communicate OUTSIDE of the VPN network to another application.

    see A24 note 1 for details about localhost:-

    see A27 for details about correct usage of VPN_OUTPUT_PORTS


    11 hours ago, storagehound said:

    If I create a custom network and add DelugeVPN

    you should be able to use a custom network - at least it did work in testing a long time ago!, what you cannot use is specific ip addresses for the vpn container, that will not work.

    p.s. i do not like the usage of VPN_OUTPUT_PORTS or VPN_INPUT_PORTS actually, its a little confusing for the average user, however its a necessary evil (havent found a better way) to guarantee zero ip leakage which of course is the most important thing, so for now thats how it is.

    • Thanks 1
  8. Still the same issue for me (using
    I turned on debug logging in Emby in hopes it might make it easier for troubleshooting and ran screen grabber on the same file twice.

    I left the full log just in case there's anything related to ffmpeg versions or dependencies. The screen grabber itself is at the bottom.
    Thanks for looking into this, binhex
    I think this might be a question for emby support, the docker image is using emby version of ffmpeg as far as I can tell so there isn't a lot I can change on my end, maybe it's a known bug in 4.7.x

    Sent from my CLT-L09 using Tapatalk

  9. Hi, Ive been having an issue where none of my preferences save and even if i try manually editing the file, Notepad++ on windows says its unable to open the file and if i nano it from Unraid Terminal, it will get reset when i start the container again. It is also downloading all torrents to the docker.img file and not to the specified download folder. any advice?
    Stop the container, then edit the config file, then start and verify settings are correct.

    Sent from my CLT-L09 using Tapatalk

  10. On 7/21/2022 at 7:02 AM, PeterZ said:


    I have the same problem.

    The error occurs when process runs the 'ImageExtraction'.

    My Emby version is 4.7.5 and Unraid version is 4.10.3.

    i have updated the image to now use emby supplied ffmpeg, can you pull down the latest image and let me know if it improves things.

  11. 6 hours ago, TrondHjertager said:

    Looks like changing the network type from bridge mode to host mode did the trick. Not sure why. All three containers were set to use bridge mode, but changing radarr to host mode solved the problem.

    that should not be necessary, bridge should work ok, was radarr set to use a custom bridge?. 

  12. ok new special snapshot tagged version has been made available, this has the netty fix included (snapshot 22w24a), please do the following to use it:-


    1. unraid webui/docker

    2. left click edit minecraft container

    3. edit 'repository' and append :snapshot-22w24a to the repository name

    4. click apply to pull down tagged version


    once 1.19.1 has been released then simply reverse the above to get back to latest.

    • Thanks 1
    • Upvote 1
  13. 10 hours ago, slofiend said:

    I've also gone in through FileZilla and manually deleted the whole binhex-plexpass folder from my appdata

    that will definitely do it, the only place configuration for plex is stored is in /config, the only other persistent data is configuration of the container, this is stored on your usb key and can be completely removed by going to docker/add container/ then 'select a template' dropdown and select under [user templates] your plex template then to the left of the name is a 'x' click it to delete the template, then reinstall from CA.

  14. 14 minutes ago, NotNeo said:

    sorry if this is a Noob question or has been asked before but how do i route all Jellyfin traffic through your wonderful DelugeVPN ?


    i tried changing the network type to none and setting extra arguments to "--net=container:binhex-delugevpn" but it just block the webUI even when i adding port 8096 & 8920 in the delugeVPN docker.




  15. 14 hours ago, jfine said:

    Does anyone know how to contact the author? I submitted a little while ago and if I'm understanding things I think it'll only require rebuilding the image to resolve the 1.19 netty issue.

    hi guys, sorry for the delay in responding, my life is mental right now!. ok so i can update to the snapshot, however i am concerned this may cause issues with the minecraft client being out of sync with the server version, i guess the safest option is to create a specific tagged version, leave it with me.

    • Like 1
  16. I had a similar issue to you. 
    My DelugeVPN docker stopped working (I use Mullvad as well). It wouldn't start at all. 
    I changed the STRICT_PORT_FORWARD to NO which fixed the problem. 
    Trust me that is definitely not the fix as that only takes effect when VPN provider is set to Pia which will not be the case for you

    Sent from my CLT-L09 using Tapatalk

  17. Interesting that your container settings have some entries that are different than mine.. for example, WEBUI_PORT doesn't exist for me, and VPN_INPUT_PORTS and VPN_OUTPUT_PORTS are combined into ADDITIONAL_PORTS.  You also don't have either DELUGE_DAEMON_LOG_LEVEL or DELUGE_WEB_LOG_LEVEL.  If you hit "v Show more settings" or "v Show docker allocations" near the bottom, are there more entries that appear?  Also, is the IP address showing in the bottom right of your Deluge window your endpoint IP or something different?
    Edit:  What are the container settings up above, like network type, etc.?
    It sounds like you have an out of date template keep in mind changes to the templates cannot be pushed out to users.

    Sent from my CLT-L09 using Tapatalk

  18. How can I move my previous (Official) Emby to Binhex Emby?
    I have the "Official" Emby docker and would like to clone/copy all my settings, libraries, etc to the Binhex docker is there a streamlined way to do this without having to manually go through every setting in the new setup?
    If you can work out which files contain settings and your library etc then you should be able to simply copy and paste from one configuration set to the other as it is the same application (emby)

    Sent from my CLT-L09 using Tapatalk

    • Upvote 1
  19. If that's the case why couldn't I access the container from in-network? even if it couldn't get out to download anything from the internet, I should still be able to communicate with it in-network, shouldn't I?!?
    To prevent IP leakage the application will not start until the VPN is fully established and confirmed working

    Sent from my CLT-L09 using Tapatalk