chillr

Members
 View Profile  See their activity

  • Posts

    6

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

chillr's Achievements

Noob

Noob (1/14)

1

Reputation

  1. chillr started following Server locked up twice since updating yesterday
  2. chillr started following Unraid 6.10, permission denied from docker containers , Immich docker self-hosted google photos setup , [PLUG-IN] NerdTools and 1 other
  3. chillr
    Request for Netcat & bc, thanks
  4. chillr
    Had a party Friday night and was disappointed that Roon couldn't go for more than a couple of hours before playback issues occurred. Restarting the docker fixed things as usual. Today I got a chance to have a look at things and noticed the roonserver docker was using 21GB of ram which lead me to this post that may be related: https://community.roonlabs.com/t/memory-leak-in-roon-see-staff-post/145321/88?page=5 FYI - on restarting the docker it consumes 1.4GB of ram and continues to creep up.
  5. chillr
    I noticed the same stuttering you describe a few times, the last was in the weekend. It was during a 96khz Qobuz track and at the time I put it down to an internet streaming related issue. Have never had an issue playing back music from my local library (44.1 - 192khz).
  6. chillr
    Thanks for looking into it. I checked & found my installed binhex/arch-privoxyvpn docker version was 7 months old for some reason - strange as I only installed it for the first time last week (on two different Unraid machines as well - both grabbed the old version) . binhex/arch-privoxyvpn latest sha256:62829fd90130a29e48320faacc9c0ffc249a0cc1e13a56a4699652f2e00e684e 818db7544137 7 months ago 685MB Anyway, forcing a check for updates in the Unraid Docker GUI page found the latest version which I installed and tested - works well as you describe.
  7. chillr
    FYI - temporary work around I'm using to get microsocks to run without requiring authentication is to edit the /home/nobody/microsocks.sh file from the container console and remove the following entries: -u "${SOCKS_USER}" -P "${SOCKS_PASS}" Then restart the container. Would probably need to be done each time the container is edited / updated.
  8. chillr
    Hi there, regarding socks5 without authentication - is this confirmed as still working? With the empty strings passed i get this in the container logs: 2021-11-15 16:20:27.768499 [info] ENABLE_SOCKS defined as 'yes' 2021-11-15 16:20:27.788122 [warn] SOCKS_USER not defined (via -e SOCKS_USER), defaulting to 'no' 2021-11-15 16:20:27.806554 [warn] SOCKS_PASS not defined (via -e SOCKS_PASS), defaulting to 'no' But then testing to the microsocks server with no credentials using curl i get an error: chillr@CH-R5:/mnt/c/Users/chillr$ curl --socks5 10.10.1.110:9118 www.google.com curl: (7) No authentication method was acceptable. (It is quite likely that the SOCKS5 server wanted a username/password, since none was supplied to the server on this connection.) However passing the container default microsocks credentials (admin/socks) in the same curl request works? chillr@CH-R5:/mnt/c/Users/chillr$ curl --socks5 admin:[email protected]:9118 www.google.com <!doctype html><html itemscope="" itemtype="http://schema.org/WebPage".....