Server Help No AdmLogins, No SRV password after update

After update string no more available in cfg files.

Trying to get string from wiki - but dont work.

Nice update..

Anarchy Update...

P.S.

Win 2008r2, x64 server

 

Trying to figure out how

Code:

"serverUsers" : {  }

works.

 

Yeah... me too. Anyone figured out how to use the "serverUsers" config yet? Trying to work it out myself, will post if I get anywhere with it. An official word on how this works would be nice.

As for admin, perhaps its condensed now. Maybe there's an admin extension you add onto the usernames or something?

 

i have same problem.
set a "serverUsers", but not working section.

Code:

Info: bind 
Info: TcpServer listening on: 
Info: UniverseServer: Shutting down world CelestialWorld:-798953586:408947670:-207254350:3:4 due to inactivity
Info: accept from 
Info: UniverseServer: Connection received from: 
Info: UniverseServer: Sending Handshake Challenge
Error: UniverseServer: error during worker pooled job: (VariantException) Cannot call get with key on Variant type string, must be Map type
./starbound_server(_ZN4Star13StarExceptionC2ESs+0x75) [0xeb45e5]
./starbound_server(_ZN4Star16VariantException6formatIINS_6StringEEEES0_PKcDpRKT_+0x31) [0xe90581]
./starbound_server(_ZNK4Star7Variant3getERKNS_6StringES0_+0xf0) [0xe8d8f0]
./starbound_server(_ZNK4Star7Variant4tgetIbEET_RKNS_6StringES2_+0x42) [0xe923f2]
./starbound_server() [0x796d83]
./starbound_server() [0xeadbdc]
./starbound_server(_ZN4Star10WorkerPool12WorkerThread3runEv+0xf5) [0xeae295]
./starbound_server(_ZN4Star10ThreadImpl9runThreadEPv+0x1a) [0xebca3a]
/lib64/libpthread.so.0() [0x3f63c079d1]
/lib64/libc.so.6(clone+0x6d) [0x3f638e88fd]

next, get local server win7 64bit error log.

Code:

 Info: bind 
Info: TcpServer listening on: 
Info: accept from 
Info: UniverseServer: Connection received from: 
Info: UniverseServer: Sending Handshake Challenge
Error: UniverseServer: error during worker pooled job: (VariantException) Cannot call get with key on Variant type string, must be Map type
  VariantException::VariantException(string)
  Variant::get(String, Variant)
  Variant::getBool(String, bool)
  UniverseServer::queueConnection(shared_ptr<NetSocket>, Maybe<HostAddress>)::{lambda()#1}::operator()()
  _Function_handler<void (), WorkerPool::addWork(function<void ()>)::{lambda()#1}>::(_Any_data)
  WorkerPool::WorkerThread::run()
  ThreadImpl::runThread(void*)
  BaseThreadInitThunk
  RtlInitializeExceptionChain
  RtlInitializeExceptionChain

 

I've been looking but I can't find any information at all about the changes to administrative login. Kind of a big change not to release information about how to administrate yourself or others after an update...

 

metadept is making a blog post about this shortly.
If you're too antsy, here's the example he posted.

 

Ok, nice But what with the server password?

UPD.

I try, but not working.


"serverUsers" : {
"DiWorm" : {
"admin" : true,
"password" : "xxx"
},
"Hylotl" : {
"admin" : true,
"password" : "xxx"
},
"Testbot" : {
"admin" : true,
"password" : "xxx"
}
},


in connect menu i do

login: DiWorm
pass: xxx

connect and try /admin - No priv...[DOUBLEPOST=1424195189][/DOUBLEPOST]

not working for me...

 

It's working for me. Double check your syntax and make sure:

Code:

  "allowAdminCommands" : true,
  "allowAdminCommandsFromAnyone" : false,
  "allowAnonymousConnections" : true,

assuming you want users without an account to be able to get in.

 

Thank you. It works, finally )

 

Still not work to me.

But I find way to fix this.

"allowAnonymousConnections" : false,

create admin accounts and "player" account = server with password and admins..

 

Thanks much for the link - I had passwords working, then mysteriously stopped after updating this morning and I was pulling my hair out. Turned off anonymous logins and made accounts for myself and a friend, should do the trick for now.

 

So there's no way to keep the server open to random players and be able to admin yourself?
NVM, you just make the account for yourself and keep other options as normal.

There's also a bunch of new RCON settings I can't find any info about.

Code:

  "rconServerBind" : "*",
  "rconServerPassword" : "",
  "rconServerPort" : 21026,
  "rconServerTimeout" : 500,

 

thanks Norban. you given code is work fine.

Code:

  "allowAdminCommands" : true,
  "allowAdminCommandsFromAnyone" : false,
  "allowAnonymousConnections" : true,
  "serverUsers" : {
      "user1" : {
          "admin" : true,
          "password" : "user1password"
      },
      "user2" : {
          "admin" : false,
          "password" : "user2password"
      },
  }

 

I use a clanforge server, and I can't get my admin privileges back. And the server had a game password that worked until the last patch. Changing important stuff like this without informing us is most likely a huge mistake by Chucklefish. It made my server useless IMO.

 

What do you mean they didn't inform us?
http://playstarbound.com/february-17-server-configuration-changes/

 

I mean that Clanforge clearly did not get that info. And wasn't that info published rather late, or am I wrong?

 

It was published right on Feb 17 when the patch hits. I don't think Clanforge is affiliated with Chucklefish either.

 

That's going to be confusing for people using the service since it says "Multiplay Official Server Host" on the Starbound front page and Multiplay is part of Clanforge.

 

I'm not sure of the exact timing, but it seems that blog post wasn't published until at least a few hours after the patch came out. I went into work late yesterday thanks to a snowstorm, I was messing around with my server, noticed there was an update - and then wasted part of the next couple hours wondering why the heck my config file was suddenly replaced and passwords stopped working. A comment at the top of the config file, a "READ THIS" file put in the server directory, etc....*something* would have been helpful rather than making people wonder until whoever gets around to writing a blog post.

Don't get me wrong, i'm not angry or anything, but it was definitely annoying for a while

 

There was no officially released information for hours after the update went live. The update broke out server, we updated and realized there were changes to the configuration file. I searched everywhere but the only information I found relating to the admin login change was people asking about it until sometime around mid afternoon EST. That sort of thing is server-breaking and they really should have anticipated how serious a change that is and how badly people would want to know that information before the change went live. Having your method for logging in as staff on your server broken and then not knowing how to fix that for hours is really not ideal. The way in which the front page update about it was worded only exemplifies the notion that they don't really take online as seriously as we need them to. 'and since several users have asked about it, here’s a brief explanation.' That isn't why they should post information like that, they should post it because it's NECESSARY. That data should have been released publicly before the update went live so we could be prepared and not have our servers be vulnerable until they decided to say something about the alteration.