Ockingshay

Would anyone be kind enough to do a quick summary of what was announced?

the developer has started top update this again, from various pull requests. Will these get picked up on the weekly linuxserver update? EDIT* as if by magic the update was already there for it...thanks! seems to be working a lot better now as well

Drive management; Building in pre-clearing and so you can just plug in a drive and the gui prepares it, whilst the array is up and adds it with least disruption. ability to add and remove drives to grow or shrink the array in a very user friendly way. i have 15 x 3tb drives and as with all technology moving on, I can now buy 14tb drives. Would be great to be able to remove 4 old drives and replace with a single drive. All intuitively managed by the gui. baked in unassigned drive support. basically, very easily managed drive support to give users confidence to upgrade/change things around when required, which at the end of the day is exactly what unraid core functionality is all about....drive management.

many thanks, that fixed that error. Is there any way to run it as a custom ip address?, as i cannot connect to my other custom ip addressed dockers this way. I guess I may have to run this on a separate machine to allow access. It is the same issue with wireguard.

Just did a new install and have ticked privileged and set a custom ip address. everything is default. when i try to "start the server" from within the webgui i get the following error:

can someone please screenshot their docker page? i can get this to run in bridge mode (without or without privilege toggled) but it will not connect to devices. Just states in the webgui "waiting for device and eventually times out, although it's discoverable). I had this same issue with unifi controller and set it to host, but if i do that with this docker i get error: 2019/08/30 14:18:40 [emerg] 1954#1954: bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

I was having adoption issues when i changed to this docker and then i remembered i had the same problem before after an upgrade and i had to change the docker to "host" from "bridge". Restarted the docker and it has picked up all my devices. Might help someone if they have the same issue of devices stuck in an "adopting" loop.

Or in your router you could setup port redirection. I have mine as public redirect 443 to (local) dockerip:444

double post

OMG, dickhead...it was defined in the docker container haha. i'll leave this here though, just in case some one else is as stupid as me

August last year i set this all up and haven't touch it since, but my cert expired and so began the process of working out why auto-renew failed. In the end it was because there wasn't an "A Record" for heimdall that i set-up. But in the end I didn't use it, so i must have deleted it off of name cheap. I looked at the default file and i had commented out all the heimdall stuff, but when i look at the letsencrypt log it was failing due to it not being defined. I simply recreated the "A record", let the docker run it's auto-renew at 2am, like it does every night and it was successful. I would have thought that by deleting it from namecheap and commenting out the heimdall stuff in default, it wouldn't even know to look for it. There must be another location. Anyone with experience of this and namecheap have any idea where lets encrypt is getting it's info from? whenever i start lets encrypt docker it always references the 3 places i defined: Sub-domains processed are: -d www.xxxx.com -d start.xxxx.com -d heimdall.xxxx.com

Would be great to see this running in a docker. https://github.com/blawar/nut The switch scene is really motoring forward atm

Looking back at your posts you seems to be part of maintaining this docker? Will you be offering ongoing support for it? many thanks if you are

I bit the bullet and updated through the docker. First time i me I trashed it by restarting too soon, so I left it half an hour to install the database. After another length of time the program started fine and I’m on the latest version.

Well considering Pducharme hasn't visited this site since July, we could be in for a long wait

Do we update from within the docker or does @Pducharme have to update the docker?

I also received the email... i use dropbox for black hole locations in torrent clients to sync .torrent files across devices. Is there an alternative that can do this? needs to work across Mac, Windows, iOS and Linux ideally.

i created an "A Record" called home in NameCheap and pointed it to my server. i edited letsencrypt docker and added home as a subdomain i edited the "default" file in site-confs from heimdall.domain.com to home.domain.com in those 2 places above. What i've had to do with other dockers for example Ombi is edit their Base URL within the docker itslf. I was wondering as there doesn't appear to be a setting in hemdall for Base URL it was located in a config file. Am i missing anything else? Thanks

Is there a way to change this from heimdall.server.com to something else? i would like to use home.server.com but it only works if i use heimdall and i can't see a way in the app to change it. Is it hardcoded in a config file somewhere?

If i want to change the Base URL to /requests, do i simply change every instance of ombi to requests or are there only certain ones? In ombi GUI i have changed ombi in both locations (Application URL and Base URL) location /requests { return 301 $scheme://$host/requests/; } location /requests/ { proxy_pass http://192.168.0.3:3579; proxy_set_header Host $host; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Ssl on; proxy_set_header X-Forwarded-Proto $scheme; proxy_read_timeout 90; proxy_redirect http://192.168.0.3:3579 https://$host; } if ($http_referer ~* /requests/) { rewrite ^/dist/(.*) $scheme://$host/requests/dist/$1 permanent; } VS. (5 changes) location /ombi { return 301 $scheme://$host/ombi/; } location /ombi/ { proxy_pass http://192.168.0.3:3579; proxy_set_header Host $host; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Ssl on; proxy_set_header X-Forwarded-Proto $scheme; proxy_read_timeout 90; proxy_redirect http://192.168.0.3:3579 https://$host; } if ($http_referer ~* /ombi/) { rewrite ^/dist/(.*) $scheme://$host/ombi/dist/$1 permanent; }

oh you little beauty! i thought i just had to put it in your 2nd screenshot, and that it just had to be /ombi i didn't even see the ombi tab (1st screenshot) thank you again for your time and patience ? There doesn't seem to be any standardisation between apps! very confusing for my old brain...

aha, many thanks for your patience! Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='Ombi' --net='bridge' -e TZ="Europe/London" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -p '3579:3579/tcp' -v '/mnt/user/dockerapps/Ombi/':'/config':'rw' 'linuxserver/ombi' 3de6882b9be619ce644195869f09d5613b6fb296a2f2507e2f53deef37493f52 The command finished successfully!

yes, i can access it on http://192.168.0.3:3579/ombi how do i know what the rn command is? i installed ombi from CA log starts off like this: ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Hello, welcome to Ombi Valid options are: Ombi 3.0.3477-master Copyright (C) 2018 Ombi --host (Default: http://*:5000) Set to a semicolon-separated (;) list of URL prefixes to which the server should respond. For example, http://localhost:123. Use "*" to indicate that the server should listen for requests on any IP address or hostname using the specified port and protocol (for example, http://*:5000). The protocol (http:// or https://) must be included with each URL. Supported formats vary between servers. --storage Storage path, where we save the logs and database --baseurl The base URL for reverse proxy scenarios --help Display this help screen. --version Display version information. We are running on i Hosting environment: Production Content root path: /opt/ombi Now listening on: http://[::]:3579 Application started. Press Ctrl+C to shut down.

I have this: client_max_body_size 0; location / { try_files $uri $uri/ /index.html /index.php?$args =404; } location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; # With php7-cgi alone: fastcgi_pass 127.0.0.1:9000; # With php7-fpm: #fastcgi_pass unix:/var/run/php7-fpm.sock; fastcgi_index index.php; include /etc/nginx/fastcgi_params; } location /ombi { return 301 $scheme://$host/ombi/; } location /ombi/ { proxy_pass http://192.168.0.3:3579; proxy_set_header Host $host; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Ssl on; proxy_set_header X-Forwarded-Proto $scheme; proxy_read_timeout 90; proxy_redirect http://192.168.0.3:3579 https://$host; } if ($http_referer ~* /ombi/) { rewrite ^/dist/(.*) $scheme://$host/ombi/dist/$1 permanent; } location /radarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.0.3:7878/radarr; } and in Ombi GUI i have /ombi in "Application URL"