Dr_Pippin

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by Dr_Pippin

  1. Can you share how you installed darkness falls in the container?
  2. You were 100% correct. I didn't know about steam's server browser, but that worked perfectly for me connecting over my local IP and my external IP from within my house.
  3. First off, I'd like to apologize for not saying thank you to ich777 first prior to asking for help. This is a great community and members like ich777's willingness to create such dockers and maintain them is very much appreciated. Thank you. Should the log not be longer? Mine gets to there and that's it, but the logs I'd seen other people post seemed to have much more in them. Even when I left the docker running overnight, there was nothing more added to the log. I changed to 1 as you directed and I'm still not able to connect. As for why I changed it (and why likely others have, too) is I misinterpreted the description for that value and thought that was how you made it a community server, which I didn't want. I thought public=community. I am attempting to connect to port 2457. If we pretend my server's static IP is 192.168.1.10, then I'm entering 192.168.1.10:2457 in Valheim when I click "Join IP". Is there anything else you can suggest I check or change? I will try deleting the docker and the appdata folders and starting over, but I'm not optimistic at this point that I'll have a different outcome. One more bit of info, when I attempt to connect I get a "connecting" screen for ~8 seconds, then I get a "disconnected" message. Not sure if that's unique to anything, or if that's the generic fail screen. EDIT: On my local network, if I ONLY enter the IP address (and not a port number) I can connect to the server. When I add a port number that's when I get can't connect and get the "disconnected" message.
  4. I have been struggling to get the Valheim docker working. I *think* I followed the setup guide properly, but I am unable to connect to my dedicated server on my home network. I've attached screenshot of my docker settings. I've also quoted a copy of the entire log, which appears to be showing something weird that I didn't seen anyone else mention (6th line from the bottom):
  5. Did you ever have any success with fixing this? I'm getting that error now and haven't found an answer yet.
  6. I am also having the "Not connected to D-Bus server" error in Krusader. Did you have any luck figuring out what is going on?
  7. I would be very interested in this if it worked for .zip files.
  8. My unRAID's log showed memory issues 3 days ago, so I powered down my server, removed every RAM module (8x4GB), cleaned all the contacts with rubbing alcohol, and reseated them. Now I received the call traces error this morning: I've included two diagnostic logs - one from February 8th when I had the memory issues, and one from February 11th when I had the call traces error Call traces error log: tower-diagnostics-20180211-1109.zip Memory error log: tower-diagnostics-20180208-1157.zip Screenshot of the memory errors from 3 days ago (February 8th):