
Best Answer Cervanthes, 11 September 2024 - 01:17 PM
that error mostly hangs together with NAT problems on the host machine
its a issue we just recently figured outa fix for and are slowly implementing it is for the time being the resolvment of this issue a giant hit or miss
we had good reports with using some specific VPN providers [disclaimer we are in no way sponsored or endorsed by any of them]
Privdao Free tier with a spit tunnel set up has allowed people to circumvent the issue
Premium Proton VPN with Portforwarding and p2p to true has worked 80% of the time
you can adapt these two guides into a solution should you have any questions just ask away
https://gist.github....8abcc9e2485970a
https://gist.github....fd0fa2ba48276fe
