search

pierrickrouxel / iocage-plugin-rtorrent-flood

Artifact file(s) for rTorrent Flood iocage plugin
BSD 2-Clause "Simplified" License
7 stars 7 forks source link

Cannot Get OpenVPN To Start Using Mullvad #11

Open seniorm0ment opened 2 years ago

seniorm0ment commented 2 years ago

I am using Mullvad VPN as my VPN for this, and for OpenVPN they give 4 files. A .crt (mullvad_ca.crt), a userpass (mullvad_userpass.txt), a .conf (mullvad_us_nyc.conf), and a resolve-conf (update-resolv-conf).

When I place these in the directory, and run service openvpn start, it says it failed to start. I tried renaming the conf and pass to openvpn.conf and pass.txt, didn't fix.

Not sure what's up.

JamesMcMahon commented 1 year ago

I am in the same situation, did you ever figure this out?

seniorm0ment commented 1 year ago

Nope :/

JamesMcMahon commented 1 year ago

Okay I got it.

so ignore the pass.txt file. You need a pass file, but I am not sure why the README is that specific. The Mullvad config sets up the path for everything.

Steps:

  1. Download the config files from the Mullvad conf generator
  2. Copy all the files into the rsync-flood jail to a temp location your user can write to, for instance scp -r ~/Downloads/mullvad_config_linux_us_all username@freenas-device.local:/mnt/poolname/iocage/jails/rtorrent-flood-jail/root/home/rtorrent
  3. Get a shell session open into the jail by using jls to find the jail id and using sudo jexec jail-id-number /bin/tcsh
  4. Move all the Mullvad files from the temp location above into /usr/local/etc/openvpn
  5. Rename mullvad.conf (this is different depending on the options) to openvpn.conf
  6. Edit openvpn.conf and update the up and down script path to point to /usr/local/etc/openvpn/update-resolv-conf
  7. Add execute privileges to update-resolv-conf by running chmod +x /usr/local/etc/openvpn/update-resolv-conf
  8. Install bash inside that jail using pkg install bash
  9. Change the shebang at the top of update-resolv-conf to !/usr/local/bin/bash (OpenBSD does NOT install to /bin/bash, this required so much debugging you have no idea)
  10. Follow the steps described in the README to enable and start OpenVPN

This took a lot of debugging to figure out, so good chance I missed a step here. If I missed anything update this thread.

JamesMcMahon commented 1 year ago

Word of warning, since Mullvad removed port forwarding you probably will not have much luck seeding.

seniorm0ment commented 1 year ago

I wasn't port forwarded for a while, but I primarily use private trackers. Is that likely why?