H hostmod Member Joined Aug 21, 2016 Messages 19 Reaction score 2 Points 35 Aug 22, 2016 #1 I got this error in my logs, they appear right after I log in for whmcs "error reading tcp socket Connection reset by peer"
I got this error in my logs, they appear right after I log in for whmcs "error reading tcp socket Connection reset by peer"
BugzZ Member Joined Apr 7, 2016 Messages 8 Reaction score 0 Points 36 Aug 22, 2016 #2 i got the same error
ehthe Retired Staff Contributor Joined Apr 26, 2015 Messages 1,029 Reaction score 896 Points 216 Aug 22, 2016 #3 Google is your bff. And if you still can't understand it, don't pay it no mind.
H hostmod Member Joined Aug 21, 2016 Messages 19 Reaction score 2 Points 35 Aug 22, 2016 Thread starter #4 I couldn't find anything related to this error in teamspeak server, any help is welcome.
gamesbond Member Joined Jul 21, 2015 Messages 103 Reaction score 13 Points 53 Aug 22, 2016 #5 hostmod said: I got this error in my logs, they appear right after I log in for whmcs "error reading tcp socket Connection reset by peer" Click to expand... This is an error because your firewall is not set properly and you received a ddos on tcp
hostmod said: I got this error in my logs, they appear right after I log in for whmcs "error reading tcp socket Connection reset by peer" Click to expand... This is an error because your firewall is not set properly and you received a ddos on tcp
H hostmod Member Joined Aug 21, 2016 Messages 19 Reaction score 2 Points 35 Aug 22, 2016 Thread starter #6 Brother, as I informed him only appears after I login by the teamspeak in whmcs, just lie there!
ehthe Retired Staff Contributor Joined Apr 26, 2015 Messages 1,029 Reaction score 896 Points 216 Aug 22, 2016 #7 well your whmcs is literally shit. It doesn't correctly close the connection. AGAIN DON'T BOTHER WITH IT !
well your whmcs is literally shit. It doesn't correctly close the connection. AGAIN DON'T BOTHER WITH IT !
Rikku Contributor Joined Sep 14, 2015 Messages 156 Reaction score 61 Points 122 Aug 30, 2016 #8 This will be fixed in Server Version: 3.0.13.4