Sure, but I cant predict how long it will take for the next log.

This time was slightly different. I joined a room and couldnt connect to anyone straight from beginning (all showed as fp). However this time I could close the room without voobly shutting down. But when I rejoined the room, again couldn't connect (not yet fp though, but it was clear there would be no connect) and THEN closed the room again, voobly would crash. I still think it was kind of the same error, only that this time the "cursed" player (who would prevent me from connecting with others) was already in the room instead of joining after I had already been connected to others. Unfortunately this way I can't tell who was "responsible". The only thing strange is that voobly didn't shut down the first time I left the room as I would have expected. Maybe the log still helps finding out what causes this weird error. But I can post more, maybe again in the constellation where it is clear which player was "responsible".

Attachment didn't work.

Actually I just saw in the log that there was the same player in the room as when it happened for the first time (PapinSantola). So I think the issue was again with him (no blaming intended).

Here we go again. This time it was the player llari who entered, was fp and made all the other players become fp too, then voobly crashing when trying to close the room.

Edit: Oh and if that is of any importance: There are also players who are fp but don't cause this issue. It's only specific fp players that will cause issues. Here's an example log snippet where the fp connection didnt cause problems:

00:43:36 NAT1: [00:43:36] [User: lamojo] Local User: Pooping_Pony, Remote User: lamojo
00:43:36 NAT1: [00:43:36] [User: lamojo] [Tunnel: direct] State changed to DCC_INIT
00:43:36 NAT1: [00:43:36] [User: lamojo] Sending local candidate port list, LAN Port = 16000, WAN Port = 16000, User Proxy = :0
00:43:55 NAT1: [00:43:55] [User: lamojo] Peer ack'ed local candidate port list
00:44:10 NAT1: [00:44:10] [User: lamojo] Local User: Pooping_Pony, Remote User: lamojo
00:44:10 NAT1: [00:44:10] [User: lamojo] [Tunnel: direct] State changed to DCC_INIT
00:44:10 NAT1: [00:44:10] [User: lamojo] Sending local candidate port list, LAN Port = 16000, WAN Port = 16000, User Proxy = :0
00:44:16 NAT1: [00:44:16] [User: lamojo] Peer ack'ed local candidate port list
00:44:16 NAT1: [00:44:16] [User: lamojo] Received remote candidate port list, LAN Port = 3891, WAN Port = 21289, User Proxy = :0
00:44:16 NAT1: [00:44:16] [User: lamojo] [Tunnel: user proxy] No user proxy specified
00:44:16 NAT1: [00:44:16] [User: lamojo] [Tunnel: direct] State changed to DCC_TUNNEL_TEST
00:44:16 NAT1: [00:44:16] [User: lamojo] [Tunnel: fast proxy] Received PH_TYPE_TUNNEL_TEST_ACK
00:44:16 NAT1: [00:44:16] [User: lamojo] [Tunnel: fast proxy] Proxy -> FPS_ALIVE
00:44:19 NAT1: [00:44:19] [User: lamojo] Peer's in port changed to 16000
00:44:19 NAT1: [00:44:19] [User: lamojo] [Tunnel: direct] Received PH_TYPE_DIRECT_TEST_ACK, port = 21289
00:44:22 NAT1: [00:44:22] [User: lamojo] [Tunnel: fast proxy] Received PH_TYPE_TUNNEL_TEST
00:44:24 NAT1: [00:44:24] [User: lamojo] [Tunnel: direct] in port change from 0 to 21289
00:44:24 NAT1: [00:44:24] [User: lamojo] [Tunnel: direct] Received PH_TYPE_DIRECT_TEST - port = 16000
00:44:31 NAT1: [00:44:31] [User: lamojo] [Tunnel: direct] Received PH_TYPE_TUNNEL_TEST
00:44:31 NAT1: [00:44:31] [User: lamojo] [Tunnel: direct] Received PH_TYPE_DIRECT_TEST_ACK_ACK
00:44:31 NAT1: [00:44:31] [User: lamojo] [Tunnel: direct] Both sides report direct test pass. Using port = 21289
00:44:31 NAT1: [00:44:31] [User: lamojo] [Tunnel: direct] Starting PH_TYPE_TUNNEL_TEST to verify
00:44:31 NAT1: [00:44:31] [User: lamojo] [Tunnel: direct] State changed to DCC_TUNNEL_TEST2
00:44:33 NAT1: [00:44:33] [User: lamojo] [Tunnel: direct] Received PH_TYPE_TUNNEL_TEST_ACK
00:44:33 NAT1: [00:44:33] [User: lamojo] [Tunnel: direct] State changed to DCC_DONE

(this snippet is not included in the file, tell me if you need its full log as well)

... and one more
This time the problem was with ReyDavid2000 (again he was fp, then the whole room became fp too and voobly crashed when trying to close the room). Funny thing is that I had played with him 2 games earlier without problems.

This time I think it was the player ELPR0FE_Espert...

misterionoob...

Do the files give any hints so far whats causing the error? Do you need more?

Mokelem and/or DarkSheriff

EnzoFionnIgo...

This is really weird. Do you know whether other players in the same game room have the problem as well, or is it just you disconnecting when that happens?

It's usually just me in a specific room. However, I asked some random guys once if they know this issue and several said they had experienced it before as well. Plus there was another thread formerly on this issue, so in general I don't think I am the only one.

I didn't have this problem like 2 years ago, but I can't tell whether it happens now due to some voobly update or due to my new isp.

Do you think the Windows Event Viewer might give some further insight?

This looks like an IDS/IPS event where security software (software or hardware based) is disconnecting you. Do you have a hardware firewall or Next Generation firewall or any other security software installed on your computer?

Only thing I can imagine is something hardware-based, I gotta check that.

Please make sure, that no Intrusion Detection / Intrusion Prevention or any other security feature attempting to scan the traffic going through UDP 16000, otherwise you will have exactly those issues. Sophos Firewall Home is also known causing this, so always make sure that AV, IPs, proxy, application filter etc. is turned OFF.