Replies: 5 comments 8 replies
-
|
Hey Beneix, Have you figured this one out? I am able to get into the web UI with ssh port forward but it is kind of annoying. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
according to https://github.com/haugene/docker-transmission-openvpn/blob/1103172c3288b7de681e2fb7f1378314f17f66cf/openvpn/start.sh#LL313C4-L325C9 |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
In transmission/transmission-home/transmission.log, I can only find these lines, not sure if they tell us anything: |
Beta Was this translation helpful? Give feedback.
-
|
Share the whole log please.. the snippet has nothing to do with local
network
…On Sat, 29 Apr 2023 at 17:58, beneix ***@***.***> wrote:
In transmission/transmission-home/transmission.log, I can only find these
lines, not sure if they tell us anything:
[2023-04-01 19:47:15.628] RPC Server Adding address to whitelist: 127.0.0.1 (/home/buildozer/aports/community/transmission/src/tr
ansmission-3.00/libtransmission/rpc-server.c:956)
[2023-04-01 19:47:15.628] RPC Server Serving RPC and Web requests on 0.0.0.0:9091/transmission/ (/home/buildozer/aports/community
/transmission/src/transmission-3.00/libtransmission/rpc-server.c:1243)
—
Reply to this email directly, view it on GitHub
<#2483 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7OFYXETBYAVPE3PJHPFVDXDTJ3BANCNFSM6AAAAAATRAJIUE>
.
You are receiving this because you commented.Message ID:
<haugene/docker-transmission-openvpn/repo-discussions/2483/comments/5760698
@github.com>
|
Beta Was this translation helpful? Give feedback.
3 replies
-
|
OK, here goes: After that, it's just lines with updates about the torrents. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I need the docker container logs, not transmission logs |
Beta Was this translation helpful? Give feedback.
-
|
Hmmm. Where do I find those? In the main QNAP docker interface, there is just a very summary log that looks like this: QNAP creates a new volume under Container/container-station-data/lib/docker/volumes/ each time you create a new container. Under these, there is just one subdirectory, _data. This only contains openvpn-credentials.txt and transmission-credentials.txt. Any idea where to look for the log file? |
Beta Was this translation helpful? Give feedback.
-
|
Cli command is ‘docker logs <container id > ‘
No idea for qnap
…On Sat, 29 Apr 2023 at 21:43, beneix ***@***.***> wrote:
Hmmm. Where do I find those? In the main QNAP docker interface, there is
just a very summary log that looks like this:
Info 2023/04/29 13:49:00 Container admin Start container (docker, 9dd2bb325ff1, nzbget)
Info 2023/04/29 13:49:00 Container admin Start container (docker, d0386c44a36a, plex)
Info 2023/04/29 13:44:24 Container admin Start container (docker, 1a1084a6a21b, OVPN_Transmission_PIA)
QNAP creates a new volume under
Container/container-station-data/lib/docker/volumes/ each time you create a
new container. Under these, there is just one subdirectory, _data. This
only contains openvpn-credentials.txt and transmission-credentials.txt.
Any idea where to look for the log file?
—
Reply to this email directly, view it on GitHub
<#2483 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7OFYWIA77RRLXMZTKNLDDXDUEIVANCNFSM6AAAAAATRAJIUE>
.
You are receiving this because you commented.Message ID:
<haugene/docker-transmission-openvpn/repo-discussions/2483/comments/5761527
@github.com>
|
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Thanks. In that log, it says: |
Beta Was this translation helpful? Give feedback.
-
|
That looks correct, can you share the rest as well please? Just to confirm it all looks ok |
Beta Was this translation helpful? Give feedback.
-
|
Sure, here is the full log (it does contain some errors but they do not look related to the issue at hand): Thanks for looking at this! |
Beta Was this translation helpful? Give feedback.
-
|
Looks fine to me.. perhaps some docker networking issue
…On Sun, 30 Apr 2023 at 17:34, beneix ***@***.***> wrote:
Sure, here is the full log (it does contain some errors but they do not
look related to the issue at hand):
Starting container with revision: 47f3261
Creating TUN device /dev/net/tun
Using OpenVPN provider: PIA
Provider PIA has a custom setup script, executing it
Downloading OpenVPN config bundle openvpn into temporary file /tmp/tmp.DbkEpb
Extract OpenVPN config bundle into PIA directory /etc/openvpn/pia
Starting OpenVPN using config france.ovpn
Modifying /etc/openvpn/pia/france.ovpn for best behaviour in this container
Setting OpenVPN credentials...
adding route to local network 192.168.2.0/24 via 10.0.3.1 dev eth0
adding route to local network 192.168.5.0/24 via 10.0.3.1 dev eth0
2023-04-29 13:44:26 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning.
2023-04-29 13:44:26 OpenVPN 2.5.2 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on May 4 2021
2023-04-29 13:44:26 library versions: OpenSSL 1.1.1l 24 Aug 2021, LZO 2.10
2023-04-29 13:44:26 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2023-04-29 13:44:26 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL-----
<key excluded>
-----END X509 CRL-----
2023-04-29 13:44:26 TCP/UDP: Preserving recently used remote address: [AF_INET]156.146.63.147:1198
2023-04-29 13:44:26 UDP link local: (not bound)
2023-04-29 13:44:26 UDP link remote: [AF_INET]156.146.63.147:1198
2023-04-29 13:44:26 [paris402] Peer Connection Initiated with [AF_INET]156.146.63.147:1198
2023-04-29 13:44:26 sitnl_send: rtnl: generic error (-101): Network unreachable
2023-04-29 13:44:26 TUN/TAP device tun0 opened
2023-04-29 13:44:26 /sbin/ip link set dev tun0 up mtu 1500
2023-04-29 13:44:26 /sbin/ip link set dev tun0 up
2023-04-29 13:44:26 /sbin/ip addr add dev tun0 10.12.112.170/24
2023-04-29 <http://10.12.112.170/242023-04-29> 13:44:26 /etc/openvpn/tunnelUp.sh tun0 1500 1553 10.12.112.170 255.255.255.0 init
Up script executed with tun0 1500 1553 10.12.112.170 255.255.255.0 init
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.12.112.170
Updating Transmission settings.json with values from env variables
Using existing settings.json for Transmission /data/transmission-home/settings.json
Overriding bind-address-ipv4 because TRANSMISSION_BIND_ADDRESS_IPV4 is set to 10.12.112.170
Overriding blocklist-enabled because TRANSMISSION_BLOCKLIST_ENABLED is set to true
Overriding blocklist-url because TRANSMISSION_BLOCKLIST_URL is set to https://github.com/Naunter/BT_BlockLists/releases/download/master/bt_blocklists.gz
Overriding download-dir because TRANSMISSION_DOWNLOAD_DIR is set to /data/completed
Overriding incomplete-dir because TRANSMISSION_INCOMPLETE_DIR is set to /data/incomplete
Overriding rpc-authentication-required because TRANSMISSION_RPC_AUTHENTICATION_REQUIRED is set to true
Overriding rpc-password because TRANSMISSION_RPC_PASSWORD is set to [REDACTED]
Overriding rpc-port because TRANSMISSION_RPC_PORT is set to 9091
Overriding rpc-username because TRANSMISSION_RPC_USERNAME is set to transmission
Overriding watch-dir because TRANSMISSION_WATCH_DIR is set to /data/watch
sed'ing True to true
-------------------------------------
Transmission will run as
-------------------------------------
User name: root
User uid: 0
User gid: 0
-------------------------------------
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.
2023-04-29 13:44:27 WARNING: OpenVPN was configured to add an IPv6 route. However, no IPv6 has been configured for tun0, therefore the route installation may fail or may not work as expected.
2023-04-29 13:44:27 add_route_ipv6(2000::/3 -> :: metric -1) dev tun0
2023-04-29 13:44:27 ERROR: Linux route -6 add command failed: external program exited with error status: 2
2023-04-29 13:44:27 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2023-04-29 13:44:27 Initialization Sequence Completed
Running functions for token based port fowarding
Sat Apr 29 13:44:37 CEST 2023: getSignature error
{ "status": "ERROR", "message": "Login failed!" }
the has been a fatal_error
Sat Apr 29 13:44:38 CEST 2023: bindPort error
{ "status": "", "message": "bad signature" }
the has been a fatal_error
transmission auth required
waiting for transmission to become responsive
transmission became responsive
2 39% 57.92 MB Unknown 0.0 0.0 8.6 Idle Hampton Hawes - Live at the Montmartre (1971) [Jazz][mp3 320][h33t][schon55]
Sum: 318.7 MB 0.0 0.0
setting transmission port to
localhost:9091/transmission/rpc/ responded: "success"
Checking port...
Error: portTested: http error 400: Bad Request
#######################
SUCCESS
#######################
Port:
Expiration
#######################
Entering infinite while loop
Every 15 minutes, check port status
60 day port reservation reached
Getting a new one
Reserved Port: 30437 Sat Apr 29 13:44:50 CEST 2023
transmission auth required
waiting for transmission to become responsive
transmission became responsive
2 39% 57.92 MB Unknown 0.0 0.0 8.6 Idle Hampton Hawes - Live at the Montmartre (1971) [Jazz][mp3 320][h33t][schon55]
Sum: 318.7 MB 0.0 0.0
setting transmission port to 30437
localhost:9091/transmission/rpc/ responded: "success"
Checking port...
Port is open: Yes
Reserved Port: 30437 Sat Apr 29 14:00:01 CEST 2023
Reserved Port: 30437 Sat Apr 29 14:15:01 CEST 2023
Reserved Port: 30437 Sat Apr 29 14:30:01 CEST 2023
Reserved Port: 30437 Sat Apr 29 14:45:02 CEST 2023
Reserved Port: 30437 Sat Apr 29 15:00:04 CEST 2023
Thanks for looking at this!
—
Reply to this email directly, view it on GitHub
<#2483 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7OFYXRHCXHU4ZX4XYG35LXDYPY7ANCNFSM6AAAAAATRAJIUE>
.
You are receiving this because you commented.Message ID:
<haugene/docker-transmission-openvpn/repo-discussions/2483/comments/5765208
@github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Just to rule things out.. if you either try swapping the subnets around or try ONLY sofortige the 0.5/24 one.. does it still not work? |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My container is running in docker on a QNAP NAS, which is on the 192.168.2.0/24 subnet. I can access the transmission web interface without issues from clients on that subnet. I also have clients on 192.168.5.0/24 but these cannot access the web interface - it just times out.
Clients on the 192.168.5.0/24 subnet can access other services on the QNAP on other ports (e.g. Plex, Unifi Controller), so it does not look like a router/firewall issue.
Is there some configuration setting for transmission that determines which IP addresses it accepts access requests from? I tried setting
LOCAL_NETWORK=192.168.2.0/24,192.168.5.0/24but that didn't work.
Beta Was this translation helpful? Give feedback.
All reactions