aptalca

Community Developer
 View Profile  See their activity

  • Posts

    3064

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Everything posted by aptalca

  1. aptalca
    It looks like you're trying to proxy /web through the root domain, and also /web through subfolder /data or /wss and you only added the websocket bits to the /data or /wss subfolder. Does the app actually serve the websockets at subfolder /data or /wss? From the error message, it looks like it doesn't
  2. aptalca
    See how we handle websocket proxy for unifi, these two lines are key: https://github.com/linuxserver/docker-letsencrypt/blob/master/root/defaults/proxy-confs/unifi.subdomain.conf.sample#L46-L47
  3. aptalca
    What are you trying to proxy?
  4. aptalca
    If a docker container has its own ip, the connection between that and the host will be blocked. That's a security feature of macvlan
  5. aptalca
    ?? Working just fine over here, no spikes
  6. aptalca
    Macvlan prevents access to host so your pihole won't be able to connect to your unraid host or any containers running in bridge or host mode (or vice versa)
  7. aptalca
    You can map that file in your container settings, similar to mapping a folder
  8. aptalca
    It doesn't need api keys or password, just the address
  9. aptalca
    Follow the container info on either github or docker hub. All you need is in there
  10. aptalca
    Plex has been having issues with remote access for a while. See their forum, it's full of similar complaints. I reverse proxy plex and have no issues
  11. aptalca
    We need more info on your setup. Describe where and how you're running the container (friend's or yours?) and how you're trying to access. Also post your site config that's giving you issues
  12. aptalca
    Did you enable the preset proxy confs? Did you create the new network as described in the readme in the proxy conf folder?
  13. aptalca
    I would put a different router in there to be honest. Different port should work unless you have incorrect redirects in your site config files
  14. aptalca
    I don't know why or where you're using an .htaccess file but that's likely your issue. You need to pass ports 443 and 80 to the letsencrypt container unaltered. Browser thing is just a cache issue. 301 redirects are permanently cached
  15. aptalca
    Based on the error, it seems your port 80 is not correctly forwarded by your router to this container
  16. aptalca
    Post your container log and the container settings
  17. aptalca
    Don't do host networking
  18. aptalca
    Post your container settings
  19. aptalca
    Php is enabled by default. Make sure your php block is still enabled in your default site config
  20. aptalca
    Nginx reverse proxy is the right way for that. Check out the letsencrypt image. It works with duckdns
  21. aptalca
    Ah, gotcha. Will do
  22. aptalca
    If you want your containers to be able to connect to each other using container names as hostnames, then the user defined bridge network works great. Letsencrypt takes advantage of this to standardize proxy configs by using container names instead of IPs
  23. aptalca
    I believe this is a bug. The feature was already requested and it was added. The "user defined bridge" networks are already listed in the gui as a network option. The bug is that when a user defined network is selected, the "add port" screen does not allow for entering in the "container port". See below screenshot.
  24. aptalca
    Bump
  25. aptalca
    When you set edge to 1, it will update during container start. But their download server is unreliable and sometimes it takes a long time to download the update. During which time, the web gui won't be up. Watch the logs to see what's going on. Once updated, going back may break things due to calibre database having been updated