Jump to content

EdgarWallace

Members
 View Profile  See their activity

  • Posts

    894

  • Joined

  • Last visited

 Content Type 

Posts posted by EdgarWallace

    Dynamix File Integrity plugin

    in Plugin Support

    Posted

    Great @bonienl

    Worked very well, thank you very much: 

    root@Tower:~# /usr/local/emhttp/plugins/dynamix.file.integrity/scripts/bunker -b2 -u "/mnt/disk2/iTunes/Music/Eric Clapton/I Still Do"
Finished - verified 12 files, skipped 0 files. Found: 0 mismatches, 1 corruption (updated). Duration: 00:00:04. Average speed: 149 MB/s

     

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted · Edited by EdgarWallace

    On 6/6/2019 at 4:09 PM, saarg said:

     

    I think this belongs in the letsencrypt thread and not nextcloud as it hasn't anthing to do with the nextcloud container. So please move the conversation there.

    I'll anser you here now though.

     

    It's impossible for us to know what happened without any logs and saying it was working isn't helpful either.

    I don't know the inner working of letsencrypt, but it sounds wrong that you have so many certs. Or is this something you are modifying? I see you talked about adding certs to your devices earlier, but do not know what is the purpose of it.

     

    As for adding a subdomain, that is to trigger a change in the config so the certs are renewed. Then you can change it back.

     

    Please answer in the letsencrypt thread, as it belongs there.

    @trurl, thanks for your help in moving that into the correct thread.

     

    @saarg, I have never modified anything within the container because it was running as expected - until March 1st.

     

    I read, that letsencrypt is producing these file one after one e.g. /mnt/user/system/docker/appdata/letsencrypt/etc/letsencrypt/live/myurl.com/cert.pem is pointing towards the correct file in /mnt/user/system/docker/appdata/letsencrypt/etc/letsencrypt/archive/myurl.com/cert7.pem so having many of these files seems to be fine.

     

    I was asking mainly if there is a known issue with the container, because the log it isn't showing anything unusual. However, I might have overlooked something so it is attached now. 

     

    Thanks for your help.

     

     

     

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    12 hours ago, saarg said:

     

    You should not run that command yourself. It might screw things up instead of solving it.

    Add a subdomain and it will trigger a renewal.

    Thanks a lot @saarg

     

    I don't understand why the certificate wasn't renewed this time (March 1s). It was always working in the past. E.g. cert1.pem - cert6.pem are available in the respective directory but cert7.pem was missing and added with my manual action.

     

    Subdomain was always defined as (no changes from my side were made since ages): 

     , 

    I am using this container only for Nextcloud and I am accessing it via https://myurl.com/index.php/login

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    On 6/4/2019 at 1:20 PM, EdgarWallace said:

    I am having well running Nextcloud and Let's Encrypt Docker (log is saying: [services.d] done and Server ready).

     

    On March 1st the SSL Certificate was loosing validity and now all my devices (macos, iphone, iPad) can't access Nextcloud anymore. After done some search I thought that I have to download the renewed key at /mnt/user/system/docker/appdata/letsencrypt/keys/letsencrypt

     

    There are a couple of keys (cert.pem, fullchain.pem etc.) that are linked to e.g. /mnt/user/system/docker/appdata/letsencrypt/etc/letsencrypt/archive/myURL/cert.pem

     

    Whatever file I am loading into one of my devices it is telling me that it was loosing validity March 1st.

    Thanks for any help.

    Seems that Let's Encrypt didn't renew the certificate. I was searching but didn't found anything that is showing how to solve that renewal issue.

     

    Any hint?

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted · Edited by EdgarWallace

    I am having well running Nextcloud and Let's Encrypt Docker (log is saying: [services.d] done and Server ready).

     

    On March 1st the SSL Certificate was loosing validity and now all my devices (macos, iphone, iPad) can't access Nextcloud anymore. After done some search I thought that I have to download the renewed key at /mnt/user/system/docker/appdata/letsencrypt/keys/letsencrypt

     

    There are a couple of keys (cert.pem, fullchain.pem etc.) that are linked to e.g. /mnt/user/system/docker/appdata/letsencrypt/etc/letsencrypt/archive/myURL/cert.pem

     

    Whatever file I am loading into one of my devices it is telling me that it was loosing validity March 1st.

    Thanks for any help.

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    I am having well running Nextcloud and Let's Encrypt Docker (log is saying: [services.d] done and Server ready).

     

    On March 1st the SSL Certificate was losing validity and now all my devices (macos, iphone, iPad) can't access Nextcloud anymore. After done some search I thought that I have to download the renewed key at /mnt/user/system/docker/appdata/letsencrypt/keys/letsencrypt

     

    There are a couple of keys (cert.pem, fullchain.pem etc.) that are linked to e.g. /mnt/user/system/docker/appdata/letsencrypt/etc/letsencrypt/archive/myURL/cert.pem

     

    Whatever file I am loading into one of my devices it is telling me that it was loosing validity March 1st.

    Thanks for any help,

    [Plugin] IPMI for unRAID 6.1+

    in Plugin Support

    Posted · Edited by EdgarWallace

    On 3/6/2019 at 10:04 AM, dmacias said:


     

     


    Did you give it some time after you started the fan control? How long is your polling time? Also are your thresholds set with the editor for your fans?

     

    Yes, the Fan Speed Mode will be kept forever....my settings are shown below.

     

    [Plugin] IPMI for unRAID 6.1+

    in Plugin Support

    Posted

    My main server contains a X11SSL-CF board. IPMI was running very well but since a while the Fan Speed Mode is set at FULL. Hence my fans are running at full speed and only if I am setting it back to Standard or Optimal, IPMI plugin is taking back control and the fans are running at much lower speed.

    BIOS version is 2.2 from 05/23/18, Firmware is 1.48 from 06/22/18, Redfish 1.0.1

    Maybe I overlooked something during the recent IPMI updates? 

    [Support] Linuxserver.io - TVHeadend

    in Docker Containers

    Posted

    On 2/26/2019 at 8:01 PM, alturismo said:

    and after a few seconds google may try this ...

     

    --satip_xml http://IPADDRESS:8080/desc.xml

    Well, I did all may home work and even updated my Selfsat device. According to this site the correct RUN_OPT should be: 

    --satip_xml http://192.168.178.30:8000

     

    However, doesn't work for me. TVheadend even doesn't show anything under DVB Input.

    [Support] Linuxserver.io - TVHeadend

    in Docker Containers

    Posted

    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? 

    [Support] Linuxserver.io - TVHeadend

    in Docker Containers

    Posted 

    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.

    [Support] Linuxserver.io - TVHeadend

    in Docker Containers

    Posted

    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?

    Quote

     

    Host vs. Bridge

    If you use IPTV, SAT>IP or HDHomeRun, you need to create the container with --net=host and remove the -p flags. This is because of a limitation in docker and multicast.

     

     

    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

     

    [Support] Linuxserver.io - TVHeadend

    in Docker Containers

    Posted

    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.

    (Support) Aptalca's docker templates

    in Docker Containers

    Posted

    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,

    Time Machine over SMB (Mac OS Sierra)

    in Feature Requests

    Posted · Edited by EdgarWallace

    @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.

×
×
  • Create New...