@bob-dig Yes, I can ping the domain name and receive a response from the firewall.

@stephenw10 I deleted the WireGuard tunnel then I set it up all over again. Done the same thing at VPS. Rebooted remote VM and pfSense and it started working.

I have no idea what happened before but I thanks you for all the support you provided!!

Thanks a lot

:-)

kind regards

@johnpoz

Thanks - but that gave the same error. I think the root of my problem is that VirginMedia hate VPNs!

https://windowsreport.com/vpn-blocked-virgin/

I think I will try accessing the site sometime when on another isp!

Thanks again - must go battery very low.

@gabacho4 Did you ever figure it out?

I created a small tool luckman212/stv to help make it a little easier to debug states. In case it's useful to anyone else.

@ma0f97 Has no one an idea?

For anyone else finding this thread. I've found the solution.

Create a port forwarding rule

INTERFACE: WG0
PORT: 44158
DESTINATION: WG0
DEST PORT: 44158
REDIRECT TARGET IP: MINER IP
REDIRECT PORT: 44158

Then everything works as expected.

@jimp thx for the hint it's working now, it totally make sense now. hope it will you @bbusa as well

@theonemcdonald said in Wireguard Public and Private Key Protection:

I have mentally considered an additional layer for the extremely paranoid, but because pfsense already has encrypted configuration backup capabilities, I don't plan on spending much time on this any time soon.

Fully agreed.

@johnnyfive Yeah this is the problem - what a shame. It would be really great to have full acceleration using QuickAssist!

@jimp Yes would love this feature as wel. Tested it and works really fast en easy to setup. Timeline even for beta release would be great.
OpenVpn has so much overhead, and just does not meet the speed requirements with low(er) end hardware.