Jump to content

aptalca

Community Developer
  • Content Count

    2497
  • Joined

  • Last visited

Everything posted by aptalca

  1. When it's officially released as either beta or stable, there will be automatic updates
  2. Code server subdomain config that comes with letsencrypt works with no issues here
  3. 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?
  4. 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.
  5. 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/
  6. 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.
  7. 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
  8. 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
  9. 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
  10. Add this to the bottom of your nginx.conf file, put in your ip and port for openvpn stream { log_format basic '$remote_addr [$time_local] ' '$protocol $status $bytes_sent $bytes_received ' '$session_time'; access_log /config/log/nginx/streamaccess.log basic; error_log /config/log/nginx/streamerror.log; server { listen 80; proxy_pass serverip:port; } }
  11. You likely have double auth, once through htpasswd and once through sonarr/radarr Two solutions: 1) remove internal auth in sonarr/radarr and only rely on http auth, or 2) make sure the user pass are exactly the same for htpasswd and the app's internal auth
  12. GitHub readme and the docker hub pages both have changelogs
  13. Do not manually run commands inside the container. Create a fresh container with an empty appdata folder, follow the directions in the readme
  14. Only the city one is provided by the alpine package, but it contains country info as well
  15. Everything's already installed. You just edit the nginx config to enable it however you like
  16. Did you forward port 53444 on your router to port 53444 on unraid and also map port 53444 to port 53444 in container settings?
  17. Take a step back. What exactly are you trying to achieve? Are you trying to be able to access nextcloud at https://yourdomain.com:53444 ?
  18. Different docker images created by different devs. They are like 2 different operating systems both running plex
  19. The only thing I can think of is that geoip v1 was recently removed as it was deprecated a while back and now the databases are no longer available. If you were using geoip, that will result in a failure. Geoip v2 is included in the image with an up-to-date database. You can use that instead
  20. Don't stop it, keep it running. If you don't want to use the webserver features at all, use dns validation and don't map any ports
  21. Where do you see that log? That doesn't look like the docker log for our image
  22. You should set up a reverse proxy. Look into our letsencrypt image: https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/#nextcloudsubdomainreverseproxyexample
  23. I noticed that, too. Didn't look into it yet, since it seems to work fine after a restart