• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

vast's Achievements


Newbie (1/14)



  1. On another note, I saw PIA recently added Switzerland as a dedicated IP location. So I am considering getting that again. Do you think there would be a way to select this dedicated IP via the ENDPOINT variable?
  2. I see to be having huge issues with speed, dropping to a couple of KB/s. I used to have 25 MB/s. Furthermore, I've gone ahead and set qBit to TCP connections only. Yet, it seems that my speeds are very bad on the PIA network. Not sure what is going on. Maybe it would be interesting to see if you have recommended settings for qBit to use together with PIA.
  3. Oh okay, I think I understood this incorrectly then. The ENDPOINT requires an IP from the vpn provider, not a written string like "Switzerland" or "Netherlands". I just thought since there is a generator that operates that way for PIA, it would be the same here. That should also explain as to why the generator did not work when running it the first time with my PIA credentials.
  4. I was also wondering where can I find the ENDPOINT variable, for the PIA Wireguard config generator, in which config file? I would love to change it to Switzerland instead of the Netherlands.
  5. Somehow it seems that via PIA my Wireguard configuration is not properly obtained. The Address and Public Key is missing in the config file when obtained and therefore the Wireguard instance fails to connect properly. Erroring out on those lines missing. Address = PrivateKey = ************************************* PostUp = '/root/' PostDown = '/root/' [Peer] PublicKey = AllowedIPs = Endpoint = ************************************
  6. So I checked and it seem I only have the issue when trying to run Wireguard, but it works completely fine when running OpenVPN. Obviously Wireguard would be nicer since the performance should be substantially better.
  7. Not sure what you mean by that?!? Host port 3 is set to 8080 as well as the WEBUI_PORT.
  8. I've just finished setting up docker using wireguard and the config provided from my vpn provider. I'm not sure why but I can't connect to the qbit web-ui. I've tried running it in host mode that doesn't seem to work at all. Only bridged mode works. I'm really unsure as to why the web-ui doesn't show up. I tried changing ports etc, and I'm aware that no other app is using that port. Any suggestions? text error warn system array login -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i wg0 -j ACCEPT -A OUTPUT -d <HIDDEN-for-my-PRIVACY>/32 -o eth0 -j ACCEPT -A OUTPUT -s -d -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --sport 8080 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -A OUTPUT -o wg0 -j ACCEPT 2023-02-18 13:58:11,311 DEBG 'start-script' stdout output: -------------------- 2023-02-18 13:58:11,464 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'up'... 2023-02-18 13:58:11,889 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2023-02-18 13:58:11,896 DEBG 'start-script' stderr output: [#] ip link add wg0 type wireguard 2023-02-18 13:58:11,897 DEBG 'start-script' stderr output: [#] wg setconf wg0 /dev/fd/63 2023-02-18 13:58:11,899 DEBG 'start-script' stderr output: [#] ip -4 address add dev wg0 2023-02-18 13:58:11,904 DEBG 'start-script' stderr output: [#] ip link set mtu 1420 up dev wg0 2023-02-18 13:58:11,906 DEBG 'start-script' stderr output: [#] resolvconf -a wg0 -m 0 -x 2023-02-18 13:58:12,141 DEBG 'start-script' stderr output: could not detect a useable init system 2023-02-18 13:58:13,387 DEBG 'start-script' stderr output: [#] wg set wg0 fwmark 51820 2023-02-18 13:58:13,388 DEBG 'start-script' stderr output: [#] ip -4 route add dev wg0 table 51820 2023-02-18 13:58:13,389 DEBG 'start-script' stderr output: [#] ip -4 rule add not fwmark 51820 table 51820 2023-02-18 13:58:13,391 DEBG 'start-script' stderr output: [#] ip -4 rule add table main suppress_prefixlength 0 2023-02-18 13:58:13,393 DEBG 'start-script' stderr output: [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 2023-02-18 13:58:13,497 DEBG 'start-script' stderr output: [#] iptables-restore -n 2023-02-18 13:58:14,184 DEBG 'start-script' stderr output: [#] '/root/' 2023-02-18 13:58:15,562 DEBG 'start-script' stdout output: [info] Attempting to get external IP using ''... 2023-02-18 13:58:19,026 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address <HIDDEN-for-my-PRIVACY> 2023-02-18 13:58:19,027 DEBG 'start-script' stdout output: [info] WireGuard interface 'up' 2023-02-18 13:58:19,038 DEBG 'watchdog-script' stdout output: [info] qBittorrent listening interface IP and VPN provider IP different, marking for reconfigure 2023-02-18 13:58:19,183 DEBG 'start-script' stdout output: [info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment 2023-02-18 13:58:20,306 DEBG 'watchdog-script' stdout output: [info] qBittorrent not running 2023-02-18 13:58:20,500 DEBG 'watchdog-script' stdout output: [info] Removing session lock file (if it exists)... 2023-02-18 13:58:20,508 DEBG 'watchdog-script' stdout output: [info] Attempting to start qBittorrent... 2023-02-18 13:58:24,959 DEBG 'watchdog-script' stdout output: [info] qBittorrent process started [info] Waiting for qBittorrent process to start listening on port 8080... 2023-02-18 13:58:25,559 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8080
  9. Here is a configuration I wrote for SWAG, based on the one @beep wrote previously. I will try to submit it to SWAG as a sample so people can use it in the future! Make sure to edit and your-unraid-lan-ip when using this! ## Version 2022/11/25 # This is a configuration for IBRACORP’s setup of Pterodactyl # It assumes you have the panel configured on port 8001 # It assumes you have the node configured on port 8181 # This will enable a proper connection to Cloudflare # However the SSL security of the connection is not fully granted # This is likely SSL must be enabled for both the panel and then node # from the side of pterodactyl to fully support this. #pterodactyl panel server { listen 80; server_name panel.*; return 301$request_uri; } server { listen 443 ssl http2; server_name panel.*; add_header X-Frame-Options "SAMEORIGIN" always; include /config/nginx/ssl.conf; add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; location / { include /config/nginx/proxy.conf; proxy_pass http://your-unraid-lan-ip:8001; } } #pterodactyl node server { listen 80; server_name node.*; return 301$request_uri; } server { listen 443 ssl http2; server_name node.*; add_header X-Frame-Options "SAMEORIGIN" always; include /config/nginx/ssl.conf; add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; location / { include /config/nginx/proxy.conf; proxy_pass http://your-unraid-lan-ip:8181; } }