rvlution

Could access UI on sunday, can't remember when I updated. Can't access now

Woke up to a couple torrents downloading very slowly, all had seeds so should be working fine. Rebooted container and speeds shot up to what my max is. A few minutes later it's dropped back down and seems to be fluctuating. Anyone else experiencing this? Using PIA with Wireguard, Toronto endpoint.

So I think it may have to do with my port forwarding. I have checked if port 1194 is open and it is not. Not really sure where to go from here since every walkthrough takes about 2 minutes and doesn't give any additional details.

Are they editing their .ovpn file?

Here is my log from trying to connect using my laptop: Fri Nov 08 16:37:56 2019 OpenVPN 2.4.8 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Oct 31 2019 Fri Nov 08 16:37:56 2019 Windows version 6.2 (Windows 8 or greater) 64bit Fri Nov 08 16:37:56 2019 library versions: OpenSSL 1.1.0l 10 Sep 2019, LZO 2.10 Fri Nov 08 16:37:56 2019 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340 Fri Nov 08 16:37:56 2019 Need hold release from management interface, waiting... Fri Nov 08 16:37:56 2019 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340 Fri Nov 08 16:37:57 2019 MANAGEMENT: CMD 'state on' Fri Nov 08 16:37:57 2019 MANAGEMENT: CMD 'log all on' Fri Nov 08 16:37:57 2019 MANAGEMENT: CMD 'echo all on' Fri Nov 08 16:37:57 2019 MANAGEMENT: CMD 'bytecount 5' Fri Nov 08 16:37:57 2019 MANAGEMENT: CMD 'hold off' Fri Nov 08 16:37:57 2019 MANAGEMENT: CMD 'hold release' Fri Nov 08 16:37:57 2019 WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead. Fri Nov 08 16:37:57 2019 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Fri Nov 08 16:37:57 2019 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Fri Nov 08 16:37:57 2019 MANAGEMENT: >STATE:1573249077,RESOLVE,,,,,, Fri Nov 08 16:37:57 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]207.98.189.235:1194 Fri Nov 08 16:37:57 2019 Socket Buffers: R=[65536->65536] S=[65536->65536] Fri Nov 08 16:37:57 2019 UDP link local: (not bound) Fri Nov 08 16:37:57 2019 UDP link remote: [AF_INET]207.98.189.235:1194 Fri Nov 08 16:37:57 2019 MANAGEMENT: >STATE:1573249077,WAIT,,,,,, Fri Nov 08 16:37:57 2019 MANAGEMENT: >STATE:1573249077,AUTH,,,,,, Fri Nov 08 16:37:57 2019 TLS: Initial packet from [AF_INET]207.98.189.235:1194, sid=e9df0c07 3bef4c4d Fri Nov 08 16:37:57 2019 TLS Error: cannot locate HMAC in incoming packet from [AF_INET]207.98.189.235:1194 Fri Nov 08 16:37:58 2019 MANAGEMENT: >STATE:1573249078,AUTH,,,,,,

I've followed Spaceinvader One's newest tutorial for this (as well as setting up a duck dns profile) and I am stuck. I have verified that my IP address is correct but as soon as I get to trying to connect it fails. Any thing I should try to check first?

It still didn't seem to recognize I had anything in the drive even outside of the gui. However, I'm perfectly fine taking the extra step of pulling up the gui.

I can't seem to input this correctly, am I missing something? UPDATE: So I tried turning off automatic disc ripper and it immediately recognized the first disc I tried. Are there settings with that I may have not configured correctly? Thanks again for the help, this all new territory to me.

If I have a minute tonight I'll make that change. Thanks!

I won't be able to try again for a few days but I'll check the log.

Restarted multiple times, and just now put the same disc in to no avail.

I am having trouble getting it to recognize I have a disk in the drive. I have the Extra Parameters included and the drive is being seen, but no disks. However, today I was able to get a disk to successfully rip once I reinstalled the docker. After 1 rip it does not recognize disks anymore. Included are my settings. Any suggestions are appreciated!