Post #2233189

@fergycool@mastodon.social @warandpeas@mastodon.social @smallsco@oldbytes.space yup, if you're getting a timeout on the client side, it definitely sounds like a firewall/port forwarding issue. If you have your log level set at INFO or more verbose (I wouldn't recommend DEBUG though, it significantly slows things down and causes random issues), you should see something like "INFO:atalkvpn.server:Registered new node ...". This message shows if anything comes over UDP, so you can easily check if your server is reachable with netcat, e.g.: nc -zu your.atalkvpn.server.address 1029. Keep in mind that there's no client timeout mechanism implemented yet, so the client will stay registered until server restart. It shouldn't cause any issues though, it's just a tiny client object instance sitting quietly in server memory.