Jump to content

aptalca

Community Developer
 View Profile  See their activity

  • Posts

    3,064

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Everything posted by aptalca

  1. aptalca
    You can have access to your entire lan in bridge mode. Don't change every setting in the gui, especially don't try and change the server ip. Just add your subnet to the nat settings and check the box to allow clients access to other devices on your lan
  2. aptalca
    Update again. That was already fixed last night
  3. aptalca
    Glad to hear you figured it out. And just an fyi, "Literally just upgraded the container to the latest version" often means "I changed a bunch of other things as well but I can't remember at the moment" 😉
  4. aptalca
    It's been discussed to death. Harmless lua error. Unrelated. Server ready means nginx is up and running. Check your dns settings and port forwarding
  5. aptalca
    https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/
  6. aptalca
    You know about "mc", right? Midnight Commander
  7. aptalca
    Not sure, it's a docker security feature to block connections between host and macvlan. I don't recommend using macvlan unless you really have to. I only have 2 services on macvlan just so I can set up an ip based rule to let them bypass vpn. But even that is a fringe case
  8. aptalca
    Go back a few pages, there was a detailed overview
  9. aptalca
    Nope
  10. aptalca
    Use bridge networking
  11. aptalca
    No idea with the little info you provided
  12. aptalca
    Why would unraid be forced to do that? They don't currently put out a new release when there is a new docker update, or an update to the Intel gpu drivers, or kernels, etc. They put out a release when they feel like it or when there is a major security fix. We on the other hand feel like we are forced to put out an update for this addon whenever there is a new unraid release. It is plenty of extra work for us.
  13. aptalca
    That ip is what letsencrypt is getting for your domain name. Check your dns settings if that is not your public ip
  14. aptalca
    You can leave it. When you type address in the url bar (inside your lan), use https so the requests go to letsencrypt. Http requests will go to unraid's port 80
  15. aptalca
    That was just added a few days ago. It will be included in the next letsencrypt build: https://github.com/linuxserver/reverse-proxy-confs/pull/111
  16. aptalca
    The readme explains how to troubleshoot that
  17. aptalca
    Look into hairpin nat
  18. aptalca
    The letsencrypt log you posted earlier shows port 80 going to unraid gui
  19. aptalca
    Limetech would just have to include the nvidia driver in the unraid build. Nvidia runc could be offered as an official plugin or baked in. That's what chbmb does, unpack unraid, bake in nvidia drivers and runc, and recompile. But because chbmb doesn't exactly know what may or may not have changed in unraid releases (not open source) he has to reverse engineer quite a bit. Qnap on the other hand bakes nvidia drivers and runc in their software.
  20. aptalca
    It's your router and/or port settings. I'm assuming you're running unraid on port 443. Your router is redirecting internal (lan) requests to your domain to the unraid ip in the same 443 port, so you're getting unraid. You can move unraid's https port to something else and run letsencrypt on 443 instead
  21. aptalca
    Your port forwarding is not correctly applied. Try restarting the router
  22. aptalca
    Open a github issue for a feature request and we'll add it when we get to it
  23. aptalca
    I'll look into port share. It sounds like it might be useful
  24. aptalca
    No, there is no dyn dns update. We recommend ddclient or router based solutions Edit: looks like saarg beat me to it
  25. aptalca
    Never used port share in openvpn, don't really know anything about it. Unfortunately stream and http cannot listen on the same port. For a while I used port 80 with stream for openvpn. Then I switched to using port 53 over udp. Both let me access openvpn on various public wifi that normally block vpn connections. It's not bulletproof, but works well. I'm now using wireguard over 53 udp and openvpn over 80 tcp
×
×
  • Create New...