The problem occurs in all sources. You're not blocking some things through firewall, so some servers are able to receive external packets from net crawlers. You could also just use the updated network code from v21.2, and it fixes the issue as well.
Can you guys share more information?
11/11/2022 17:04
M¿dScientist#16
11/12/2022 04:58
Ruby-FlyFF#17
I see, but I doubt he has the ability to do that, more help for him would be appreciated, I don’t see how I could help him I did the maximum and I still don’t find his problem after 3 hours spent on discord
11/12/2022 12:10
makvee#18
Hi thanks for the reply. Anyway i don't have any clue about "updated network code" can you give me some clue please?Quote:
The problem occurs in all sources. You're not blocking some things through firewall, so some servers are able to receive external packets from net crawlers. You could also just use the updated network code from v21.2, and it fixes the issue as well.
11/12/2022 19:58
Nιgнтмαяε#19
Just change all the ports and only allow the ones actually needed. This issue is really simple to fix and usually always due to poor firewall settings.Quote:
11/22/2022 10:33
Tamus#20
Quote:
Can you guys share more information as to why this error pops up? I've been receiving this error few times that causes core server to crash. Any information is very very well appreciated.
Error:
This is only my own theory:Code:CClientSocket.Fetch: ip = 54.245.49.145, size = 790647882
When you use any hosting services, random snapshots of bots maybe or services as well that pings your server in a certain port and thus making your core server crash. I might really be wrong but I hope you get what I want to tell.
secured your coreserver