• Posts

  • Joined

  • Last visited

Posts posted by Durin

  1. 27 minutes ago, ich777 said:

    What is the exact issue, this is nothing to worry about...

    As the warning itself says, it's a warning not an error.


    I can not reproduce this issue, a log output would be very helpful, this is the startup of a fresh installed container:

    I tried with a fresh install now and I can no longer reproduce the error, I guess there was something wrong with the other deployment.


    I still think you should remove the "public" property and clearly state that password is required however! :)

  2. 3 minutes ago, schuu said:

    Is it possible for Valheim to be put behind a reverse proxy like swag so I can use a domain to join rather then wan ip address? sometimes friends can not join via the community list as it does not show, and i do not want to give out my public ip address to people to add to the steam server list.

    I guess this is not the right thread for questions like this, but as far as I know there is no way to join a Valheim server with a domain. The only way is to add it as a favorite server in steam but then the resolved IP will show anyway.

    • Thanks 1
  3. I have issues with the Valheim docker container when starting without the "validate installation" set to true, the container won't start. If I enable "validate installation" it works but it downloads some dependency every time. As far as I can see from the logs the problem is a missing SDL dependency. This is the message I see:

    sdl Warning: failed to init SDL thread priority manager: SDL not found


    I have experimented with the Docker image and the solution I found was to add the following:

    RUN dpkg --add-architecture i386
    RUN apt-get update && \
    	apt-get -y install --no-install-recommends lib32gcc1 screen file libc6-dev unzip libsdl2-2.0 libsdl2-2.0-0:i386 && \
    	rm -rf /var/lib/apt/lists/*

    Specifically those two: "libsdl2-2.0 libsdl2-2.0-0:i386"


    Do you think you could add this to the image? This will also make the container start faster since it does not have to resolve those missing dependencies at runtime.

  4. 45 minutes ago, ich777 said:

    When I created the container for this I stumbled across this, eventually something has changed lately with a update...


    But I've connected with public set to '0' and no password set and it worked.

    I really wanted to find out how to start the server without password so... I checked the source code, and I can confirm that as the code is now, there is now way to start the server without a valid password, and "public" is hardcoded to "true". :)

  5. 7 minutes ago, ich777 said:

    Nice, then please tell them to remove this from their installation instructions that ship with the dedicated servers... :D

    But one thing that I've discovered is that when public is set to '1' and no password is entered the server won't start but if you set public to '0' you can actually leave the password empty and connect to it.

    I will leave it in because it hurts no one by now... :D

    Are you sure about this? I have tried that several times because I do not want to have a password on the server, but the server does not start when I do that! All sources I have found says that password is required...