EdgarWallace

Thanks @alturismo According to my search engine of choice you are using a Fritz!Box? The port of my Selfsat dish/sat>ip server is; 8000 Using your example: 2019-02-26 18:59:05.103 [ ERROR] satip: Cannot get http://192.168.178.30:49000/satipdesc.xml: Connection refused Using port 8000: 2019-02-26 19:01:49.576 [ ERROR] satip: Cannot get http://192.168.178.30:8000/satipdesc.xml: No such file or directory Seems that port 8000 is correct but how do I get the xml file?

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='tvheadend' --net='host' --log-opt max-size='10m' --log-opt max-file='1' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'TCP_PORT_9981'='9981' -e 'TCP_PORT_9983'='9983' -e 'PGID'='100' -e 'PUID'='99' -v '/mnt/cache/system/docker/appdata/tvheadend/':'/config':'rw' -v '/mnt/user/Recordings/':'/recordings':'rw' --satip_xml 192.168.178.30 'linuxserver/tvheadend' unknown flag: --satip_xml See 'docker run --help'. The command failed. Thanks @saarg the message appears when I am adding --satip_xml 192.168.178.30 which is the selfsat ip address.

Thanks to @j0nnymoe and @alturismo I was running tvheadend always in host mode and I have removed the DVB Edition. How do I remove the -p flag? The docker is pulling the wrong IP address. 192.168.178.28 is the server address, the sat>ip address is 192.168.178.30. Adding --satip_binaddr into Extra Parameters is causing a docker crash. 2019-02-26 10:06:08.656 [ INFO] main: Log started 2019-02-26 10:06:08.656 [ INFO] http: Starting HTTP server 0.0.0.0:9981 2019-02-26 10:06:08.656 [ INFO] htsp: Starting HTSP server 0.0.0.0:9982 2019-02-26 10:06:08.656 [ ERROR] satips: use --satip_bindaddr parameter to select the local IP for SAT>IP 2019-02-26 10:06:08.656 [ ERROR] satips: using Google lookup (might block the task until timeout) 2019-02-26 10:06:08.674 [ INFO] satips: Starting SAT>IP RTSP server 192.168.178.28:9983 2019-02-26 10:06:08.674 [ INFO] satips: SAT>IP Server initialized 2019-02-26 10:06:08.674 [ INFO] satips: HTTP 192.168.178.28:9981, RTSP 192.168.178.28:9983

It is a Selfsat antenna which has the Satip server imbedded. Question is how to pass through the satip ip address.

I would like to pass my SAT>IP Server to the TVHEADEND docker. unRAID DVB is showing no DVB Adapter Driver, is this the reason, why I don't see any TV Adapter in TVHeadend docker? Do I need unRAID DVB at all? I was trying to use --satip_bindaddr in Extra Parameter but this avoid Docker start. Here is my log: https://pastebin.com/GhN8WSt7 Any great ideas how to use my sat>ip server with TVHeadend? Thank you very much.

Thanks a lot @aptalca this what I thought as Weller. I tried the address shown in my initial post as well as 192.168.178.22:8081. The port is available so this can‘t be the issue either.

The RDP-Calibre Docker is offering a network server so that you can add books via your home network directly into your e-book reader and without attaching it to the server USB port or avoiding to load files into a Cloud and pulling the books from there. The server ist starting just fine but showing a strange address: 172.17.0.2:8081 (you can define a different port under "settings"). Is anyone successfully using that feature? Thank you,

Oh, I need to be more patient 😃👍🏼 Thanks a lot @gfjardim

@gfjardim, have I understood correct that I have to modify my /boot/config/smb-extra.conf and adding the following: fruit:time machine = yes fruit:time machine max size = 2T If the answer is yes I have to remaining questions: Adding 2T if I would like to use 2TB for my TM backup is correct as shown above? Where do I have to "...advertise it using the Avahi SMB service"? Thanks a lot for clarifying.

Since the last Nextcloud update (Nextcloud 13.0.2) it's complaining about some security issues I have added via my config settings: Der „X-XSS-Protection“-HTTP-Header ist nicht so konfiguriert, dass er „1; mode=block“ entspricht. Der „X-Content-Type-Options“-HTTP-Header ist nicht so konfiguriert, dass er „nosniff“ entspricht. Der „X-Robots-Tag“-HTTP-Header ist nicht so konfiguriert, dass er „none“ entspricht. Der „X-Download-Options“-HTTP-Header ist nicht so konfiguriert, dass er „noopen“ entspricht. Der „X-Permitted-Cross-Domain-Policies“-HTTP-Header ist nicht so konfiguriert, dass er „none“ entspricht. However, the default file is showing the correct settings: Anyone can guide me towards a solution? Thanks a lot.

I corrected according to your advise and the shutdown went fine yesterday. This should be visible from the diagnostics below. Cross fingers that the issue is gone. Thanks again @dlandon tower-diagnostics-20180424-2331.zip

The is great advise @dlandon as I had several unclean shutdown's in the past weeks (when I tried to shutdown either via Main/Array Operation/PowerDown or via Dynamix System Buttons). I followed your advise and have modified these settings: Settings->VM Manager->VM Shutdown time-out 300 seconds Settings->Disk Settings->Shutdown time-out 420 seconds Tips and Tweaks plugin: Processes to kill before Array is Stopped: ssh, bash Here is the diagnostics from yesterday....I can't see that anything from the 3 new settings were preventing my array to shutdown but someone smarter than me might identify the root cause. Thanks a lot.

Thank you very much @aptalca adding a comma into the subdomain(s) field is working well (adding a blank isn't working btw. this is what I tried earlier..) @allanp81 you might want to try that as well. Let me know if it is working for you too.

Hi, I am having an issue with my Letsencrypt Docker whenever I am updating it. The log is showing: LOG After each update I have to remove the Subdomain(s) but I am sure that there is a smarter way to deal with this. Anyone able to help? Thanks a lot.

I tried the method mentioned above but without any success.

Sure, Sure, I double checked and am also using the nextcloud.server.com method. Not fixed yet but I will try to tomorrow and reporting back if you think that is making sense.

I am running it as https://server.com/nextcloud which is your preferred setup - right? I just discovered that there are some entries in /mnt/user/system/docker/appdata/nextcloud/nginx/site-confs/default which need some change: rewrite ^/.well-known/carddav /remote.php/dav/ permanent; rewrite ^/.well-known/caldav /remote.php/dav/ permanent; Should is rather look like: rewrite ^/.well-known/caldav /nextcloud/remote.php/dav/ permanent; rewrite ^/.well-known/carddav /nextcloud/remote.php/dav/ permanent;

Thanks @CHBMB as always. Do you have any great idea how to fix my issue? I can Imagine that I‘m not the only one....

I am having a sync issue on macOS which was also discussed here: Nextcloud: Calendar and Contacts with MacOS and iOS (iOS sync is working very well). Seems that there is something needed in macOS: Troubleshooting Contacts & Calendar The document is telling us that the .htaccess file has to be edited within the following lines to be added: Redirect301/.well-known/carddav/nextcloud/remote.php/Redirect301/.well-known/caldav/nextcloud/remote.php/dav Which file do I have to choose as there are 2 of them: /mnt/user/system/docker/appdata/nextcloud/www/nextcloud/.htaccess /mnt/user/system/docker/appdata/nextcloud/www/nextcloud/config/.htaccess Thanks for help.

Thanks to @bonienl for having looked into this however the fix that @daemon9th described worked for me. Thanks a lot!!!

The update from 6.4.1 went well, however my ubuntu VM lost it's network connection (see picture). Any thoughts? Thanks a lot.

Update via WebUI went well. Running Nextcloud 13 now :-)

I have no clue if there is any other option but I do know that this was working well for me.

MinimWatch is available here, available for all kind of operating systems: LINK I am running it on my macOS machine so that I am having full control over my music library.

Yes it was - I was not aware it's simply "allowed" to modify the unRAID's webui Port 443. I just changed it towards 442 and all is working again. I do believe that some will fall into that trap as well as soon as they are updating. Maybe @aptalca you could add this to your great guide? Thanks @aptalca and @CHBMB