Jump to content

Edit History

Please note that revisions older than 365 days are pruned and will no longer show here
Sora

Sora


Cleaned up the clarification part & added the dev's serverconfig.xml addition info

For some reason or rather, updating a dedicated server from v1.0 (beta) b313 -> b316 will render the dedicated server broken and with clients unable to play (can't interact, quests throwing errors in logs, Console error "EndOfStreamException: Attempted to read past the end of the stream" error before clicking "Spawn")

 

For anyone having this issue, try the following:

  1. Backup your serverconfig.xml, Saves, mods and anything else that is non-default.
  2. Delete the dedicated server.
  3. Re-install the dedicated server (clean full install!) from SteamCMD.
  4. Copy back your serverconfig.xml, Saves, mods and anything else that is non-default.
  5. Add the new line to serverconfig.xml (see below under Update).

 

Looks like updating a dedicated server via SteamCMD from v1.0_b313 messes something up.

A full clean reinstall followed by restoration of saves and settings fixes the problem.

 

Debugging info:

  • Tried restarting server multiple times. No luck.
  • Changed networking protocol between SteamNetworking and LiteNetLib. No luck.
  • Copied in a backup of the Pregen10kD map that was used, including the dev supplied one. No luck.
  • Copied saves from dedicated server to a normal 7D2D client: It worked! (others could also join without issues)
  • Copied the saves back from the 7D2D client to the dedicated server. No luck.
  • Clean installed a new dedicated server: It worked!
  • Copied over saves and settings into the newly installed clean dedicated server: It worked!

Conclusion:

SteamCMD's update results in a corrupted dedicated server, whereas a clean install worked fine.

 

Clarification:
Dedicated servers update without errors from SteamCMD. The problem is that clients are no-longer able to connect and play properly once they connect since everything interactable pretty much stops working as the dedicated server is no longer communicating properly with the clients after the "EndOfStreamException" error is thrown during the player's connection to the server. The error will show up on both the dedicated server logs as well as on the client side".

Update:
Devs added in the update post -> here <- that we need to add an extra line to existing pre b316 serverconfig.xml files.
 

<property name="QuestProgressionDailyLimit" value="3"/> <!-- Limits the number of quests that contribute to quest tier progression a player can complete each day. Quests after the limit can still be completed for rewards. -->

 

Sora

Sora

For some reason or rather, updating a dedicated server from v1.0 (beta) b313 -> b316 will render the dedicated server broken and with clients unable to play (can't interact, quests throwing errors in logs, Console error "EndOfStreamException: Attempted to read past the end of the stream" error before clicking "Spawn")

 

For anyone having this issue, try the following:

  1. Backup your serverconfig.xml, Saves, mods and anything else that is non-default
  2. Delete the dedicated server
  3. Re-install the dedicated server (clean full install!) from SteamCMD
  4. Copy back your serverconfig.xml, Saves, mods and anything else that is non-default

 

Looks like updating a dedicated server via SteamCMD from v1.0_b313 messes something up.

A full clean reinstall followed by restoration of saves and settings fixes the problem.

 

Debugging info:

  • Tried restarting server multiple times. No luck.
  • Changed networking protocol between SteamNetworking and LiteNetLib. No luck.
  • Copied in a backup of the Pregen10kD map that was used, including the dev supplied one. No luck.
  • Copied saves from dedicated server to a normal 7D2D client: It worked! (others could also join without issues)
  • Copied the saves back from the 7D2D client to the dedicated server. No luck.
  • Clean installed a new dedicated server: It worked!
  • Copied over saves and settings into the newly installed clean dedicated server: It worked!

Conclusion:

SteamCMD's update results in a corrupted dedicated server, whereas a clean install worked fine.

 

[Edit]Clarification: Dedicated servers update without errors from SteamCMD. The problem is that clients are no-longer able to connect and play properly once they connect since everything interactable pretty much stops working as the dedicated server is no longer communicating properly with the clients after the "EndOfStreamException" error is thrown during the player's connection to the server. The error will show up on both the dedicated server logs as well as on the client side".[/Edit]

Sora

Sora

For some reason or rather, updating a dedicated server from v1.0 (beta) b313 -> b316 will render the dedicated server broken and with clients unable to play (can't interact, quests throwing errors in logs, Console error "EndOfStreamException: Attempted to read past the end of the stream" error before clicking "Spawn")

 

For anyone having this issue, try the following:

  1. Backup your serverconfig.xml, Saves, mods and anything else that is non-default
  2. Delete the dedicated server
  3. Re-install the dedicated server (clean full install!) from SteamCMD
  4. Copy back your serverconfig.xml, Saves, mods and anything else that is non-default

 

Looks like updating a dedicated server via SteamCMD from v1.0_b313 messes something up.

A full clean reinstall followed by restoration of saves and settings fixes the problem.

 

Debugging info:

  • Tried restarting server multiple times. No luck.
  • Changed networking protocol between SteamNetworking and LiteNetLib. No luck.
  • Copied in a backup of the Pregen10kD map that was used, including the dev supplied one. No luck.
  • Copied saves from dedicated server to a normal 7D2D client: It worked! (others could also join without issues)
  • Copied the saves back from the 7D2D client to the dedicated server. No luck.
  • Clean installed a new dedicated server: It worked!
  • Copied over saves and settings into the newly installed clean dedicated server: It worked!

Conclusion:

SteamCMD's update results in a corrupted dedicated server, whereas a clean install worked fine.

Sora

Sora

For some reason or rather, updating a dedicated server from v1.0 (beta) b313 -> b316 will render the dedicated server broken and with clients unable to play (can't interact, quests throwing errors in logs, Console error "EndOfStreamException: Attempted to read past the end of the stream" error before clicking "Spawn")

 

For anyone having this issue, try the following:

  1. Backup your serverconfig.xml, Saves, mods and anything else that is non-default
  2. Delete the dedicated server
  3. Re-install the dedicated server (clean full install!) from SteamCMD
  4. Copy back your serverconfig.xml, Saves, mods and anything else that is non-default

 

Looks like updating a dedicated server via SteamCMD from v1.0_b313 messes something up.

A full clean reinstall followed by restoration of saves and settings fixes the problem.

Debugging info:

  • Tried restarting server multiple times. No luck.
  • Changed networking protocol between SteamNetworking and LiteNetLib. No luck.
  • Copied in a backup of the Pregen10kD map that was used, including the dev supplied one. No luck.
  • Copied saves from dedicated server to a normal 7D2D client: It worked! (others could also join without issues)
  • Copied the saves back from the 7D2D client to the dedicated server. No luck.
  • Clean installed a new dedicated server: It worked!
  • Copied over saves and settings into the newly installed clean dedicated server: It worked!

Conclusion:

SteamCMD's update results in a corrupted dedicated server, whereas a clean install worked fine.

×
×
  • Create New...