ErikH

Members
  • Posts

    12
  • Joined

  • Last visited

Converted

  • Personal Text
    (Unraid 6.7.0) - Z390 + i9 9900k, 32 Gb, GTX 1070 + R 580

ErikH's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Gentlemen, it took me some time before I actually had the time to work on this. I first removed router 2 and made sure the ip-range was correct. The network now works with only one (the first) router. Then I tried again, but had no luck. So after that I tried a clean install of the server and then it worked! Thanks!
  2. What I've read so far, to be (completely) safe, Hyper-threading should be disabled. I'm wondering if / how this will affect (my) unraid builds...
  3. Well it's a good excuse to clean up the network and take the 2nd router out of the loop. Been meaning to do that for some time, and this is a good reason. Port forwarding worked till now so I didn't expect that to be the problem. Anyway, I'll be back
  4. NP, I added an extra image to show how the routing is done. The reason for 2 routers is that router 1 used to be a simple cable modem. It broke when I was not at home and a technician replaced it with a fancy all in one modem / router. When I got back, I left it like that (due to the fact that the two are two floors apart) and just routed the ports on router 1 to just pass them on 1 on 1. routing.zip
  5. here's my routing. I have directed the a-records directly to my ip for now (my ip adress hasn't changed over a year), which I will set up further when I have this working. routing.zip
  6. 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'='xxxx@xxxxxxxx.xxx' -e 'URL'='xxxxxx.xxx' -e 'SUBDOMAINS'='nextcloud,deluge' -e 'ONLY_SUBDOMAINS'='true' -e 'DHLEVEL'='2048' -e 'VALIDATION'='http' -e 'DNSPLUGIN'='' -e 'PUID'='99' -e 'PGID'='100' -p '180:80/tcp' -p '1443:443/tcp' -v '/mnt/user/appdata/letsencrypt':'/config':'rw' -v '/mnt/user/appdata/letsencrypt/logs':'/var/log/letsencrypt':'rw' 'linuxserver/letsencrypt'
  7. My bad... I thought "Nginx is never starting up......" was the problem. So then... if the creation of the cert is failing, where do I look then?
  8. Alright, then I know the problem is Nginx. In the mean while I tried a clean unraid install + letsencrypt on yet another system and there the exact same thing happend. Any idea on how to fix this error?
  9. Thanks for your reply! Hoewever it seems that this doens't work either... all the other docker containers work fine except the letsencrypt one... I tried it on two machines now and both give the same result.
  10. I'm having this exact problem as well. When I port forward external port 80 to internal port 80, the unraid interface show up like normal on my domain. However the alternative internal port (I tried 180 and a few others and corresponding ports on the docker) will not work...