blacky89

Members
  • Posts

    14
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

blacky89's Achievements

Noob

Noob (1/14)

2

Reputation

  1. Man you do really know everything! Thank you so much! I did not uncheck that box in the advanced settings. Never looked deeper into the settings as it worked with my mac. No idea why it worked, as localhostonly is still checked there. Now that my windows machine is set up, I need to find a way to permanentely map 9666 to the unraidip from mac OS. But at least that I should be able to figure out myself. Thank you again sir !
  2. I have recieved great help in this forum, hope someone knows an answer to this: As far as I know, jdownloaders click n load runs on port 9666. I have added that port to the jdownloader docker. On my windows machine, I used netsh interface portproxy add v4tov4 listenport=9666 connectaddress=192.168.178.100 connectport=9666 listenaddress=127.0.0.1 However, I am still not able to use click n load. Anyone knows what im missing ? Edit: Really dont get it. If I run the same command on my windows machine but change the contactaddres to the IP of my mac, everything works. I click the click and load button on my pc and the jdownloader on the mac picks it up. However, using the unraid machines Ip, it doesnt work. Does the dockers JD not come with cnl capabilities ?
  3. yeah, should :'( I'll monitor this thread, if anyone has another idea... Thank you so far man Edit: I did it so often. It didnt work. I didnt know why. Felt like doing it one more time just now. It worked. I dont know why. The joy of working with computers. I'm fairly sure my fritz box had a hiccup. port 443 is open now. Next step: Getting it to work with mineOS and Nextcloud. Hope I can do that on my own.
  4. Huh. canyouseeme gives me an error for 443 and 2132 I doubt there is anything wrong with my ddns, I have verified the correct spelling multiple times and it is most certainly routing to my IP. Edit: Oh well, I give up for now.
  5. yup. installed the nginx docker. I can reach the landing page from that one from within the network as well as from the ddns.
  6. shouldn't I at least be able to see the default landing page from unraidmachine:2132 from within the local network ? Because I cant. Its like its not running. Or would that only be running after the connection was successful?
  7. No offence taken at all. Sometimes you just get confused and someone else just needs to look at it for a second. I have no doubt I'm just making a rookie mistake. Router interface is german, but it should be self explanatory. I really do appreciate your help.
  8. Yes, the ddns is working perfectly. For example, I have the jdownloader docker running and forwarded its port. I can connect to its interface via XXXX.duckdns.org:JdownloaderPort just fine.
  9. Just did that before running it, same result :'(
  10. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="Nginx-letsencrypt" --net="bridge" --privileged="true" -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -e "EMAIL"="[email protected]" -e "URL"="XXXXXXX.duckdns.org" -e "SUBDOMAINS"="www" -p 2132:80/tcp -p 443:443/tcp -v "/mnt/user/appdata/Nginx-letsencrypt":"/config":rw aptalca/nginx-letsencrypt adb8d02c04a3c41e18866e7be435ed10dd33ed416c18ea7eab31f4a2f269ea41
  11. Hey guys, It just doesnt want to work for me. I forwarded port 443 to the Unraid machine in my router, I believe I entered everything correctly. I'm probably just being stupid, but I would really appreciate your help guys: *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/firstrun.sh... Setting the correct time Current default time zone: 'Europe/Berlin' Local time is now: Mon Nov 7 19:18:27 CET 2016. Universal Time is now: Mon Nov 7 18:18:27 UTC 2016. Copying the default nginx.conf Copying the default nginx-fpm.conf Copying the default site config Copying the default landing page Copying the default jail.local Copying default fail2ban filters SUBDOMAINS entered, processing Sub-domains processed are: -d www.XXXXXXXX.duckdns.org Creating DH parameters for additional security. This may take a very long time. There will be another message once this process is completed Generating DH parameters, 2048 bit long safe prime, generator 2 This is going to take a long time ...+....................+...+...+...+...+...+........................................................................................+.........................................+.....................+........................+...+..............................................................................................+.................+...................................................................................................+...................................................................................+.......................................+...+...+.........................................................................+...........................+....................................................+......................................+...+.....+...+...+...+...+.............+...+.....................................................................+...+...............................................+...+..............+.....................................................................+..........................+.....................................................................+.................................................+.......................................................................+..................+...............................................................................................+...+.............................................+...................................................................+.......................................+...........................................................................................+..............................................................+...+.................................................................................................+..........+...................................................................+.......................................................+..............................................+.........................+....................................................+.....................................................................................+.....................................................................+...+.................................................................................................+........+...+...+...........................+.......+..........+...............................................+...+..........................................................................................+..............+...+............................................................................+.........................................+.......................+..............................+...+............................+...+..................................................................+...+.................................+...+...............................+......................................+................................................................................................+...........................+....+...................................+............................................................+......................................+..............................................+................................................................+....................................................+...........+...............+....................................+.....................................+.................+.......................+...+............................+...++*++* DH parameters successfully created - 2048 bits Generating new certificate Upgrading certbot-auto 0.8.1 to 0.9.3... Replacing certbot-auto... Creating virtual environment... Installing Python packages... Installation succeeded. WARNING: The standalone specific supported challenges flag is deprecated. Please use the --preferred-challenges flag instead. Saving debug log to /var/log/letsencrypt/letsencrypt.log Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org Obtaining a new certificate Performing the following challenges: tls-sni-01 challenge for XXXXXXXX.duckdns.org tls-sni-01 challenge for www.XXXXXXXX.duckdns.org Waiting for verification... Performing the following challenges: tls-sni-01 challenge for XXXXXXXX.duckdns.org tls-sni-01 challenge for www.XXXXXXXX.duckdns.org Waiting for verification... Cleaning up challenges Failed authorization procedure. XXXXXXXX.duckdns.org (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to XX.XXX.XXX.XXX:443 for TLS-SNI-01 challenge, www.XXXXXXXX.duckdns.org (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to XX.XXX.XXX.XXX:443 for TLS-SNI-01 challenge IMPORTANT NOTES: - If you lose your account credentials, you can recover through e-mails sent to [email protected]. - The following errors were reported by the server: Domain: XXXXXXXX.duckdns.org Type: connection Detail: Failed to connect to XX.XXX.XXX.XXX:443 for TLS-SNI-01 challenge Domain: www.XXXXXXXX.duckdns.org Type: connection Detail: Failed to connect to XX.XXX.XXX.XXX:443 for TLS-SNI-01 challenge To fix these errors, please make sure that your domain name was entered correctly and the DNS A 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. /etc/my_init.d/firstrun.sh: line 138: cd: /config/keys: No such file or directory Error opening input file cert.pem cert.pem: No such file or directory * Starting nginx nginx ...fail! * Starting authentication failure monitor fail2ban ERROR No file(s) found for glob /config/log/nginx/error.log ERROR Failed during configuration: Have not found any log file for nginx-http-auth jail ...fail! *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 326 Nov 7 19:20:11 934a18475510 syslog-ng[335]: syslog-ng starting up; version='3.5.3'
  12. Love this docker, super easy to set up. However, I agree, I should be able to disable rescan on restart. I have like a thousand photos, it takes forever. ------------------ To scan from two different path, you need to add them when you install the docker. Afterwars, you need to go to the install folder of minidlna and edit the minidlna.conf. Under "set this to the directory you want scanned", you need to write "media_dir=/ followed by the countainer path you gave it when installing the docker. Example: The standard path, /mnt/user/Media/ is mounted to container path /media. I have another folder on my server that I want to share, at /mnt/user/Eltern/. I mounted this one to the container path /eltern when installing the docker. So I have two container paths, /media and /eltern. In the minidlna.conf, the given part would look like this for me: Important lines are in bold. Now the DLNA Server will scan for files in /media and /eltern, which we previously mapped to /mnt/user/Media/ and /mnt/user/Eltern/ respectively when installing the docker. Dont forget to restart the docker after editing the conf file.
  13. Hello, I recently build my machine for unraid and it was quite some work to set it up, but everything worked really well in the end. Unraid really is great. So now I ran into a problem with some of the other dockers interfaces. mineOS and nextcloud for example are reachable via https only, which is nice. However, I always have to confirm in my browsers that I trust the certificate. I guess I need to generate new certs for those dockers, so the browsers stop complaining ? I tried some stuff with the Nginx-letsencrypt docker, but it didnt work out for me. I'm fairly sure I did it wrong anyway If anyone got a simple guide on how to generate or renew certs with this docker, I'd really appreciate it. I usually google my way to success, but it didnt work out this time and its frustrating. I bet its very easy once you know how to do it. Note that I do not necessarily need this to work external but mainly on the intranet, for example 192.168.178.111. You get the idea. I assume its the same way for both of this though. I'd be really thankful if someone could help a noob here out.