1. Hiya.

    Just updated and started one server up, but the others can't be started. I'm getting a pop-up saying 'another instance is already running'

    Help me!... please.

    Image here

    Thank you.
     
  2. Also having this problem, might just have to use separate rust installs for now as a workaround. This might cause worse performance though
     
  3. Yeah, I'm really hoping this is just a small bug.
    [DOUBLEPOST=1528493398][/DOUBLEPOST]
    I've just tried that, same error.
     
  4. The same problem, anyone solution????
     
  5. Yep, this seems to be the issue. Can't run more than one server out of the same folder. Gonna have to do separate setups for each server. I want to punch myself in the face.
     
  6. Hello,

    I get the following error since the last update.
    I hope someone can help me? If you need more information, please let me know.
    2018-6-9_1-2-53_1528498973661235992.png
     
  7. Unfortunately we need to wait until the developers will fix this bug.
     
  8. So is it a bug of rust?
     
  9. same issue here
     
  10. i also have tis problem -.-
     
  11. My 2 servers run just fine, Is it cause ive 2 diffrent maps maybe?
     
  12. Windows or Linux?
     
  13. Guys, you can do a trick with file and folder names
    Make a copy of RustDedicated.exe and RustDedicated_Data folder
    Then rename it whatever you like
    I`m added "_" symbol in the copyed files and folders
    Don`t forget to change in your bat file new exe file name
     

    Attached Files:

  14. Yes but this is not like it should work is it :)
     
  15. Since Friday's update (6/8) I am no longer able to run multiple servers on one machine. I used to be able to use one installation, and have several batch files to start different servers, just changing port and server identity, but now I simply get an error window that shows:
    Code:
    Fatal Error
    Another instance is already running
    I have already tried using a different directory the other server, but it gives me the same problem.
     
  16. This seems to work for now
     
  17. That was always the way to go. This is not a bug but built in to prevent errors.
     
  18. Never happened before, so it must be from the update.
     
  19. How long will the problem be solved ? To warn the users of the server ?
     
  20. @Wulf Do you have any input on this? Do you know what's causing it? etc. Thanks.