EdgarWallace

Members
  • Content count

    783
  • Joined

  • Last visited

Community Reputation

3 Neutral

About EdgarWallace

  • Rank
    Advanced Member
  • Birthday 09/05/1963

Converted

  • Gender
    Male
  • Location
    Germany

Recent Profile Visitors

327 profile views
  1. MinimServer docker problem

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

    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.
  3. [Support] Linuxserver.io - Letsencrypt (Nginx)

    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
  4. [Support] Linuxserver.io - Letsencrypt (Nginx)

    @CHBMB that means it‘s working for you under 6.4? I have altered my post and it shows that there is an issue with port 443 already assigned. Gesendet von iPad mit Tapatalk
  5. [Support] Linuxserver.io - Letsencrypt (Nginx)

    This was working for unRAID 6.3.5 but it stopped working for 6.4. Anyone Else whole made that experience? Latest letsencrypt Docker is installed: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -e "EMAIL"="email@gmx.net" -e "URL"="mydomain.org" -e "ONLY_SUBDOMAINS"="false" -e "DHLEVEL"="4096" -e "PUID"="99" -e "PGID"="100" -e "HTTPVAL"="true" -p 85:80/tcp -p 443:443/tcp -v "/mnt/user/system/docker/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt68820e55413df4f6d12189d079334a943a01c4699136e38059fc459597f8670b/usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint letsencrypt (296916628be7ee045bd094ac8ebaa72631a8bd1146130c8480a19b91462dd0d4): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use. Gesendet von iPad mit Tapatalk
  6. MinimServer docker problem

    @steve1977 have you checked the "Show Log" in MinimWatch which is available to control MinimServer? You have to accept Terms & Condition, otherwise MinimServer doesn't start.
  7. MinimServer docker problem

    Well, only with HOST option the server is showing up e.g. in KAZOO. And yes you need to add the ports as there is no template existing,.
  8. MinimServer docker problem

    I just changed the Repository towards: nielsdb97/docker-minimserver This is a fork of the previous docker an is updated to the most recent version of MinimServer. All other Docker definitions can be kept.
  9. [Support] Linuxserver.io - Letsencrypt (Nginx)

    The was doing the trick: port forward http (tcp 80 -->> 85) as well as https (tcp 443 -->> 443) is required. Thanks a lot.
  10. [Support] Linuxserver.io - Letsencrypt (Nginx)

    I applied the fix...still not working: ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| 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] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... 4096 bit DH parameters present No subdomains defined E-mail address entered: email@gmx.net Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ... Certbot can obtain and install HTTPS/TLS/SSL certificates. By default, it will attempt to use a webserver both for obtaining and installing the certificate. certbot: error: argument --cert-path: No such file or directory Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for xxxxxxxx.xxxxxx.org Waiting for verification... Cleaning up challenges Failed authorization procedure. xxxxxxxx.xxxxxx.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://xxxxxxxx.xxxxxx.org/.well-known/acme-challenge/igQwFM5uEZH-G1E1iS-R0v-GlcC3-xv-g9F1n-9r51g: Timeout IMPORTANT NOTES: - The following errors were reported by the server: Domain: xxxxxxxx.xxxxxx.org Type: connection Detail: Fetching http://xxxxxxxx.xxxxxx.org/.well-known/acme-challenge/igQwFM5uEZH-G1E1iS-R0v-GlcC3-xv-g9F1n-9r51g: Timeout To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. /var/run/s6/etc/cont-init.d/50-config: line 134: cd: /config/keys/letsencrypt: No such file or directory [cont-init.d] 50-config: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
  11. [Support] Linuxserver.io - Letsencrypt (Nginx)

    Same here....everything was running fine until the todays container update: ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| 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] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... 4096 bit DH parameters present No subdomains defined E-mail address entered: email@gmx.net Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. /var/run/s6/etc/cont-init.d/50-config: line 134: cd: /config/keys/letsencrypt: No such file or directory [cont-init.d] 50-config: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
  12. MinimServer docker problem

    Great that you sorted it out. The remaining issue is that this Docker contains an old version of Minimserver so let‘s hope that this Docker is going to be updated.
  13. MinimServer docker problem

    Have you installed the Community Apps? That is a prerequesite. Please check the screen shot of the Docker settings. That should answer your remaining questions if you are a bit familiar with the unRAID Docker environment. Good luck!!
  14. MinimServer docker problem

    Good morning, here is how I implemented by using one of the Dockerhub (this is copy & paste of post #38 of the MinimServer Forum link I posted above. : https://hub.docker.com/r/tromatik/docker-minimserver/1.) You need to accept Dockerhub in CA2.) Install the Docker from above3.) Modify settings and add one Host Path4.) Starting your new Docker and open the log in order to accept Terms & ConditionsDone However, this version is not officially supported by Simon but his official guide doesn‘t provide a solution that is surviving a reboot.
  15. Real Docker FAQ

    Hi Squid, this is a great thread. Thanks for all your hard work. I have read through and implemented a Minimserver Docker that I found at Dockerhub: https://hub.docker.com/r/tromatik/docker-minimserver/ My /boot/config/plugins/dockerMan/templates-user/my-minimserver.xml looks like so: <?xml version="1.0"?> <Container version="2"> <Name>minimserver</Name> <Repository>tromatik/docker-minimserver</Repository> <Registry>https://hub.docker.com/r/tromatik/docker-minimserver/~/dockerfile/</Registry> <Network>host</Network> <Privileged>false</Privileged> <Support>https://hub.docker.com/r/tromatik/docker-minimserver/</Support> <Overview>MinimServer is a new UPnP AV music server with a number of innovative features...</Overview> <Category>Media Servers:</Category> <WebUI/> <TemplateURL/> <Icon/> <ExtraParams/> <DateInstalled>1506328130</DateInstalled> <Description>MinimServer is a new UPnP AV music server with a number of innovative features...</Description> <Networking> <Mode>host</Mode> <Publish> <Port> <HostPort>9790</HostPort> <ContainerPort>9790</ContainerPort> <Protocol>tcp</Protocol> </Port> <Port> <HostPort>9791</HostPort> <ContainerPort>9791</ContainerPort> <Protocol>tcp</Protocol> </Port> </Publish> </Networking> <Data> <Volume> <HostDir>/mnt/user/iTunes/Music/</HostDir> <ContainerDir>/media</ContainerDir> <Mode>ro</Mode> </Volume> </Data> <Environment/> <Config Name="Host Port 1" Target="9790" Default="9790" Mode="tcp" Description="Container Port: 9790" Type="Port" Display="always" Required="true" Mask="false">9790</Config> <Config Name="Host Port 2" Target="9791" Default="9791" Mode="tcp" Description="Container Port: 9791" Type="Port" Display="always" Required="true" Mask="false">9791</Config> <Config Name="Host Path 1" Target="/media" Default="/mnt/user/" Mode="ro" Description="Container Path: /media" Type="Path" Display="always" Required="true" Mask="false">/mnt/user/iTunes/Music/</Config> </Container> The config page is attached below. Container is starting well and working as expected. I have 2 remaining questions: is there any way to add a nice icon that is located somewhere on /boot where are the config files? I am not sure that this Docker is surviving a reboot Would be great if you can explain how to do that. Thanks a lot.

Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.