Jump to content

planetwilson

Members
  • Posts

    242
  • Joined

  • Last visited

Posts posted by planetwilson

  1. I am in the same boat, Ryzen or a Xeon E5 build? The Xeon's just don't clock as high in general but wondering if I should be too worried. I am not a massive gamer so as long as they boost up to say 3GHz then together with my GTX 950 I think it would be one for moderate gaming. Then I could still have 12 or 14 cores for VMs...those X99 mobs are a bit pricey as well. The Ryzen equivalents look cheaper.

  2. 2 hours ago, planetwilson said:

    I have switched from Aptalca's docker which was working perfectly to the linuxserver one, kept my old nginx config and now getting this error:-

     

    nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address in use)

     

    I have the https port mapped to 4443. The reason for this is that I also run an OpenVPN-AS docker which intercepts all 443 traffic coming into the NAS (so I can run a VPN to home on TCP/443 and get around firewall restrictions in a lot of locations). You can configure OpenVPN to pass non-VPN traffic on to another server, in this case my letsencrypt/nginx docker which I have set to 4443 normally (with it appearing as 443 inside the docker)

     

    Now this worked perfectly before but doesn't with the newer linuxserver docker. Is this new docker hard-wired to only work with 443 somehow? doesn't seem like that should be the case?

     

     

    My fault. I had replaced ngingx.conf wholesale from the previous Docker. I did it again just transferring my server entries and all working now. Can't quite spot the difference though!

  3. I have switched from Aptalca's docker which was working perfectly to the linuxserver one, kept my old nginx config and now getting this error:-

     

    nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address in use)

     

    I have the https port mapped to 4443. The reason for this is that I also run an OpenVPN-AS docker which intercepts all 443 traffic coming into the NAS (so I can run a VPN to home on TCP/443 and get around firewall restrictions in a lot of locations). You can configure OpenVPN to pass non-VPN traffic on to another server, in this case my letsencrypt/nginx docker which I have set to 4443 normally (with it appearing as 443 inside the docker)

     

    Now this worked perfectly before but doesn't with the newer linuxserver docker. Is this new docker hard-wired to only work with 443 somehow? doesn't seem like that should be the case?

     

  4. Sorry if this has been answered, I did find a mention this error but it sounded like a problem with the Docker container? When I attempt to update my nginx + let's encrypt docker I get:-

     

    "Error: layers from manifest don't match image configuration"

     

    Do I copy off my config somewhere, make a note of the settings and delete / re-download? If. do that will it need to regenerate the certificates again? Currently got t sitting behind an OpenVPN docker which intercepts all 443 traffic. I can get that out of the way I guess for a new setup...

  5. Download is working for me. I did however have an issue in creating the ISO image from the USB key. Not sure if this is a Sierra problem or not. In the end I have gone with a hybrid approach and created a blank file image using the instructions from danofun here:-

     

    https://lime-technology.com/forum/index.php?topic=43816.420

     

    but then used the EFI folder provided by grid runner on his video example. Although I am obviously doing something wrong as I never get to the installer. get the Apple logo, then a loa of text, a reboot and then a no entry sign.

     

×
×
  • Create New...