djvj

Thanks saarg, I did figure out what to do and updated my post above before I noticed you replied. It was the manual approach, but did fix the images and my SSH url all at once. Will your solution work for both? Update: I tried adding that variable and changing it to match my url and port I used in the external_url setting, restarted server, but it did not have any effect. I defined the the setting as so: external_url 'http://MYURL.com:9080/'; gitlab_rails['lfs_enabled'] = true; Images and SSH still show unraid.

All images uploaded into gitlab, like profile or a project image are trying to load from the internal url, not external: http://unraid:9080/uploads/user/avatar/2/avatar.png http://unraid:9080/uploads/project/avatar/1/RL_1308x1066.png That url should not be pointing to unraid. Is there a setting or something I need to change that will affect all urls? Even when looking at the SSH of my git project, it uses unraid. UPDATE: I fixed this by editing the external_url in the gitlab.rb file by SSH into the docker and editing that file manually: https://docs.gitlab.com/omnibus/settings/configuration.html#configuring-the-external-url-for-gitlab Is there any way to control this as a docker setting instead?

Thanks for the info binhex. linuxserver's docker doesn't have any port mappings in the docker settings, so it's not apparent up front what ports it's using. The thing is, are you sure there is a conflict with the other deluge docker when the initial install of your deluge docker went fine? It only gave the conflicting port issue when trying to restart this docker. Because of this it seemed more like something that was installed with this docker wasn't shutting down or restarting right when the docker tried to start again.

Thanks, that fixed it!

I just installed this docker for the first time. Install went ok. I went back and added another mapping, but when I clicked apply, it could not restart the docker and got this error: If I try start it again I get a server execution error. I tried removing the docker and installing it again but now it wont install with the same error.

After adding a couple large gamecube torrents, deluge no longer connects from the connection manager, I just get stuck with the blank web gui. The only thing in the log is now this: /usr/lib/python2.7/site-packages/deluge/_libtorrent.py:59: RuntimeWarning: to-Python converter for boost::shared_ptr<libtorrent::alert> already registered; second conversion method ignored. import libtorrent as lt /usr/lib/python2.7/site-packages/deluge/_libtorrent.py:59: RuntimeWarning: to-Python converter for boost::shared_ptr<libtorrent::alert> already registered; second conversion method ignored. import libtorrent as lt /usr/lib/python2.7/site-packages/deluge/_libtorrent.py:59: RuntimeWarning: to-Python converter for boost::shared_ptr<libtorrent::alert> already registered; second conversion method ignored. import libtorrent as lt /usr/lib/python2.7/site-packages/deluge/_libtorrent.py:59: RuntimeWarning: to-Python converter for boost::shared_ptr<libtorrent::alert> already registered; second conversion method ignored.import libtorrent as lt If I try to open the connection from the manager, nothing happens and it says in the lower left "Not Connected". Everything was working great until these last couple of torrents I added. I think I also updated version to latest a couple days ago as well.

Running v6.2.4

WebUI cannot be accessed on a new install of this docker. Running unraid 6.2.4. docker log: http://pastebin.com/eYHrP8WF my appdata points to: /mnt/cache/appdata/deluge Restarting the docker once allowed web.conf and hostlist.conf.1.2 to be created in the appdata folder as these were not there on first boot but am still unable to connect. I read through this thread but was not able to find anything specific to fix this issue. Update: was able to fix this by setting network type to Host. All my other dockers work fine as bridge but this one failed when set to that.

Trying to give rTorrent access to my /Games share so for example I can update/overwrite my Mame roms in /Games/Mame/. I added a path in the docker like so: Config Type: Path Container Path: /games Host Path: /mnt/user/Games Access Mode: Read/Write I can access the folder within rTorrent by adding a torrent and settings it's download path to /games/_Test (for example). When I look in my cache folder, I can see it created a folder as /mnt/cache/Games/_Test. When I download files from a torrent to this folder, it creates the files, and they are the right size, but they are essentially blank/corrupted files. The torrent also never changes from the Downloading state. When I save the torrent to the /downloads path (mapped to /mnt/cache/downloads/), it saves the files fine (in /mnt/cache/downloads/rutorrent/complete/) and torrent starts seeding. I checked permissions on the folders and they are owned by nobody and CHMOD of 777. I initially had the /Games share set to Secure, but I also tried Public and still the same. What am I missing here? Update: I installed the deluge docker and with same exact mapping, a test torrent went to seeding fine. So this is related to rTorrent only. I also tried legacy-rTorrent docker and had the same issue as well.

I also would love this. Sent from my SM-N910V using Tapatalk

I often am not able to login to this. I don't know what causes it, but I will be asked for a user/pass and I get "login incorrect". I notice it often happens after having 2 connections open already to it and I try a 3rd and get this error. At the moment, I have no connections open and still cannot login. The log shows this when I attempt: Dec 6 16:12:07 Storinator login[10711]: ILLEGAL ROOT LOGIN on '/dev/pts/11' from '192.168.1.6' I saw this thread, so it may be that I have too many ghost connections. If this is the problem, how can I clear these ghost connections? I also noticed if I have just one SSH connection, I cannot use this plugin to telnet at all.

Ok so this round I was able to shut the docker from unraid. Last night I wasn't able to and Sonarr got locked up. At least I fared better this time. Only reason I got suspicious is because sabnzbd had no problem shutting down from its own gui, but sonarr didn't. As long as I can still shut the docker from unraid, I can hopefully shut the array fine. If not, I'll look further into what you suggested. Thanks so far.

I posted a piece of the trace log in the post above. I reconnected it to sabnzbd. It wasn't running because I was trying to shut down the array so I can add more drives. I brought it back up in the log above. That wasn't the issue though. I can try your other suggestions though. I do have my 2 eth ports in bridge mode, that's the only slightly unusual network setup if you want to call it that. Only one is even connected though.

I am unable to safely shut down this docker. When I try from within Sonarr itself by pressing the power button in the settings, it says it will shutdown shortly but never does. It also tries to connect to sabnzbd every time I try to shutdown as well, which I don't see why it would. This is an excerpt from the log: Sabnzbd Unable to connect to SABnzbd, please check your settings: Unable to connect to SABnzbd, please check your settings 18:59 Sabnzbd Couldn't get download queue. Unable to connect to SABnzbd, please check your settings 18:59 TaskExtensions Task Error: Unable to connect to SABnzbd, please check your settings 18:59 LifecycleService Shutdown requested. 18:59 TaskExtensions Task Error: Unable to connect to SABnzbd, please check your settings 18:58 LifecycleService Shutdown requested. 18:58 RssSyncService RSS Sync Completed. Reports found: 225, Reports grabbed: 0 18:58 DownloadDecisionMaker Processing 225 releases 18:58 RssSyncService Starting RSS Sync 18:58 Sabnzbd Unable to connect to SABnzbd, please check your settings: Unable to connect to SABnzbd, please check your settings 18:58 Sabnzbd Couldn't get download queue. Unable to connect to SABnzbd, please check your settings 18:58 Sabnzbd Unable to connect to SABnzbd, please check your settings: Unable to connect to SABnzbd, please check your settings 18:56 Sabnzbd Couldn't get download queue. Unable to connect to SABnzbd, please check your settings 18:56 TaskExtensions Task Error: Unable to connect to SABnzbd, please check your settings 18:56 LifecycleService Shutdown requested. If I try to Shut the docker from unraid, it hangs forever with no ability to shut it down, even from CLI. The only thing that somewhat worked was stopping the docker service. Also here is an excerpt from the trace log after I clicked shutdown. You can see it didn't process anything except go onto it's normal routine and not shutdown. http://pastebin.com/4m8C35Pt

So after rebooting server, the log issue went away...

I just got this when trying to view my system log from the stats tab: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 120 bytes) in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(300) : eval()'d code on line 73 It didn't happen a couple days ago and I haven't added anything new plugin/docker-wise since. I've only been adding more HDDs to my array. Any clue how to fix before I start uninstalling some dynamix plugins to figure out which is causing it? Using unRaid v6.2.1