4554551n

"additional_ports"? I watched the video abvoe and followed the instructions there. And I did set up a "port" config type in deluge with Host Port being 9117 (the port used by jackett), but navigating to the URl just gives the default can't be loaded screen. Jackett has no webui option now, and that's fine. I can use bookmarks lol, but putting in the URL:port, having set the extra "port" in deluge still doesn't work, and I followed the instructions in the above video specifically, so I'm really unsure why that's happening

Can anyone please shed any light on this? It's super confusing why the webgui doesn't work

Could someone please help me with a strange issue I am having. It relates to external storages using SFTP. There are two issues. First (and this isn't that important for now) is that using RSA private key doesn't work. No matter how I configure it, it says cannot read key (RSA 4096 key, generated in linux via ssh-keygen, that connects in fine). Secondly, and this is a lot more concerning, and I am completely stuck: Using RSA public key, created by NC, I can connect to external shares, and upload files. But I cannot then download those files again (accessing the server directly, the files are fine, I can download them through other means, they work etc) Logs are pointing to SFTP.php as the culprit, but that's literally as far as I am able to get. For example: Here is trying to save a file I uploaded ``` Error: fopen(sftpread://home/[username]/public//gba.7z): failed to open stream: "OCA\Files_External\Lib\Storage\SFTPReadStream::stream_open" call failed at /config/www/nextcloud/apps/files_external/lib/Lib/Storage/SFTP.php#378 GET /remote.php/webdav/[username]Share/gba.7z?downloadStartSecret=[11 character code] from [IP] by [username] at 2020-08-26T08:13:59+00:00 ``` line 378 is $handle = fopen('sftpread://' . trim($absPath, '/'), 'r', false, There are other errors for opening files, trying to save uploaded files, copying uploaded files. Basically anything to do with interacting with a file that's been uploaded to the external share (all SFTP shares) via NC

Ok, that's been super helpful, thank you. I still have the webui problem even though I forward the port 9117 in the delugevpn container (which I didn't do before the video). Everything works, curl ifconfig.io is the same on both containers, and radarr and sonarr test fine with the jackett based indexers(!), but I still can't get at the webui using ip:port. Just says connection timed out. Though it does correctly add "/UI/Dashboard" after ip:port automatically like it would the old way. Any thoughts?

Thank you, that's a little awkward, but otherwise a really good work around. However I notice that doing that removes the webUI option from the jackett docker, and I can't navigate to it via the port anymore. Do you just set the settings you want, then make the above change, and revert the change next time you want to modify jackett again, or is there an easier way? @binhex I was wondering if this is something you'd consider looking at? Not rushing, just curious if waiting is a valid option, or I need to look more into exploring something like the above?

Ok, so I can set it persistent as above, I will try that. But to confirm, are you saying worst case scenario is it stops ingestion and pops up with errors? Am I right in understanding that if that happens, I can set the license type to free in the GUI at any point thereafter, and things will swim along? Forwarders as I understand cache everything if they can't send it, so I may get a bit of log build up, but once that license is set to free, it should just open the flood gates? Or is it not quite as simple as log once "in a while" and set the license to free via GUI? Also, could you please confirm what you mean by "Delete all default indexes from disk" Is that referring to the "main" index? Does this=data loss? Would the work around there (if I wanted to keep using trial) to create a new custom index straight away and keep everything in that?

Thank you. I'll get onto all of that over the weekend, there's a bit there to get my head around. Quick question about the license though cos that's something I can knock out quickly: so this container is made to run the non free license presumably for your own necessity. *So how would I go about changing that to free (that you say I would need to do every update)? Also, with autoupdate dockers, what would happen if I updated the docker, and didn't immediately change it to free? Would I have issues ingesting logs from forwarders (other issues?), or it would work perfectly fine as long as I changed it within the trial period window of 60 days (and then what would happen if I didn't do it in time)?

Hi, I am trying to set this up for the first time and have a couple of questions: Re resetting trial license: If I don't need the enterprise version, and the free version suits my needs, can I just never worry about this and keep splunk running as a free version? Re splunk index/data location: I would really like to set up the hot bucket to live in appdata (on the cache, faster writes to the SSD/not constantly hammering my array with writes) limited to maybe 2-3GB (or when the docker is restarted), and have the warm and cold buckets moved to the array (so as not to fill up the cache disk). Could I please have some guidance in how I would use the docker edit menu in unraid to create the extra folder/mount point for the warm and cold (and frozen/thawed I guess?) buckets? Note, I am seeing on splunk docs that both hot and warm buckets live in "$SPLUNK_HOME/var/lib/splunk/defaultdb/db/*" so it may be impossible to separate them, in which case maybe how can I keep hot and warm on the cache, but all the others on array? (I would like to keep Frozen buckets archives and not deleted too, that's kinda the point of a massive RAID array, right)

Hi binhex, I've just joined this forum to say I've got the same issues happening as described by Silverhand. I am on 6.8.3, and the latest binhex-jackett docker image, which goes nuts when the pia socks proxy is applied. I have it pinned to a CPU as you suggested to mitigate the damage. Would it be possible to please ask you to have another look at this, as it does seem to be affecting a few people. [edit] Pinning to CPU doesn't mitigate the errors from the other dockers, so it requires a lot of manual oversight and regular restarts just to have sonarr and radarr to work as intended and get regular automated downloads.