Posted March 16, 2019 Hello and Well Met, New WU Admin here. Played WO for a while a few years ago, but new to WU. I have a quick question... Today, I installed Ago's Server-ModLauncher-0.42, Client-ModLauncher-0.10.1, and a few select mods to get my feet wet with running a Modded server. Everything went fine without a hiccup and I was able to log in and test things out nicely. Everything until my friends tried to log into the server this evening (we've been playing on the server together for a few weeks now without a problem). When trying to log in, they would never connect - the connection would time out. I ended up disabling all the mods (love JPWM_ModGUIManager by the way) and starting the server like normal through the Steam GUI instead of using Modlauncher.bat. Then they were both able to connect as usual. Can anyone tell me what I did wrong? Does everyone who joins a Modded server have to install Client-ModLauncher or do something special? Do I need to do something special? Thanks in advance - Xil Share this post Link to post Share on other sites
Posted March 16, 2019 Could you list what mods you are using on your server? Are you able to connect with a non modded client? Are they able to connect with a modded client? Share this post Link to post Share on other sites
Posted March 16, 2019 (edited) 2 hours ago, Retrograde said: Could you list what mods you are using on your server? Are you able to connect with a non modded client? Are they able to connect with a modded client? Thanks for your reply Retrograde, I modded my Client and I was able to connect and play/test on my Modded Server just fine. However, I am playing on the same machine that the server is running on. When my friends try to connect to the modded server, their connections always time out. This is happening to both of them (one has a modded clients and the other is un-modded). If I launch the server through the Steam Client (instead of modlauncher.bat), everyone is able to connect to the server with modded and unmodded clients just fine. But of course, this means the server is not using the mods. I have the following Mods downloaded and installed in my Mods folder (most of which came with Server-ModLauncher), but they are currently disabled using JPWM_ModGUIManager to disable them (even JPWM_ModGUIManager is currently disabled). I have listed the property files that have been renamed ".disabled" beside the mods below. Announcer - announcer.disabled Bagofholding - bagofholding.disabled creatureagemod - creatureagemod.disabled cropmod - cropmod.disabled fixguards - fixguards.disabled harvesthelper - harvesthelper.disabled hitchingpost - hitchingpost.disabled httpserver - httpserver.disabled inbreedingwarning - inbreedwarning.disabled JPWM_ModGUIManager - JPWM_ModGuiManager.disabled scriptrunner - scriptrunner.disabled serverfixes - serverfixes.disabled servermap - servermap.disabled serverpacks - serverpacks.disabled spellmod - spellmod.disabled survival - survival.disabled TreasureHunting - TreasureHunting.disabled Edited March 16, 2019 by Xilanthus Share this post Link to post Share on other sites
Posted March 17, 2019 (edited) I got it working. I moved the server off my Windows box and onto my Linux box. Everything works fine now. I am having difficulty setting up the Wurm Dedicated Server as a Service on Ubuntu 14.04. If anyone has any hints as to how to do this, it would be most appreciated. Thanks, Jim Edited March 17, 2019 by Xilanthus Share this post Link to post Share on other sites
Posted March 17, 2019 sounds to me like firewall issues, if you can connect on same machine but others trying to connect can't then more likely firewall than a mod issue. Still possible it is a mod of course but my guess would be firewall, a lot of people have issues with getting that part set up. Share this post Link to post Share on other sites
