Posts by thegameksk

Is it possible to have a staticip when using transmissionVPN? How would I do this?

Quote from KM0201

How do you have the folders mapped in your docker-compose?

Can't explain your download speeds... I have zero issues there. Maybe try a different server. As for it "getting stuck".. no idea on that one.

I got it working. Ty!

Prowlarr log https://pastebin.com/aUz8u69L

Fiaresolverr log https://pastebin.com/1NK90MSs

I installed Flare and its running when I check. It says its ready. I test it in prowlarr index proxies and it says it gives me green checkmark. I put a tag of move in both my flaresolverr indexer and 1337x but it doesnt work. It keeps telling me unable to access blocked by cloudflare protection. Can anyone help?

I also tried getting it to work with Jackett and it tells me the cookies provided are not valid.

Quote from KM0201

Testing the VPN is easy. The container has a built in kill switch, where if it's not connected to the VPN, it simply restarts itself about every 15sec. Easy way to test this, go to your stack, and change your VPN password to something that is obviously wrong.. then redeploy the stack. Watch your container log and you'll see what I'm talking about.

Another easy test.. (the below assumes the rest of your server is not behind a VPN)

1. SSH your server and execute this command. (alternatively, you could use one of your network machines that is not behind a VPN, and go to whatismyip.com to get your public IP)

Code

host myip.opendns.com resolver1.opendns.com

Again, assuming the rest of your server is not behind the VPN, this will return your public IP.

2. Now, execute the following command (again, this assumes the container is named transvpn).

Code

docker exec -it transvpn host myip.opendns.com resolver1.opendns.com

That will return the public IP address for the container. If they are different, then the VPN is working.

Code

root@openmediavault:~# host myip.opendns.com resolver1.opendns.com
Using domain server:
Name: resolver1.opendns.com
Address: 208.67.222.222#53
Aliases: 

myip.opendns.com has address 73.146.xxx.xxx

root@openmediavault:~# docker exec -it transvpn host myip.opendns.com resolver1.opendns.com
Using domain server:
Name: resolver1.opendns.com
Address: 208.67.222.222#53
Aliases: 

myip.opendns.com has address 102.129.xxx.xxx
root@openmediavault:~# 

Display More

Obviously my server has a different public IP than my container, so the VPN is working.

As for your seeding question can't really answer that. You could try messing with your volume paths a bit, but I always had permission issues with that container when I moved away from the what is more or less default.

edit: There is still something wrong. I can download somethings but other with lots of seeds from different site wont dl and my speed is really bad. 1 mb if im lucky.

Display More

Its confusing. Even the folder Have pointed to store finished downloads isnt being used. Instead its going to /data/completed when it should go to downloads

Edit: There is still an issue I cna only dl somethings. Even things with lots of seeds will get stuck and not dl also my speed is slow like 1 mb.

Quote from KM0201

Code

version: '2.1'
services:
 transmission-openvpn:
    container_name: transvpn
    volumes:
        - /NAS/Torrents/:/data
    environment:
        - PUID=1000
        - PGID=100
        - CREATE_TUN_DEVICE=true
        - OPENVPN_PROVIDER=PIA
        - PIA_OPENVPN_CONFIG_BUNDLE=openvpn
        - OPENVPN_CONFIG=us_florida
        - OPENVPN_USERNAME=
        - OPENVPN_PASSWORD=
        - DISABLE_PORT_UPDATER=true
        - TRANSMISSION_WEB_UI=transmission-web-control
        - OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60
        - WEBPROXY_ENABLED=false
        - LOCAL_NETWORK=192.168.1.0/24
    cap_add:
        - NET_ADMIN
    logging:
        driver: json-file
        options:
            max-size: 10m
    ports:
        - 9091:9091
    restart: always
    image: haugene/transmission-openvpn

Display More

Try deleting your old container, and adding this to your stacks and deploy it. Only thing you should need to adjust is your PIA username/password, your /data volume, and the server you want to use (this one is using us_florida)

For a full list of the servers available for PIA in this container...

1. Bash into the container (below assumes your transmission container is named "transvpn" as I did in that stack)

Code

docker exec -it transvpn bash

2. Once bashed in

Code

cd /etc/openvpn/pia

3. Then use ls and you'll see all the PIA servers included with this container.

Display More

I did the stack and it says healthy but not running. I had the /data set to my old transmissionvpn folder so my unfinished downloads would finish but for some reason it made a completely new transmission folder. Here is what it says in logs

https://pastebin.com/eCAGSJjS

edit: its working based off the fl vpn. I can download but hopefully im protected by my vpn lol. How can I get it to use my old folder? Now I have my original downloads completed and incomplete folder and my old one. I want to be able to use the old folders to finish pending downloads and to know what ive already downloaded.

Quote from KM0201

the easiest way to do it... is create a codebox (like you did there)

and then paste the compose in side a codebox

or you can put it in a pastebin at pastebin.com, and give me the link. whatever works for you..

just make sure you remove your PIA password and username whichever you do.

Display More

https://pastebin.com/gxYWgVc0

Quote from KM0201

can you post your stack? Remove your PIA username and password from the stack

  Been a while since ive done this. Whats the best way to post? Copy and paste seems to make a mess because its a whole lot of  text.

It was working fine. Turned off my NAS while away on vacation and now I cant download. Everything stays on magnitized downloads but I am able to seed. Heres my logs:

Modification: Remap SIGUSR1 signal to SIGTERM, avoid OpenVPN restart loop

Setting OpenVPN credentials...

adding route to local network 192.168.1.0/24 via 172.18.0.1 dev eth0

Fri Sep 2 23:34:48 2022 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 22 2022

Fri Sep 2 23:34:48 2022 library versions: OpenSSL 1.1.1f 31 Mar 2020, LZO 2.10

Fri Sep 2 23:34:48 2022 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

Fri Sep 2 23:34:48 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]179.61.228.51:1198

Fri Sep 2 23:34:48 2022 Socket Buffers: R=[212992->212992] S=[212992->212992]

Fri Sep 2 23:34:48 2022 UDP link local: (not bound)

Fri Sep 2 23:34:48 2022 UDP link remote: [AF_INET]179.61.228.51:1198

Fri Sep 2 23:34:48 2022 TLS: Initial packet from [AF_INET]179.61.228.51:1198, sid=3222d396 fb73ff59

Fri Sep 2 23:34:48 2022 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

Fri Sep 2 23:34:48 2022 VERIFY OK: depth=1, C=US, ST=CA, L=LosAngeles, O=Private Internet Access, OU=Private Internet Access, CN=Private Internet Access, name=Private Internet Access, emailAddress=secure@privateinternetaccess.com

Fri Sep 2 23:34:48 2022 VERIFY KU OK

Fri Sep 2 23:34:48 2022 Validating certificate extended key usage

Fri Sep 2 23:34:48 2022 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication

Fri Sep 2 23:34:48 2022 VERIFY EKU OK

Fri Sep 2 23:34:48 2022 VERIFY OK: depth=0, C=US, ST=CA, L=LosAngeles, O=Private Internet Access, OU=Private Internet Access, CN=perth403, name=perth403

Fri Sep 2 23:34:49 2022 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 2048 bit RSA

Fri Sep 2 23:34:49 2022 [perth403] Peer Connection Initiated with [AF_INET]179.61.228.51:1198

Fri Sep 2 23:34:50 2022 SENT CONTROL [perth403]: 'PUSH_REQUEST' (status=1)

Fri Sep 2 23:34:50 2022 PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway def1,route-ipv6 2000::/3,dhcp-option DNS 10.0.0.243,route-gateway 10.50.112.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.50.112.127 255.255.255.0,peer-id 1,cipher AES-128-GCM'

Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: timers and/or timeouts modified

Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: compression parms modified

Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: --ifconfig/up options modified

Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: route options modified

Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: route-related options modified

Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified

Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: peer-id set

Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: adjusting link_mtu to 1625

Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: data channel crypto options modified

Fri Sep 2 23:34:50 2022 Data Channel: using negotiated cipher 'AES-128-GCM'

Fri Sep 2 23:34:50 2022 Outgoing Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key

Fri Sep 2 23:34:50 2022 Incoming Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key

Fri Sep 2 23:34:50 2022 ROUTE_GATEWAY 172.18.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:12:00:02

Fri Sep 2 23:34:50 2022 GDG6: remote_host_ipv6=n/a

Fri Sep 2 23:34:50 2022 ROUTE6: default_gateway=UNDEF

Fri Sep 2 23:34:50 2022 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options

Fri Sep 2 23:34:50 2022 OpenVPN ROUTE: failed to parse/resolve route for host/network: 2000::/3

Fri Sep 2 23:34:50 2022 TUN/TAP device tun0 opened

Fri Sep 2 23:34:50 2022 TUN/TAP TX queue length set to 100

Fri Sep 2 23:34:50 2022 /sbin/ip link set dev tun0 up mtu 1500

Fri Sep 2 23:34:50 2022 /sbin/ip addr add dev tun0 10.50.112.127/24 broadcast 10.50.112.255

Fri Sep 2 23:34:50 2022 /etc/openvpn/tunnelUp.sh tun0 1500 1553 10.50.112.127 255.255.255.0 init

Up script executed with tun0 1500 1553 10.50.112.127 255.255.255.0 init

Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.50.112.127

Updating Transmission settings.json with values from env variables

Using existing settings.json for Transmission /config/settings.json

Overriding bind-address-ipv4 because TRANSMISSION_BIND_ADDRESS_IPV4 is set to 10.50.112.127

Overriding download-dir because TRANSMISSION_DOWNLOAD_DIR is set to /storage/downloads/completed

Overriding incomplete-dir because TRANSMISSION_INCOMPLETE_DIR is set to /storage/downloads/incomplete

Overriding rpc-port because TRANSMISSION_RPC_PORT is set to 9091

Overriding watch-dir because TRANSMISSION_WATCH_DIR is set to /storage/downloads/watch

sed'ing True to true

Enforcing ownership on transmission config directories

Applying permissions to transmission config directories

Setting owner for transmission paths to 1000:100

Setting permissions for download and incomplete directories

2

Directories: 775

Files: 664

Setting permission for watch directory (775) and its files (664)

-------------------------------------

Transmission will run as

-------------------------------------

User name: abc

User uid: 1000

User gid: 100

-------------------------------------

STARTING TRANSMISSION

Provider PIA has a script for automatic port forwarding. Will run it now.

If you want to disable this, set environment variable DISABLE_PORT_UPDATER=true

Transmission startup script complete.

Fri Sep 2 23:35:22 2022 /sbin/ip route add 179.61.228.51/32 via 172.18.0.1

Fri Sep 2 23:35:22 2022 /sbin/ip route add 0.0.0.0/1 via 10.50.112.1

Fri Sep 2 23:35:22 2022 /sbin/ip route add 128.0.0.0/1 via 10.50.112.1

Fri Sep 2 23:35:22 2022 WARNING: OpenVPN was configured to add an IPv6 route over tun0. However, no IPv6 has been configured for this interface, therefore the route installation may fail or may not work as expected.

Fri Sep 2 23:35:22 2022 Initialization Sequence Completed

Running functions for token based port fowarding

Reserved Port: 44075 Fri Sep 2 23:35:31 CDT 2022

transmission auth not required

waiting for transmission to become responsive

transmission became responsive

3282* 100% 3.51 GB Done 0.0 0.0 0.0 Stopped Becky (2020) (1080p BluRay x265 HEVC 10bit AAC 5.1 Tigole)

Sum: 16.62 TB 0.0 0.0

setting transmission port to 44075

localhost:9091/transmission/rpc/ responded: "success"

Checking port...

Port is open: Yes

#######################

SUCCESS

#######################

Port: 44075

Expiration Fri Nov 4 11:20:13 CDT 2022

#######################

Entering infinite while loop

Every 15 minutes, check port status

Reserved Port: 44075 Fri Sep 2 23:51:01 CDT 2022

Quote from Soma

KM0201

It seems that the container's last commit, changed the behaviour of cron (inside the container)

update cron times, clean up scripts · linuxserver/docker-duckdns@4b1e602 (github.com)

thegameksk

If you just want to stop seeing the constant IP update on the logs, add this environment to the DUCKDNS yml/stack:

Code

LOG_FILE=false

The stack will look like this:

Code

---
version: "2.1"
services:
  duckdns:
    image: lscr.io/linuxserver/duckdns
    container_name: duckdns
    environment:
      - PUID=1000 #optional
      - PGID=1000 #optional
      - TZ=Europe/London
      - SUBDOMAINS=subdomain1,subdomain2
      - TOKEN=token
      - LOG_FILE=false # This will stop the constant showing of the IP update
    volumes:
      - /path/to/appdata/config:/config #optional
    restart: unless-stopped

Display More

Display More

Thank you I will do that when I get home.

Its just weird how its random. Yes as you pointed out yesterday was every 5 minutes. The day before for it would be all over the map in terms of getting that message.

Quote from KM0201

How often is it saying this? What are the timestamps on the duckdns log?

It can range from second to minutes or hours. Here is an example of the logs:

 -1 }">2022-03-01T12:52:00.410943511Z Your IP was updated at Tue Mar  1 12:52:00 New 2022
 -1 }">2022-03-01T12:57:00.407314801Z Your IP was updated at Tue Mar  1 12:57:00 New 2022
 -1 }">2022-03-01T13:02:00.408443657Z Your IP was updated at Tue Mar  1 13:02:00 New 2022
 -1 }">2022-03-01T13:07:00.440618122Z Your IP was updated at Tue Mar  1 13:07:00 New 2022
 -1 }">2022-03-01T13:12:00.538653781Z Your IP was updated at Tue Mar  1 13:12:00 New 2022
 -1 }">2022-03-01T13:17:00.497604396Z Your IP was updated at Tue Mar  1 13:17:00 New 2022
 -1 }">2022-03-01T13:22:00.433548755Z Your IP was updated at Tue Mar  1 13:22:00 New 2022
 -1 }">2022-03-01T13:27:00.383057940Z Your IP was updated at Tue Mar  1 13:27:00 New 2022
 -1 }">2022-03-01T13:32:00.423378190Z Your IP was updated at Tue Mar  1 13:32:00 New 2022
 -1 }">2022-03-01T13:37:00.704207530Z Your IP was updated at Tue Mar  1 13:37:00 New 2022
 -1 }">2022-03-01T13:42:00.447414898Z Your IP was updated at Tue Mar  1 13:42:00 New 2022
 -1 }">2022-03-01T13:47:00.458787246Z Your IP was updated at Tue Mar  1 13:47:00 New 2022
 -1 }">2022-03-01T13:52:00.444740691Z Your IP was updated at Tue Mar  1 13:52:00 New 2022
 -1 }">2022-03-01T13:57:00.919942521Z Your IP was updated at Tue Mar  1 13:57:00 New 2022
 -1 }">2022-03-01T14:02:00.621766114Z Your IP was updated at Tue Mar  1 14:02:00 New 2022
 -1 }">2022-03-01T14:07:00.460942429Z Your IP was updated at Tue Mar  1 14:07:00 New 2022
 -1 }">2022-03-01T14:12:00.589373214Z Your IP was updated at Tue Mar  1 14:12:00 New 2022
 -1 }">2022-03-01T14:17:00.480306874Z Your IP was updated at Tue Mar  1 14:17:00 New 2022
 -1 }">2022-03-01T14:22:00.499991020Z Your IP was updated at Tue Mar  1 14:22:00 New 2022
 -1 }">2022-03-01T14:27:00.437403545Z Your IP was updated at Tue Mar  1 14:27:00 New 2022
 -1 }">2022-03-01T14:32:00.572580658Z Your IP was updated at Tue Mar  1 14:32:00 New 2022
 -1 }">2022-03-01T14:37:00.465217759Z Your IP was updated at Tue Mar  1 14:37:00 New 2022
 -1 }">2022-03-01T14:42:01.000214207Z Your IP was updated at Tue Mar  1 14:42:00 New 2022
 -1 }">2022-03-01T14:47:00.520508454Z Your IP was updated at Tue Mar  1 14:47:00 New 2022
 -1 }">2022-03-01T14:52:00.560941814Z Your IP was updated at Tue Mar  1 14:52:00 New 2022
 -1 }">2022-03-01T14:57:00.544258264Z Your IP was updated at Tue Mar  1 14:57:00 New 2022
 -1 }">2022-03-01T15:02:00.731163285Z Your IP was updated at Tue Mar  1 15:02:00 New 2022
 -1 }">2022-03-01T15:07:00.609135382Z Your IP was updated at Tue Mar  1 15:07:00 New 2022
 -1 }">2022-03-01T15:12:00.586808874Z Your IP was updated at Tue Mar  1 15:12:00 New 2022
 -1 }">2022-03-01T15:17:00.559471976Z Your IP was updated at Tue Mar  1 15:17:00 New 2022
 -1 }">2022-03-01T15:22:00.565504621Z Your IP was updated at Tue Mar  1 15:22:00 New 2022
 -1 }">2022-03-01T15:27:00.799475857Z Your IP was updated at Tue Mar  1 15:27:00 New 2022
 -1 }">2022-03-01T15:32:00.561448475Z Your IP was updated at Tue Mar  1 15:32:00 New 2022
 -1 }">2022-03-01T15:37:00.698690184Z Your IP was updated at Tue Mar  1 15:37:00 New 2022
 -1 }">2022-03-01T15:42:00.573329305Z Your IP was updated at Tue Mar  1 15:42:00 New 2022
 -1 }">2022-03-01T15:47:00.587846759Z Your IP was updated at Tue Mar  1 15:47:00 New 2022
 -1 }">2022-03-01T15:52:00.548637930Z Your IP was updated at Tue Mar  1 15:52:00 New 2022
 -1 }">2022-03-01T15:57:00.587001497Z Your IP was updated at Tue Mar  1 15:57:00 New 2022
 -1 }">2022-03-01T16:02:00.651278514Z Your IP was updated at Tue Mar  1 16:02:00 New 2022
 -1 }">2022-03-01T16:07:00.564115462Z Your IP was updated at Tue Mar  1 16:07:00 New 2022
 -1 }">2022-03-01T16:12:00.736902350Z Your IP was updated at Tue Mar  1 16:12:00 New 2022
 -1 }">2022-03-01T16:17:00.724206299Z Your IP was updated at Tue Mar  1 16:17:00 New 2022
 -1 }">2022-03-01T16:22:01.924036609Z Your IP was updated at Tue Mar  1 16:22:01 New 2022
 -1 }">2022-03-01T16:27:00.578996818Z Your IP was updated at Tue Mar  1 16:27:00 New 2022
 -1 }">2022-03-01T16:32:00.536544733Z Your IP was updated at Tue Mar  1 16:32:00 New 2022
 -1 }">2022-03-01T16:37:00.624981659Z Your IP was updated at Tue Mar  1 16:37:00 New 2022
 -1 }">2022-03-01T16:42:00.556750787Z Your IP was updated at Tue Mar  1 16:42:00 New 2022
 -1 }">2022-03-01T16:47:00.672099004Z Your IP was updated at Tue Mar  1 16:47:00 New 2022
 -1 }">2022-03-01T16:52:00.580244134Z Your IP was updated at Tue Mar  1 16:52:00 New 2022
 -1 }">2022-03-01T16:57:00.786299799Z Your IP was updated at Tue Mar  1 16:57:00 New 2022
 -1 }">2022-03-01T17:02:00.586957324Z Your IP was updated at Tue Mar  1 17:02:00 New 2022
 -1 }">2022-03-01T17:07:00.699085771Z Your IP was updated at Tue Mar  1 17:07:00 New 2022
 -1 }">2022-03-01T17:12:00.717337878Z Your IP was updated at Tue Mar  1 17:12:00 New 2022
 -1 }">2022-03-01T17:17:00.618373833Z Your IP was updated at Tue Mar  1 17:17:00 New 2022
 -1 }">2022-03-01T17:22:00.759624589Z Your IP was updated at Tue Mar  1 17:22:00 New 2022
 -1 }">2022-03-01T17:27:00.753689633Z Your IP was updated at Tue Mar  1 17:27:00 New 2022
 -1 }">2022-03-01T17:32:00.808284308Z Your IP was updated at Tue Mar  1 17:32:00 New 2022
 -1 }">2022-03-01T17:37:00.786665334Z Your IP was updated at Tue Mar  1 17:37:00 New 2022
 -1 }">2022-03-01T17:42:00.809556310Z Your IP was updated at Tue Mar  1 17:42:00 New 2022
 -1 }">2022-03-01T17:47:00.788036487Z Your IP was updated at Tue Mar  1 17:47:00 New 2022
 -1 }">2022-03-01T17:52:00.804533909Z Your IP was updated at Tue Mar  1 17:52:00 New 2022
 -1 }">2022-03-01T17:57:00.748620703Z Your IP was updated at Tue Mar  1 17:57:00 New 2022
 -1 }">2022-03-01T18:02:00.923255294Z Your IP was updated at Tue Mar  1 18:02:00 New 2022
 -1 }">2022-03-01T18:07:00.782941202Z Your IP was updated at Tue Mar  1 18:07:00 New 2022
 -1 }">2022-03-01T18:12:00.744409739Z Your IP was updated at Tue Mar  1 18:12:00 New 2022
 -1 }">2022-03-01T18:17:00.706217553Z Your IP was updated at Tue Mar  1 18:17:00 New 2022
 -1 }">2022-03-01T18:22:00.814913853Z Your IP was updated at Tue Mar  1 18:22:00 New 2022
 -1 }">2022-03-01T18:27:00.719203325Z Your IP was updated at Tue Mar  1 18:27:00 New 2022
 -1 }">2022-03-01T18:32:00.846186870Z Your IP was updated at Tue Mar  1 18:32:00 New 2022
 -1 }">2022-03-01T18:37:00.757072916Z Your IP was updated at Tue Mar  1 18:37:00 New 2022
 -1 }">2022-03-01T18:42:00.741061863Z Your IP was updated at Tue Mar  1 18:42:00 New 2022
 -1 }">2022-03-01T18:47:00.793639224Z Your IP was updated at Tue Mar  1 18:47:00 New 2022
 -1 }">2022-03-01T18:52:00.679303853Z Your IP was updated at Tue Mar  1 18:52:00 New 2022
 -1 }">2022-03-01T18:57:00.966688950Z Your IP was updated at Tue Mar  1 18:57:00 New 2022
 -1 }">2022-03-01T19:02:00.798919614Z Your IP was updated at Tue Mar  1 19:02:00 New 2022
 -1 }">2022-03-01T19:07:00.842389187Z Your IP was updated at Tue Mar  1 19:07:00 New 2022
 -1 }">2022-03-01T19:12:00.941985736Z Your IP was updated at Tue Mar  1 19:12:00 New 2022
 -1 }">2022-03-01T19:17:00.771002530Z Your IP was updated at Tue Mar  1 19:17:00 New 2022
 -1 }">2022-03-01T19:22:00.971753447Z Your IP was updated at Tue Mar  1 19:22:00 New 2022
 -1 }">2022-03-01T19:27:00.863685083Z Your IP was updated at Tue Mar  1 19:27:00 New 2022
 -1 }">2022-03-01T19:32:01.009272762Z Your IP was updated at Tue Mar  1 19:32:01 New 2022
 -1 }">2022-03-01T19:37:01.045000106Z Your IP was updated at Tue Mar  1 19:37:01 New 2022
 -1 }">2022-03-01T19:42:01.084436153Z Your IP was updated at Tue Mar  1 19:42:01 New 2022
 -1 }">2022-03-01T19:47:00.908456901Z Your IP was updated at Tue Mar  1 19:47:00 New 2022
 -1 }">2022-03-01T19:52:01.021944645Z Your IP was updated at Tue Mar  1 19:52:01 New 2022
 -1 }">2022-03-01T19:57:02.131448120Z Your IP was updated at Tue Mar  1 19:57:02 New 2022
 -1 }">2022-03-01T20:02:02.292861135Z Your IP was updated at Tue Mar  1 20:02:02 New 2022
 -1 }">2022-03-01T20:07:01.323071020Z Your IP was updated at Tue Mar  1 20:07:01 New 2022
 -1 }">2022-03-01T20:12:01.138004773Z Your IP was updated at Tue Mar  1 20:12:01 New 2022
 -1 }">2022-03-01T20:17:01.143471286Z Your IP was updated at Tue Mar  1 20:17:01 New 2022
 -1 }">2022-03-01T20:22:01.201517771Z Your IP was updated at Tue Mar  1 20:22:01 New 2022
 -1 }">2022-03-01T20:27:01.332283938Z Your IP was updated at Tue Mar  1 20:27:01 New 2022
 -1 }">2022-03-01T20:32:01.351127494Z Your IP was updated at Tue Mar  1 20:32:01 New 2022
 -1 }">2022-03-01T20:37:02.255309920Z Your IP was updated at Tue Mar  1 20:37:02 New 2022
 -1 }">2022-03-01T20:42:01.531933057Z Your IP was updated at Tue Mar  1 20:42:01 New 2022
 -1 }">2022-03-01T20:47:01.247911157Z Your IP was updated at Tue Mar  1 20:47:01 New 2022
 -1 }">2022-03-01T20:52:01.359450453Z Your IP was updated at Tue Mar  1 20:52:01 New 2022
 -1 }">2022-03-01T20:57:00.975274219Z Your IP was updated at Tue Mar  1 20:57:00 New 2022
 -1 }">2022-03-01T21:02:01.021220294Z Your IP was updated at Tue Mar  1 21:02:01 New 2022
 -1 }">2022-03-01T21:07:01.147554061Z Your IP was updated at Tue Mar  1 21:07:01 New 2022

Quote from Soma

How is the IP beeing updated?

Duckdns YML?

Or some other way?

Thats what I dont know. The only VPN container I have is TransmissionVPN which was the first thing I setup with KM0201's help. It doesnt affect any other containers. In duckdns it has my correct IP in duckdns homepage and its not changing on the homepage but the logs keeps saying "ip was updated"

Quote from KM0201

One last thing...

Look at your log, does it show the specific IP's involved? Are the IP's consistent (ie it's always jumping between 1.2.3.4 and 5.6.7.8) or do the numbers seem totally random?

If they are constantly the same IP address, then it would suggest there is a configuration issue somewhere (where I have no idea, I've pulled certs 100's of times and never had this issue). If they are random... I have no idea what the hell that would mean

The logs dont show the IP. It just says "Your IP was updated at Tue Mar 1 14:02:00 New 2022" over and over again.

Quote from KM0201

That is weird.

Do you by chance have airsonic and transmission in the same stack?

No and after an hr it went back to "ip address has updated" messages every few minutes again.

Quote from KM0201

I honestly don't know.. never seen this problem.

My good luck continues lol. Im doing an experiment while at work tonight. I turned off the transmission vpn container. Its been 20 minutes and so far the IP updated message hasnt appeared in duckdns log.

Quote from KM0201

It shouldn't, unless you're trying to route airsonic through the VPN as well.. or trying to route transmission through swag. I could see this happening if you're doing that... It picks up the VPN for transmission, changes it, then the duckdns container immediately changes it back as it's not being the VPN

Nope I havent touched the transmission container since we set it up back then. How do I go about fixing this?

Quote from KM0201

That doesn't really matter. If you check your duckdns account while behind the vpn of a client, if is going to auto update with the public IP of the client (which is the vpn IP, and would explain this whole problem)

Do you have linuxserver/duckdns container installed? It will auto update your duckdns domain with your public IP. IF YOUR WHOLE SERVER is behind the VPN, it's going to send the wrong IP to your duckdns account

I didnt check the duckdns account while on my VPN of my PC. Its so strange watching literally every few minutes the log in linuxserver/duckdns constantly say IP updated every few minutes while on my PC the VPN is not on. We did set up a VPN for transmission on the server. Could that do this? Yes linuxserver/duckdns container is installed on my Server.

Quote from KM0201

Something isn't right here.. especially with duckdns logs showing your IP changing constantly. Is your laptop/client computer behind a VPN, when you check your duckdns account?

Try this...

SSH your server... and execute the following the command

Code

host myip.opendns.com resolver1.opendns.com

You should get an output something like this...

It should give you an output something like this

Code

ken@openmediavault:~$ host myip.opendns.com resolver1.opendns.com
Using domain server:
Name: resolver1.opendns.com
Address: 208.67.222.222#53
Aliases: 

myip.opendns.com has address YOUR.IP.HERE
ken@openmediavault:~$ 

Does that IP address (where I put YOUR.IP.HERE) match your client machine (whatismyip.com) and what is in duckdns?

Display More

Just saw this. No it doesnt match. It only shows an IPV6 address. I do sometimes us a VPN but when I turn it off I restart my pc. I used it last week and now im getting the IP address changing constantly message. Swag is running according to my logs and its up. DuckDNS is the issue.

Quote from Soma

But you are doing it while on the same router? Or you try it with, for eg. the Phone on Mobile data?

Ive tried both.

Quote from Soma

Are you trying to connect on the same network? I mean, the device you're using to log onto the Server is using the same router?

And I can reach your airsonic login page without issues so your server is running properly.

Yes. I can get to my subsonic page on subsonic. It works fine if im home on my wifi. When I try to connect via duckDNS is when it doesnt work using airsonic.domian.duckdns.org. I have the correct domain name set in subsonic and also on my PC if I try to connect to airsonic.domian.duckdns.org with the correct domain name it gives me connection time out error.

Quote from Soma

Please, edit your post and ommit sensible data.

Also delete the txt for the same reasons.

I can see your SWAG park page secured, What is the issue?

Subsonic wont connect. It keeps giving me network error. Please check the server address or try again later