Nickatony

Relevant logs attached -- apologies for the oversight. binhex_qbit_command_execution_logs.txt binhex_qbit_supervisord_debug_logs.txt

I seem to be having an issue with port forwarding that I can't resolve after a few hours of troubleshooting. I've followed the relevant question 31 in the FAQ and configured it to the best of my knowledge according to the documentation. I use ProtonVPN: both OVPN and WireGuard VPN configurations work great with the exception of port forwarding. My WireGuard configuration has port forwarding enabled, confirmed by the wg0 config, and my user has the appropriate +pmp appended. Without STRICT_PORT_FORWARD enabled, I can see the following in the logs: [info] Port forwarding is not enabled This is my primary issue that I'd like to understand a bit better. I'm not sure where how this determination is made. I have enabled port forwarding enabled from ProtonVPN, it's set in my wg0, the server supports it, and my user is appended with the correct flag/identifier for port forwarding. Doing some more tinkering, I came across this: With STRICT_PORT_FORWARD enabled, I can see some other things in the debug logs which appear to be doing some port assignment from ProtonVPN. 2025-01-16 22:13:57,120 DEBG 'start-script' stdout output: initnatpmp() returned 0 (SUCCESS) using gateway : 10.2.0.1 sendpublicaddressrequest returned 2 (SUCCESS) readnatpmpresponseorretry returned 0 (OK) Public IP address : <redacted> epoch = 4978682 closenatpmp() returned 0 (SUCCESS) 2025-01-16 22:13:57,121 DEBG 'start-script' stdout output: [debug] Running infinite while loop to keep assigned incoming port for ProtonVPN live... 2025-01-16 22:13:57,272 DEBG 'start-script' stdout output: [debug] ProtonVPN assigned incoming port is '50862' Cursory port-forwarding checks while running in this configuration came up with the particular port being closed. Also, with STRICT_PORT_FORWARD enabled, I am unable to access the GUI--this is likely a separate issue. Should STRICT_PORT_FILTERING have any bearing on an ProtonVPN setup? As I understand, the STRICT_PORT_FILTERING is a setting relevant to PIA. I'd appreciate any help that someone could offer. I think this is my 3rd time trying to get port forwarding up and running and am still having little luck.

Welp, I took the plunge a couple weeks ago, and all is well. I followed another thread on here that suggested some pre-activities like backing up the apps directory, VMs, and removing some unsupported plugins. I also ran the upgrade helper and it guided me through most of it. It's worth noting that I have a very straight-forward setup with only a couple docker containers and VMs. Most importantly, I backed-up the USB so that if anything went wrong, I had an avenue to revert back.

I'm in the same boat as you. Did you make the jump? How did it go?