Jump to content

aptalca

Community Developer
  • Content Count

    2527
  • Joined

  • Last visited

Everything posted by aptalca

  1. Don't mess with mapping folders in those locations. To test, just edit the crontab file under your config folder and restart the container. Make sure you have more than 1 minute between your upcoming script run time and restarting the container.
  2. That's strange. I have a gtx1060 and a gt710. Similarly, 1060 is used for transcoding in emby and 710 is used for a win vm. They both work fine. I did not stub the cards, emby config defines the id for 1060 so it leaves the 710 alone. Are you starting unraid in gui mode? I do headless and it uses the mobo built-in matrox gpu. That could be the main difference between our servers.
  3. Try this: https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/
  4. That's a new one for me. Check that file /config/etc/letsencrypt/renewal/website.com.conf to make sure it contains all the parameters including this line: dns_cloudflare_credentials = /config/dns-conf/cloudflare.ini
  5. For future reference and other users, you don't need to install nano inside the container as you can edit the file on the host under the mapped config folder
  6. Yes, that should work. I believe I had done just that a while back.
  7. It's simple, just use one of the examples from the default site config and plug in your IIS server's IP and port
  8. Stream module is already installed and enabled. I use it to proxy vpn tcp connections
  9. We need more info than "not connecting" Is this a new container or existing? What address are you going to? What is the docker run command?
  10. Update: this was solved on discord. Pihole / dns settings were preventing outgoing connection to letsencrypt servers
  11. RTFM is universal; applies to people of all ages, genders and medical conditions.
  12. Then you enabled http auth in heimdall. Don't enable it in letsencrypt. Doubling up will cause issues.
  13. Or you could have read the instructions in the readme, which talks about renewals. We do not support running manual commands inside the container. You're on your own from this point on
  14. 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.
  15. Host networking doesn't work on the latest unraid. Plenty of posts in this thread if you search. Use bridge networking
  16. 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
  17. 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
  18. https://github.com/linuxserver/docker-openvpn-as/blob/master/README.md#application-setup
  19. Comment out the main location block in the default site config
  20. 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
  21. That's likely the macvlan security feature that blocks connections between host and macvlan containers
  22. 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.
  23. 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).
  24. 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/