You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The transmission-openvpn script is ready for testing: bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/transmission-openvpn.sh)"
This application requires a VPN provider to work. Please refer to your VPN provider’s documentation for setting up OpenVPN.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Hi,
It’s been about three weeks and no one has tested this image yet. As I’m the developer, I’d be happy to help if needed or would you prefer to keep development and testing independent?
Hmmm i ran the install and the access interface port of 9091 dosent seems to show anything
So maybe theres a problem with transmission web ui starting?
Hmmm i ran the install and the access interface port of 9091 dosent seems to show anything
So maybe theres a problem with transmission web ui starting?
Hi DragoQC,
Thank you for helping test this script. From my point of view, as long as OpenVPN cannot reach your VPN provider, this behavior is expected. The application blocks all network traffic as part of its kill-switch mechanism.
I can help you set up your OpenVPN configuration. Do you already have a VPN provider, and if so, which one are you using?
If you don’t have a VPN provider, we can also set up your own VPN server using the community OpenVPN script, and then configure transmission-vpn to use it as the VPN provider.
Could you send me the logs after running the following command?
root@transmission-openvpn:# systemctl status openvpn-custom.service
○ openvpn-custom.service - Custom OpenVPN start service
Loaded: loaded (/etc/systemd/system/openvpn-custom.service; enabled; preset: enabled)
Active: inactive (dead) since Sat 2025-11-29 23:56:04 EST; 45s ago
Duration: 589ms
Invocation: 56c288de25c0440b80303a93039b8bdb
Process: 5150 ExecStart=/etc/openvpn/start.sh (code=exited, status=0/SUCCESS)
Main PID: 5150 (code=exited, status=0/SUCCESS)
Mem peak: 8M
CPU: 134ms
root@transmission-openvpn:#
I just basicaly dont know how to use this XD
Seems to be up and running but i dont know what its used for i think transmission is for torrent download? so you did like a mix of openvpn and transmission to have a vpn in it right? im using a unifi router and i got my openvpn setup i can try something or if you have a quick guide on how to set those up i can test it
Yes, that’s exactly what this image does: it ensures that all Transmission traffic goes only through an OpenVPN tunnel.
Below is a quick guide on how to set up the image using a CyberGhost configuration.
When you generate an OpenVPN configuration from your CyberGhost account, you normally get these files:
default.ovpn
ca.crt
client.crt
client.key
The image can technically work with a single .ovpn file, but CyberGhost’s .ovpn references the other certificate files, so they are required.
Your default.ovpn should look like this:
client
remote 87-1-de.cg-dialup.net 443
dev tun
proto udp
auth-user-pass /config/openvpn-credentials.txt
... (OpenVPN settings)
ca /etc/openvpn/custom/ca.crt
cert /etc/openvpn/custom/client.crt
key /etc/openvpn/custom/client.key
Move all four files into: /etc/openvpn/custom
Make sure the .ovpn file is named: default.ovpn.This is required so the container can detect it when using a custom provider.
Once you get these file you should edit the env files /opt/transmission-openvpn/.env and update these variables:
OPENVPN_USERNAME="your_cyberghost_username"
OPENVPN_PASSWORD="your_cyberghost_password"
OPENVPN_PROVIDER="CUSTOM"
OPENVPN_CONFIG="The Country Where you VPN is configured"
NB: If the Proxmox UI doesn’t give you proper shell access to the container (this happening to me right for any image i'm trying to install with the PVED toolkit), enter it from the host with:
pct enter <container_id>
You mentioned that you already have an OpenVPN setup on your UniFi router.
Just to clarify an important point:
UniFi provides a remote-access VPN, not a VPN provider.
This means:
It allows you to connect to your home network remotely
It does not provide a VPN exit to the internet
It cannot act as a VPN service like CyberGhost, NordVPN, PIA, Mullvad, etc.
Because of this, Transmission-OpenVPN cannot use the OpenVPN configuration from a UniFi router.
It needs a real VPN provider with external servers, otherwise torrent traffic will still go out through your regular public IP.
Can you confirm that you don’t have a VPN provider ? Let me know and I can try to find a workaround using your OpenVpn as a server so you don’t have to pay anything but should be used only for test
And Create /etc/openvpn/server.conf (use nano /etc/openvpn/server.conf):
port 1194
proto udp
dev tun
ca ca.crt
cert server.crt
key server.key
dh dh.pem
server 10.8.0.0 255.255.255.0
keepalive 10 120
persist-key
persist-tun
verb 3
2. Client configuration (This is your transmission-openvpn) [This is similar to what I described for CyberGhost VPN
STEP 1 Create VPN files
In /etc/openvpn/custom create the file default.ovpn as below [The IP address display in your screenshot is 192.168.120.87 but replace it by the real one if it is not]:
client
dev tun
proto udp
remote 192.168.120.87 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca /etc/openvpn/custom/ca.crt
cert /etc/openvpn/custom/client1.crt
key /etc/openvpn/custom/client1.key
verb 3
Return in the OpenVPN server container and copy the following files in /etc/openvpn/custom (if you know how to export files from one container to another or just use nano and copy paste it will be easier juste be careful that the files are well copied a the client1.crt may be long you will need to copy past multiple time as nano cant display the whole file)
ca.crt
client1.crt
client1.key
STEP2 configure the environment:
In /opt/transmission-openvpn/.env modify it like that:
Do not hesitate to restart both containeurif there are some troubleshoot. As I think the openvpn server may be more instable it can sometimes disconnect I think.
Moreover here are my logs for the OpenVpn container [journalctl -u openvpn@server.service -f]:
Im like stuck at client configuration. what do i call the files? test.opvn?
or what should i do i have my two containers one for the debian as you said i did the certs and copied it to the right place in the openvpn server.
Im not the best with VPN servers and network im better with DNS and game servers
I added you on discord cause its not working for me maybe its a file i didnt copied right or something else. if nord VPN works i could get a free week and try to set it up with it. i basicaly never used any vpn provider so if any have free months im ok to try.
Finally, we got it working.
I made a mistake with the .ovpn file and named it .opvn instead…
After fixing that and completing the setup we did together, everything works correctly.
I also tested the update function, and it works properly.
I didn’t see the warning about the web page being inaccessible if the VPN isn’t configured at startup, but it is in the JSON, so users are still informed.
I tested the update exactly as shown by sunflowerhowl, and it worked 100%.
It should also work with any VPN provider that supplies OpenVPN configuration files, and that’s documented in both OpenVPN and Transmission docs — so users who want these apps to work together should already know how to set them up.
Activity
github-actions commentedon Oct 15, 2025
The transmission-openvpn script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/transmission-openvpn.sh)"This application requires a VPN provider to work. Please refer to your VPN provider’s documentation for setting up OpenVPN.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
SunFlowerOwl commentedon Nov 3, 2025
Hi,
It’s been about three weeks and no one has tested this image yet. As I’m the developer, I’d be happy to help if needed or would you prefer to keep development and testing independent?
DragoQC commentedon Nov 30, 2025
Hmmm i ran the install and the access interface port of 9091 dosent seems to show anything
So maybe theres a problem with transmission web ui starting?
SunFlowerOwl commentedon Nov 30, 2025
Hi DragoQC,
Thank you for helping test this script. From my point of view, as long as OpenVPN cannot reach your VPN provider, this behavior is expected. The application blocks all network traffic as part of its kill-switch mechanism.
I can help you set up your OpenVPN configuration. Do you already have a VPN provider, and if so, which one are you using?
If you don’t have a VPN provider, we can also set up your own VPN server using the community OpenVPN script, and then configure transmission-vpn to use it as the VPN provider.
Could you send me the logs after running the following command?
DragoQC commentedon Nov 30, 2025
root@transmission-openvpn:
# systemctl status openvpn-custom.service#○ openvpn-custom.service - Custom OpenVPN start service
Loaded: loaded (/etc/systemd/system/openvpn-custom.service; enabled; preset: enabled)
Active: inactive (dead) since Sat 2025-11-29 23:56:04 EST; 45s ago
Duration: 589ms
Invocation: 56c288de25c0440b80303a93039b8bdb
Process: 5150 ExecStart=/etc/openvpn/start.sh (code=exited, status=0/SUCCESS)
Main PID: 5150 (code=exited, status=0/SUCCESS)
Mem peak: 8M
CPU: 134ms
root@transmission-openvpn:
I just basicaly dont know how to use this XD
Seems to be up and running but i dont know what its used for i think transmission is for torrent download? so you did like a mix of openvpn and transmission to have a vpn in it right? im using a unifi router and i got my openvpn setup i can try something or if you have a quick guide on how to set those up i can test it
SunFlowerOwl commentedon Nov 30, 2025
Yes, that’s exactly what this image does: it ensures that all Transmission traffic goes only through an OpenVPN tunnel.
Below is a quick guide on how to set up the image using a CyberGhost configuration.
When you generate an OpenVPN configuration from your CyberGhost account, you normally get these files:
The image can technically work with a single .ovpn file, but CyberGhost’s .ovpn references the other certificate files, so they are required.
Your default.ovpn should look like this:
Move all four files into: /etc/openvpn/custom
Make sure the .ovpn file is named: default.ovpn.This is required so the container can detect it when using a custom provider.
Once you get these file you should edit the env files /opt/transmission-openvpn/.env and update these variables:
NB: If the Proxmox UI doesn’t give you proper shell access to the container (this happening to me right for any image i'm trying to install with the PVED toolkit), enter it from the host with:
You mentioned that you already have an OpenVPN setup on your UniFi router.
Just to clarify an important point:
UniFi provides a remote-access VPN, not a VPN provider.
This means:
It allows you to connect to your home network remotely
It does not provide a VPN exit to the internet
It cannot act as a VPN service like CyberGhost, NordVPN, PIA, Mullvad, etc.
Because of this, Transmission-OpenVPN cannot use the OpenVPN configuration from a UniFi router.
It needs a real VPN provider with external servers, otherwise torrent traffic will still go out through your regular public IP.
Can you confirm that you don’t have a VPN provider ? Let me know and I can try to find a workaround using your OpenVpn as a server so you don’t have to pay anything but should be used only for test
SunFlowerOwl commentedon Nov 30, 2025
Hi I've tested a work arround and it work:
Follow the step below:
1. Create an OpenVpn Server
On your proxmox shell run:
Choose default installation or as you do usually.
stop the container
And after that, again on you proxmox shell run:
Add at the end the following lines
Save by clicking ctrl+x and after y for yes
restart the containeur
On the server (LXC container)
Once the installation is done run:
Generated files are located in:
Copy to /etc/openvpn/:
And Create /etc/openvpn/server.conf (use nano /etc/openvpn/server.conf):
Start and enable the service:
2. Client configuration (This is your transmission-openvpn) [This is similar to what I described for CyberGhost VPN
In /etc/openvpn/custom create the file default.ovpn as below [The IP address display in your screenshot is 192.168.120.87 but replace it by the real one if it is not]:
Return in the OpenVPN server container and copy the following files in /etc/openvpn/custom (if you know how to export files from one container to another or just use nano and copy paste it will be easier juste be careful that the files are well copied a the client1.crt may be long you will need to copy past multiple time as nano cant display the whole file)
In /opt/transmission-openvpn/.env modify it like that:
Once you're done make sure that your openvpn server is running and then run in the client container:
or just reboot the container or whatever and see the magic at http://192.168.120.87:9091
Do not hesitate to restart both containeurif there are some troubleshoot. As I think the openvpn server may be more instable it can sometimes disconnect I think.
Moreover here are my logs for the OpenVpn container [journalctl -u openvpn@server.service -f]:
And the result:
DragoQC commentedon Nov 30, 2025
Im like stuck at client configuration. what do i call the files? test.opvn?
or what should i do i have my two containers one for the debian as you said i did the certs and copied it to the right place in the openvpn server.
Im not the best with VPN servers and network im better with DNS and game servers
SunFlowerOwl commentedon Nov 30, 2025
Dont worries
Nice this should be working then.
No it should be called default.opvn in /etc/openvpn/custom
You must add also in the directory the ca.crt the client1.key and client1.crt from the server configuration step
DragoQC commentedon Dec 1, 2025
I added you on discord cause its not working for me maybe its a file i didnt copied right or something else. if nord VPN works i could get a free week and try to set it up with it. i basicaly never used any vpn provider so if any have free months im ok to try.
DragoQC commentedon Dec 5, 2025
Finally, we got it working.
I made a mistake with the .ovpn file and named it .opvn instead…
After fixing that and completing the setup we did together, everything works correctly.
I also tested the update function, and it works properly.
I didn’t see the warning about the web page being inaccessible if the VPN isn’t configured at startup, but it is in the JSON, so users are still informed.
I tested the update exactly as shown by sunflowerhowl, and it worked 100%.
It should also work with any VPN provider that supplies OpenVPN configuration files, and that’s documented in both OpenVPN and Transmission docs — so users who want these apps to work together should already know how to set them up.
@michelroegl-brunner