• Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

Bjur's Achievements


Apprentice (3/14)



  1. Am I the only one who hasn't received mails regarding GSuite transition? I'm afraid of loosing my unlimited date if they're degrading it, but I haven't received any mails and I can only see my active GSuite Business account and next invoice date in February 2022. Question 2: In OAuth consent screen have you guys made the project external or internal? I had it as external, but now I'm not sure.
  2. Hi I've configured Plex in conf file and SWAG starts without any errors, but when I select proxynet in Plex docker, it won't start Plex. All other services are working. Any suggestions?
  3. Got it working now. The error was that the client Id, secret I created was on another account. When I read the description it stated it didn't matter, but it did. Also @DZMM I used your enhanced settings for playback, and it works much better now. Thanks:) PS: The note from Google in regards to moving to workspace, did you guys get it on your primary emails or on the Gsuite mail? I haven't received any note about it yet, at least not what I could find.
  4. I have my team drives and SA running for a long time without any problems, but now want to create a normal drive + crypt. Here's my config. [googleAuDr] type = drive client_id = client_secret = xxx scope = drive server_side_across_configs = true token = {"access_token":"xxx"} drive = folder ID I found in Drive like the team drives. root_folder_id = Folder ID [googleAuDr_crypt] type = crypt remote = googleAuDr:GCryptAuDr filename_encryption = standard directory_name_encryption = true password = xxx password2 = xxx The problem is, that it doesn't use my drive ID when uploading but uses a random, so it doesn't show up in the folder I've created in drive.
  5. This is how my Drive looks. I have 4 TD configured besides this. [googleAuDr] type = drive drive = server_side_across_configs = true service_account_file = /mnt/user/appdata/other/rclone/service_accounts/sa_dau1.json client_id = client_secret = scope = drive [googleAuDr_crypt] type = crypt remote = googleAuDr:GCryptAuDr filename_encryption = standard directory_name_encryption = true password = password2 =
  6. But my confusion is that I will need to have a regular Drive in rclone and from what I can read I can't use SAs for regular Drive right? Then I need clientID. I've created a regular Drive in rclone but it will only create a mountpoint if I configure SAs beside the client id. Funny thing is I can run upload script and it uploads but can't see the test file in drive.
  7. Thanks for the quick reply. To understand correct. When you say I don't need client ID. If I have a regular Drive and want to access like the TD I need to create the Drive in Rclone and that needs the Client ID. I tried without and just copy a TD remote and edit the settings but no mountpoint and won't create. 2. Yes I mean playback time, but on my TDs I have both 4k and non-4k together, but perhaps I can try the settings in the mountscript.
  8. @DZMM: 1. As far as I understand you are using a regular Drive for music, but first uploads through TeamDrive and afterwards run a move script from TD to Drive right? How is the script like for this? I have 4 TD and 4 crypts (4 mountscripts and 4 upload scripts). I wanted to create a regular Drive, but the clientID etc, was to much hassle when having TD already, so a script to move from 1 to another I think is a good idea. 2. Also first part of my script is like this. Can I optimize it for loading times? I haven't used cache or anything like that. #!/bin/bash ###################### #### Mount Script #### ###################### ### Version 0.96.6 ### ###################### ####### EDIT ONLY THESE SETTINGS ####### # INSTRUCTIONS # 1. Change the name of the rclone remote and shares to match your setup # 2. NOTE: enter RcloneRemoteName WITHOUT ':' # 3. Optional: include custom command and bind mount settings # 4. Optional: include extra folders in mergerfs mount # REQUIRED SETTINGS RcloneRemoteName="google_crypt" # Name of rclone remote mount WITHOUT ':'. NOTE: Choose your encrypted remote for sensitive data RcloneMountShare="/mnt/user/mount_rclone" # where your rclone remote will be located without trailing slash e.g. /mnt/user/mount_rclone MergerfsMountShare="/mnt/user/mount_mergerfs" # location without trailing slash e.g. /mnt/user/mount_mergerfs. Enter 'ignore' to disable DockerStart="sonarr" # list of dockers, separated by space, to start once mergerfs mount verified. Remember to disable AUTOSTART for dockers added in docker settings page LocalFilesShare="/mnt/user/local" # location of the local files and MountFolders you want to upload without trailing slash to rclone e.g. /mnt/user/local. Enter 'ignore' to disable MountFolders=\{"media/temp,downloads/complete"\} # comma separated list of folders to create within the mount
  9. A couple of questions. 1. Has there been any significant changes to scripts within the last year, where you are recommending to update? I'm using Mergersf currently. Can something be gained in regards to Plex loadtimes? 2. What does people use for music or where there's a lot of files? Mount multiple teamdrives or I read using GDrive but then you will have disadvantages like limited storage or?
  10. Hi I've received this mail from Google, do I need to do anything to not loose files with this plugin: A security update will be applied to Drive On September 13, 2021, Drive will apply a security update to make file sharing more secure. This update will change the links used for some files, and may lead to some new file access requests. Access to these files won't change for people who have already viewed them. What do I need to do? You can choose to remove this security update in Drive, but removing the update is not recommended and should only be considered for files that are posted publicly. Learn more After the update is applied, you can avoid new access requests by distributing the updated link to your file(s). Follow instructions in the Drive documentation Which files will the update be applied to? See files with the security update
  11. You can just do as I do. Use exclusion to exclude metadata and subs from being uploaded.
  12. Sorry you are right, I've just reverted back to standard port 32400. But would it be more safes or is 32400 standard good enough since it's not a directly attached login local on Plex?
  13. Thanks so what you are saying that it is just as secure opening port 32400 instead of running it behind a reverse proxy? I don't have port 32400, since it's running on reverse proxy so port 1443 is open and also configured at 1443 at Plex settings.