I was in a similar situation as well. Based on my conversation with the support staff, it seems like they are not allowed to access customer information without the transaction ID. At least unmigrated Minecraft account still works, despite them saying they wouldn't be accessible after March.

I think i'm going to write a convert a wireguard config into a wireproxy config file. Hopefully that will make it easier for people to use.

Suggest to try with this - https://github.com/go-ini/ini Wireguard config is ini format.

Yes, and supporting multiple peers isn't really on my todo list. I guess you can host multiple wireproxy instances for each peers.

Not yet unfortunately. I'll add it in the future, but I'm preoccupied with homework right now.

i have yet to encounter a case where a udp-tunnel has a practical advantage over tcp; on the other hand, corporate/hotel/coffeeshop firewalls that block anything not tcp/443 are super commom.

Thanks.

I made it because my friends and I use wireguard to have a private network, and they don't feel comfortable running a ssh server on their machines. It can also be used with a vpn provider like Mullvad without setting up a new nic or requiring special privs.

I want to point out a caveat to others: Proxifier != VPN

wireproxy's wg only forwards TCP and UDP. I am not sure how ICMP is handled. Other transports, though rarely used, won't be tunneled (and may leak, if not dropped).

Most importantly missing: DNS, which usually is handled over UDP (changing slowly now with DNS-over-HTTPS and some TCP resolvers). Without handling DNS requests via your proxy, you're still leaking information about yourself to the resolver you're using.

SOCKS5 supports DNS queries. Not sure if this project implements it though.

To clarify, UDP is not currently supported, but I intend to support it in the future. Incoming ICMP should be completely dropped, and outgoing ICMP is not supported.