Skip to content
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Donate
Collapse

Plutonium

  1. Home
  2. BO2 Server Hosting Support
  3. How to debug/where is log located?

How to debug/where is log located?

Scheduled Pinned Locked Moved BO2 Server Hosting Support
3 Posts 2 Posters 84 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • SwaffelSmurfundefined Offline
    SwaffelSmurfundefined Offline
    SwaffelSmurf
    wrote on last edited by SwaffelSmurf
    #1

    Hi,

    I am trying to create a (docker) container for T6 multiplayer. I little experience of running the bo2 server on Windows server or any Linux distro but have read documentation and threads here of course.

    Thus far I am fairly successful (wines works fine, also updating etc. works), however I am running into some problems now.

    1. I cannot connect to the server via T6 client

      • I am using <local ip>:port to connect
      • docker run command exposes the right port (which opens the container up to network)
      • I have opened right port on my router (which is irrelevant for this problem)
    2. Heartbeats are successful however every minute it changes maps (see screenshot behind spoiler).

    :::

    screenshot of terminal

    :::

    My gut tells me the game never starts (cuz of some error), and thus its changing to a new map every minutes which in turn causes issue 1, so I am focusing on issue 2 for now mainly. But its a gut feeling as I said.

    Now I am wondering how to debug this so I can fix my problems.
    Any other ideas are of course welcome as well.

    Kind regards and thanks for reading 🙂

    1 Reply Last reply
    0
    • Resxtundefined Offline
      Resxtundefined Offline
      Resxt Plutonium Staff
      wrote on last edited by
      #2

      So you're hosting on the same PC you play on? What is the port set to?

      SwaffelSmurfundefined 1 Reply Last reply
      0
      • SwaffelSmurfundefined Offline
        SwaffelSmurfundefined Offline
        SwaffelSmurf
        replied to Resxt on last edited by
        #3

        Resxt Thank you for the prompt reply!

        No, I am hosting it on my (headless) server (with IP 192.168.1.2) on the same network with port 6668 (so I am using connect 192.168.1.2:6668 to connect).

        Port forward is forwarding 6668 to local ip 192.168.1.2 on port 6668 (which my container also exposes).
        port_forward_overview.png
        I also tried the default port, but felt more comfortable changing it.

        I did not add this in the original post since I did not want to make it any more complicated :).

        Next step for me is probably running the container on the same PC where I'll be playing (not using the default port of course) to see if that eliminates the issue, which I'll be doing tomorrow.

        1 Reply Last reply
        0

        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Donate