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
    Do you have htpasswd file in both letsencrypt and heimdall? If so, delete the one in heimdall. If not, clarify what you're doing. It's not clear where you're running the htpasswd command and where you're deleting the default file.
  2. aptalca
    Host networking doesn't work on the latest unraid. Plenty of posts in this thread if you search. Use bridge networking
  3. aptalca
    We do not support users running manual commands. The readme contains info on how to troubleshoot renewal issues. In your case, either your ip on duckdns is wrong or your port isn't forwarded properly
  4. aptalca
    The server is already claimed by an account, you can't expect to just claim it by another. Try removing it from the old account first
  5. aptalca
    https://github.com/linuxserver/docker-openvpn-as/blob/master/README.md#application-setup
  6. aptalca
    Comment out the main location block in the default site config
  7. aptalca
    Depends on if they made the file available at the same endpoint. It may work, worth a try, but you need to use the long version with all the extra digits after the dash
  8. aptalca
    That's likely the macvlan security feature that blocks connections between host and macvlan containers
  9. aptalca
    Did you follow the steps in the link I posted for you? You didn't even post a full log. You keep saying it doesn't work. I don't know how you expect us to help you more.
  10. aptalca
    Turn off cloudflare proxy (orange cloud)? That's what we recommend anyway. If you want to proxy through cloudflare, we don't officially support that (ie. you're on your own).
  11. aptalca
    Take one step at a time. You have not gotten your certs yet, no point in messing around with reverse proxy. See here: https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/
  12. aptalca
    Post the commands or settings you tried and the error messages you got.
  13. aptalca
    Extra domains takes fqdn's so add your subdomains in there as additional fqdn's
  14. aptalca
    Finally had time to look into it and figured it out. New build will be available shortly that will fix that error requiring restart of new containers.
  15. aptalca
    In the first scenario, why are you setting interface to eth0? It should be br1. Unraid 6.7 made some changes that introduced that iptables error when openvpn is used in host networking (and I guess macvlan). No idea what causes it.
  16. aptalca
    Are you talking about reverse proxying containers on macvlan? Then the answer is no. It's a docker restriction (security feature) that blocks connections between host and containers on macvlan.
  17. aptalca
    When it's officially released as either beta or stable, there will be automatic updates
  18. aptalca
    Code server subdomain config that comes with letsencrypt works with no issues here
  19. aptalca
    Such fixes should really be done upstream. But seeing as couchpotato isn't well supported anymore (for quite a while now), did you consider switching to radarr?
  20. aptalca
    I'm assuming you're making those go through the vpn only for outgoing connections, not incoming. Then why not make your whole lan go through the vpn? I use PIA and my whole lan goes out through the vpn by default via pfsense. Only for streaming devices (netflix and amazon refuse to work through vpn) I have a rule that lets them bypass the vpn based on their IP. I don't use vlans for containers or streamers (only for a guest network). Then you'll have all containers in bridge or host, and no issues with connecting to each other.
  21. aptalca
    Either your ip is incorrect on your dns, or your port forwarding is incorrect. Try this: https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/
  22. aptalca
    There are three types of networking for docker: host, bridge and macvlan. Host and bridge networks use the same ip as the host machine. Macvlan let's the container get its own ip. In this case you're using macvlan, and it has that security feature where it blocks communications between the container and the host ip (and everything that's using that ip). I don't know what your other containers are on so can't comment on them.
  23. aptalca
    Our image doesn't use acme, which is a third party script. We use the official client, certbot. Honestly, GoDaddy is not very good at DNS services. I'd take cloudflare over any of those domain registrar provided DNS service any day. Cloudflare is free, very easy to switch to and propagates changes almost instantly. You're better off using cloudflare as your dns provider. I have domains bought from various providers like dynadot and name cheap, but they all point the name servers to cloudflare, which handles dns for me
  24. aptalca
    If sonarr and radarr are on macvlan, and others are on a custom bridge, they won't be able to connect to each other. That's a docker security feature to prevent connections between the host (and the host networks) and macvlan
  25. aptalca
    You need to disable your http to https redirect in your default site config. You can't have both http and stream listening on port 80
×
×
  • Create New...