tmeuze

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by tmeuze

  1. Hello, I can't seem to get DNS resolution to work once Wireguard comes up. Before it comes up, it can resolve - as the WG endpoint is a hostname. Once connected - nothing. I am using Cryptostorm VPN, if that matters. I've tried various public nameservers in the container config, as well as wg0.conf, to no avail. I'm not sure where to go from here. Any insight would be helpful. Thank you! supervisord.log
  2. Sorry to bother. Are you still having this issue? Do you use a reverse proxy usually? Thinking it was my reverse proxy, I've tried Nginx, NPM, and Caddy, and they all take about 2 minutes per page. EDIT: All is good. Somehow I had the network mode set to bridge, causing this delay.
  3. That's so strange. I have a pretty standard-fare Nginx config. Mind sharing your raw config? I'm not familiar with NPM UI. As @mikel632 said, the linuxserver image doesn't have this issue with the same reverse proxy config. Here's mine
  4. Hi, I'm having this same issue with this particular image. It takes ~2 mins. to display the login page through an Nginx reverse proxy, but is instant when accessing locally. Any ideas?
  5. First post, wanted to share. Made with the My Server plugin in mind.