HpNoTiQ

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by HpNoTiQ

  1. 15 minutes ago, tsmebro said:

    I have the same problem and tried the fixes suggested. My upload script deletes empty folders, mount script is set to run every 10 minutes and when it creates the folders again they have owner root. 

     

    Not very elegant but I just run a user script to change those permissions on the local folder daily. Set to a couple of hours after the upload script has done it's thing

    Indeed, I just figured cloudplow deleted my UHD and HD Folders (which are shared with my dockers  I think Unraid recreated them with root.)
    I've changed 

    "remove_empty_dir_depth": 2, by "remove_empty_dir_depth": 3, (adapted to your architecture if you read me later).

    It's now fully working!

    • Thanks 1
  2. On 9/18/2022 at 6:23 PM, Kaizac said:

    You ran safe docker perms when you didn't have your rclone mounts mounted?

    And I think the default script already runs umask so seems like you are doubling that flag now?

    I've done :

     

    1. Fix your mount script syntax. -> Updated to last version  + Delete --umask 000 (line 138).

    2. Disable your mount script schedule -> Done 

    3. Make sure all your containers are using 99/100 umask 022 -> Done but maybe a typo : is it 002 or 022? In script it is --umask 002 \

    4.reboot your server -> Done 

    5. upon restart, run the new permissions tool for all shares including cache -> Done to all disk/all shares

    6. Delete the transcode folder for plex if have not set it up as a user share/its on tmp -> Done

    7. run your mount script ->DOne 

    8.start your dockers -> DOne by script.

     

    image.thumb.png.c26756d87541e5c0246352760ff8cdd5.png

    After a period of time, my HD and UHD folder are switching from nobody to root. (not the parent one neither the children folders).

    image.thumb.png.8725f17b91f0d0a5083d810fad4ef866.png

     

     

    image.thumb.png.94537a20ac4290b4a628c4b8bb2e2983.png

     

    I have these docker accessing this folder :

    2 Sonarr(1080/4k) 2 Radarr (1080/4k) Cloudplow Plex.
    They are all running with -e 'PUID'='99' -e 'PGID'='100' and some with -e 'UMASK'='022'.


    It's driving me nuts! (Sas, Teamdrive, cache, downloads, traktarr...) everything automated but stuck with a permission error dropping every day!

     

     

     

  3. 53 minutes ago, Kaizac said:

    You can only use service accounts with team drives. And I don't think multiple actual accounts work for your own drive. You would have to share the folder with the other account. But I think it will then fail on making the rclone mount cause rclone can't see the shared folder.

    If you have the option, team drives are the easiest option for everything. Including being consistent with the storage limits of Google Workspace.

    Read a few posts up with responses to Bjur from me and Bolagnaise that should solve your issue.

     

    I don't want to be rude. But you have no idea what you are doing. And I don't think we can understand what you are trying to do. I don't see why you bring in Krusader which is just a file browser which can also browse to mounted files. I suggest you first read up on rclone and then what the scripts in this topic do before you continue. Or be precise in what you are trying to accomplish.

    Forgot to say, I've already tried bolognaise script and safe docker new perm.


    I've already in my script :

     

    # Add extra commands or filters
    Command1="--rc"
    Command2="--uid=99 --gid=100 --umask=002"

  4. Hi,
    Root user is driving me nuts!

    Since I upgraded Unraid to 6.10, I can't manage to keep my dockers working.

    Every docker is using -e 'PUID'='99' -e 'PGID'='100' (I've 2 sonarrs (1080-4k) and 2 radarrs, 2 syncars + 1 qbittorrent + Cloudplow).


    My folders are :
    Movies/HD and Movies/UHD.

     

    Every once a while, my folders HD and UHD are switching owner to root and then Sonarr/raddar can't import anymore!

    My script is updated and I think now that it's mergerfs running as root (as my scripts).

     

    What should I try to keep it working?


    Thank you,

     

  5. On 5/15/2021 at 11:03 PM, ich777 said:

    Please force an update of the container and try to remove the TURBOVNC_PARAMS variable again, have changed the Chrome container and now it should have no such collisions.

    The other containers with VNC are currently rebuilding now (Dockerhub is really slow with the uploads today about 800KB/s... :/ )

    It is working!

    • Like 1
  6. 22 minutes ago, ich777 said:

    I will look into this asap but from what I know the http port should be disabled by default.

     

    You actually can create a variable with the key: 'TURBOVNC_PARAMS' and the value: '-securitytypes none -httpport 5900'

    Then you don't have to edit the file in the container.

    Great, thus I won't have to manually editing it after rebuild!

    • Like 1
  7. On 5/13/2021 at 9:30 AM, ich777 said:

    Doh... :D

     

    Can it be that there something else is using port 5899?

    AS said above nothing in my containers isnusing port 5899.

    Your container is using httpport 5899 for vncserver. You'll need to add -httpport in start-server.sh in order to use more than 1 docker on same network :

     

    vncserver -geometry ${CUSTOM_RES_W}x${CUSTOM_RES_H} -depth ${CUSTOM_DEPTH} :99 -rfbport ${RFB_PORT} -httpport ${HTTP_PORT} -noxstartup ${TURBOVNC_PARAMS} 2>/dev/null

    It's working now.

  8. 11 hours ago, ich777 said:

    Can you please give me a little more context what you've changed exactly in both containers, screenshots would be super nice. :)

     

    My containers doesn't listen on port 5899 for http connections, they listen on port 8080 by default, that's why I created the variables so that users that want to run multiple containers through one Docker network have no issues. :)

    You actually change the http port with the variable 'VNC_PORT'.

     

    Do you also want to set a password in the Container for the VNC Connection? Have you also created a variable 'TURBOVNC_PARAMS' and left it empty? Otherwise the password won't work.

    Here you are :

    You already solved my case with NOVNC_PORT at the beginning of april. (

     

    I've tried VNC_PORT and NOVNC_PORT Variable.

     

    Chrome.jpg

    Jdownloader.jpg

  9. On 5/3/2021 at 5:38 PM, ich777 said:

    Not '$user' it have to be in capitals '$USER' and also not 'vncpassword' it has to be 'vncpasswd'.

     

    You did it like in the Firefox container? Or like the new method?

    The new method is described here:

     

     

    If you can't connect anymore I would like to recommend to start over and delete the chrome directory that was created in your appdata directory and also in the first place the whole container, after that pull a fresh copy from the CA App.

    Hi,

    I've been using 2 of your container within docker on a wireguard network container.

    Since the chrome update, only one container can access to internet.

     

    I'm using :

    NOVNC_PORT (different) on both container (redirect also on my wireguard container).

    RFB_PORT (different) on both container

     

    Here is throwing error (loop) :

    12/05/2021 08:15:47 Using security configuration file /etc/turbovncserver-security.conf
    12/05/2021 08:15:47 Enabled security type 'none'
    _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
    12/05/2021 08:15:47 Desktop name 'TurboVNC: b05b8e5d5d3a:99 (chrome)' (b05b8e5d5d3a:99)
    12/05/2021 08:15:47 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
    12/05/2021 08:15:47 Listening for VNC connections on TCP port 5903
    12/05/2021 08:15:47 Interface 0.0.0.0
    12/05/2021 08:15:47 Listening for HTTP connections on TCP port 5899
    12/05/2021 08:15:47 URL http://b05b8e5d5d3a:5899
    12/05/2021 08:15:47 ListenOnTCPPort: Address already in use
    ---Starting Fluxbox---
    ---Starting noVNC server---
    WebSocket server settings:
    - Listen on :6001
    - Flash security policy server
    - Web server. Web root: /usr/share/novnc
    - No SSL/TLS support (no cert file)
    - Backgrounding (daemon)
    ---Starting noVNC server---
    WebSocket server settings:
    - Listen on :6001
    - Flash security policy server
    - Web server. Web root: /usr/share/novnc
    - No SSL/TLS support (no cert file)
    - Backgrounding (daemon)
    ---Starting Chrome---
    ---Starting Chrome---

    Looks like both container are using 5899 port for http.

  10. 2 hours ago, ich777 said:

    Oh, now I get it, since you are using it through one container (one network) you also have to change the RFB port because they use both inside the container 5900 and two times 5900 can't work, I would suggest that you create a Variable with the Key: 'RFB_PORT' in both containers and as Value for the jDownlaoader2 '5905' and in the Chrome container '5906' (you don't have to create a port forwarding in your Wireguard container for that, this is only how they communicate internally in the container with noVNC and the VNC server).

     

    Hope that makes sense.

    Perfectly working !
    You should add it on github or docker as env variable!

  11. 2 hours ago, ich777 said:

    Can you send screenshots from the two templates?

    Do you want to connect through noVNC (web) or through a VNC vlient?

     

    You don't have to add a port if you want to connect through noVNC you have to change the default web port from 8080 to 6001 for the first container and 6002 for the second.

     

    If you want to connect through a VNC client then you have to also change to ports to two different ports for the containers (eg 8080 and 8081) and then add the VNC_PORT variable and also a new port entry to the containers for the VNC_PORT's.

    Here you are :

    When I'm connecting to VNC within my browser (whether chrome or Jdownloader), I only get Jdownloader webui. (or the 1st container i Launched)

     

     

    Bug redirect.jpg

    Chrome.jpg

    Jdown.jpg

    Wireguard.jpg

  12. On 3/8/2021 at 4:19 PM, ich777 said:

    Try a different port Container port 5900 and Host port something completely different for example 5950 or something like that.

     

    In my case I got many containers running with this setting to connect with a VNC Viewer to it from my local network for example Thunderbird.

    grafik.png.0351b9b2428b969a693c8902e7ea44fd.png

    Hi,
    I'm try to use 2 containers from you at the same time but I can't get them to work.

    I'm connecting though a VPN docker and added 2 NOVNC_PORT to 6001 and 6002.
    When I'm launching both container (chromium and Jdownloader) I can't get them to work.

    The port is not changed, thus when I go to my IP:6001 or IP:6002 its opening the same VNC (the first docker I launched)