Jump to content

gray-pouch1731

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by gray-pouch1731

  1. Just wanted to update, I solved the problem!! Turns out something was up with my wg0.conf file. I regenerated the configuration from my VPN (AirVPN), and the endpoint had changed on me. My wg0.conf file has a bunch of extra Synology stuff going on in it, ( I think I followed this guide a couple months ago), but long story short I just had to update the endpoint. Just in case anyone else ends up here with a Synology device and is using AirVPN, make sure to change the endpoint they provide with their generated config into an ip address (I used nslookup). Thanks again for your attention!
  2. Thanks for getting back to me! Really appreciate it. I thought the same about the permissions issues, but as far as I can tell the permissions are properly configured- everything inside my /config belongs to the docker user/their group and I'm running with privileged: true. My name servers were also set to the values you've mentioned here. The lines that stick out to me from my supervisord.log file are a bunch of: qbit-vpn | sed: cannot rename /config/wireguard/sedYuVf6t: Device or resource busy qbit-vpn | qbit-vpn | qbit-vpn | 2023-10-24 12:00:34,626 DEBG 'start-script' stderr output: qbit-vpn | sed: cannot rename /config/wireguard/sedhqJ868: Device or resource busy qbit-vpn | qbit-vpn | qbit-vpn | 2023-10-24 12:00:34,630 DEBG 'start-script' stderr output: qbit-vpn | sed: cannot rename /config/wireguard/sedRTHJaC: Device or resource busy qbit-vpn | qbit-vpn | qbit-vpn | 2023-10-24 12:00:34,634 DEBG 'start-script' stderr output: qbit-vpn | sed: cannot rename /config/wireguard/sedxYdLDW: Device or resource busy In case this helps, I'm running the container on Synology DSM 7.2 through docker compose. I can paste my compose file if that helps at all! I also tried downgrading to no success 😕
  3. Hi Binhex and friends! I'm stumped, not sure where to go from here. My container was running perfectly (for at least a few months), but all of a sudden stopped uploading and downloading. I suspect it has something to do with these lines in my supervisord.log but I'm not totally sure: 2023-10-23 20:06:01,252 DEBG 'start-script' stderr output: could not detect a useable init system Afterwards I see several "Operation not permitted" errors. 2023-10-23 20:28:37,682 DEBG 'start-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... 2023-10-23 20:28:37,687 DEBG 'watchdog-script' stderr output: touch: cannot touch '/tmp/dnsfailure': Permission denied 2023-10-23 20:28:37,688 DEBG 'watchdog-script' stderr output: chmod: changing permissions of '/tmp/dnsfailure': Operation not permitted 2023-10-23 20:28:37,705 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2023-10-23 20:28:47,992 DEBG 'start-script' stdout output: [info] Failed on last attempt, attempting to get external IP using 'http://whatismyip.akamai.com'... Any idea what might be happening? Here is my supervisord.log file in case that helps- if this isn't something I should be posting to the internet please let me know so I can remove it hehe.
×
×
  • Create New...