KuroSetsuna29

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About KuroSetsuna29

  • Rank
    Newbie
  1. I do have a DoH setup on router to force DNS queries, but it is weird that this is an issue now since I set that up a few weeks ago. And I know I had to restart the delugevpn container since then and it was fine. I can't change it now but I will check later and update here if that is the case. If that is the case, hopefully others that have same setup will see this and my workaround helps them.
  2. It seems to be some kind of DNS issue? Opening the console to the container, I am unable to `ping google.com`: [root@eccca8ca86ff /]# ping google.com ping: google.com: Temporary failure in name resolution However I am able to ping google IP directly. [root@eccca8ca86ff /]# ping 172.217.164.206 PING 172.217.164.206 (172.217.164.206) 56(84) bytes of data. 64 bytes from 172.217.164.206: icmp_seq=1 ttl=117 time=2.75 ms 64 bytes from 172.217.164.206: icmp_seq=2 ttl=117 time=2.85 ms Anyone might know what might be causing this? I tried binhex_privoxyvpn container as well,
  3. Is anyone else having issue trying to use VPN with PIA? The container auto-updated last night, and now I am unable to connect to the WebUI and it seems like it is unable to connect to internet. I tried reinstalling the container fresh, with fresh config and fresh appdata, no help. I also tested my PIA config with OpenVPN client on my computer and it works. With VPN_ENABLED to no, I am able to access WebUI, but obviously no VPN. Config: Logs: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \
  4. Appreciate your effort to look, I was trying to find what was wiping it, but no success. For whatever reason it keeps resetting my /config/qBittorrent/config/qBittorrent.conf to: [BitTorrent] Session\Categories=@Variant(\0\0\0\b\0\0\0\x1\0\0\0\x4\0t\0v\0\0\0\n\0\0\0\0) [Preferences] Connection\PortRangeMin=58495 Queueing\QueueingEnabled=false WebUI\Port=8080 As mentioned before this happens both during power outage AND a docker container update. This is the logs after a simulated power outage (removed any IPs): Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___
  5. I am having the exact same issue. I have seen a couple of other people mention they are also experiencing the same issue but with no resolution. This typically usually happens to me when I lose power or when I update the container. Anyone find the cause or a solution to this?