Author Topic: Server Help  (Read 2017 times)

Shazam

  • Newbie
  • *
  • Status:
    Offline
    Posts:
    2
    • View Profile
on: February 04, 2017, 03:19:48 PM
I've recently rented a server but everytime me and my friend join our games crash. Any help would be great, heres what my log says :

Sat Feb 04 13:21:49 2017| Client UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0
Sat Feb 04 13:21:49 2017| Client UDP: Error receiving from 128.199.41.159, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:49 2017| Client UDP: Error receiving from 128.199.57.194, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:49 2017| Client UDP: Error receiving from 45.55.75.71, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:49 2017| Client UDP: Error receiving from 138.197.75.193, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:49 2017| Client UDP: Error receiving from 45.55.84.202, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.68.18.186, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.68.53.85, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.68.3.3, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 128.199.158.78, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 128.199.57.194, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 45.55.75.71, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.197.75.193, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 45.55.84.202, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.68.53.85, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.68.18.186, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.68.3.3, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 128.199.41.159, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 128.199.57.194, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 128.199.158.78, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 45.55.75.71, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.197.75.193, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 45.55.84.202, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.68.18.186, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.68.53.85, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.68.3.3, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 128.199.158.78, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 128.199.57.194, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 45.55.75.71, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.197.75.193, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 45.55.84.202, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.68.18.186, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.68.53.85, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.68.3.3, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 128.199.158.78, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 128.199.41.159, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 128.199.57.194, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 45.55.75.71, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 138.197.75.193, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:50 2017| Client UDP: Error receiving from 45.55.84.202, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 138.68.18.186, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 138.68.53.85, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 138.68.3.3, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 128.199.57.194, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 128.199.158.78, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 45.55.75.71, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 45.55.84.202, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 138.197.75.193, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 138.68.18.186, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 138.68.53.85, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 138.68.3.3, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 128.199.158.78, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 128.199.41.159, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 128.199.57.194, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 45.55.75.71, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 45.55.84.202, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 138.197.75.193, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 138.68.18.186, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 138.68.53.85, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 138.68.3.3, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 128.199.158.78, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 128.199.41.159, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 128.199.41.159, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 128.199.57.194, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 45.55.75.71, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 45.55.84.202, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:51 2017| Client UDP: Error receiving from 138.197.75.193, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:52 2017| Client UDP: Error receiving from 138.68.18.186, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:52 2017| Client UDP: Error receiving from 138.68.53.85, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:52 2017| Client UDP: Error receiving from 138.68.3.3, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:52 2017| Client UDP: Error receiving from 128.199.158.78, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:52 2017| Client UDP: Error receiving from 128.199.41.159, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:52 2017| Client UDP: Error receiving from 128.199.41.159, error: No connection could be made because the target machine actively refused it, received bytes: 0
Sat Feb 04 13:21:52 2017| UDP closed
Sat Feb 04 13:21:52 2017| Client UDP: Connection closed
Sat Feb 04 13:21:55 2017| Waiting for Online polling threads
Sat Feb 04 13:21:55 2017| Online polling threads finished
Sat Feb 04 13:21:55 2017| Waiting for LAN polling threads
Sat Feb 04 13:21:55 2017| LAN polling threads finished
Sat Feb 04 13:21:55 2017| remote address: ip, init: steam
Sat Feb 04 13:21:55 2017| Connecting to server at :27000
Sat Feb 04 13:21:55 2017| Client UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0
Sat Feb 04 13:21:55 2017| Initiating connection with server ID 90106692289774592
Sat Feb 04 13:21:59 2017| Querying for an authentication session ticket
Sat Feb 04 13:21:59 2017| Authentication successful!
Sat Feb 04 13:22:02 2017| Error: EXCEPTION_ACCESS_VIOLATION
Sat Feb 04 13:22:02 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 000000000082fbe4 2>&1
Sat Feb 04 13:22:02 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:02 2017| operable program or batch file.
Sat Feb 04 13:22:02 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 000000000083024e 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 00000000004dcea3 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 00000000004d5412 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 00000000005c2bde 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 00000000005c80de 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 0000000000821a50 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 0000000000820d2a 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 0000000000821a50 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 0000000000820d2a 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 0000000000821afd 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 00000000004a634a 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 00000000004a9130 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 0000000000407a3d 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 0000000000408811 2>&1
Sat Feb 04 13:22:03 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:03 2017| operable program or batch file.
Sat Feb 04 13:22:03 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 00000000004035e4 2>&1
Sat Feb 04 13:22:04 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:04 2017| operable program or batch file.
Sat Feb 04 13:22:04 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 0000000000ff633f 2>&1
Sat Feb 04 13:22:04 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:04 2017| operable program or batch file.
Sat Feb 04 13:22:04 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 00000000004013e8 2>&1
Sat Feb 04 13:22:04 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:04 2017| operable program or batch file.
Sat Feb 04 13:22:04 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 00000000004014eb 2>&1
Sat Feb 04 13:22:04 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:04 2017| operable program or batch file.
Sat Feb 04 13:22:04 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 00007ff8f3668364 2>&1
Sat Feb 04 13:22:04 2017| 'addr2line' is not recognized as an internal or external command,
Sat Feb 04 13:22:04 2017| operable program or batch file.
Sat Feb 04 13:22:04 2017| addr2line -i -e "E:\Steam Library\steamapps\common\Avorion\bin\Avorion.exe" 00007ff8f39070d1 2>&1
Sat Feb 04 13:22:04 2017| 'addr2line' is not recognized as an internal or external command,
« Last Edit: February 04, 2017, 03:31:49 PM by Shazam »