Quote:Error response from keygen server: Not allowed.

(02-18-2013, 01:42 AM)Mr. Bougo Wrote: The keygen will only generate one key per IP address per week, could that be it? If you're using -sessionid to run multiple instances of the dedicated server, the server keys are unique for each sessionid used, so make sure you don't constantly change that.

(02-18-2013, 01:59 PM)Mr. Bougo Wrote: The keys are stored in ~/.xonotic/ (for example ~/.xonotic/key_0.d0si for an instance without a session id). Are you sure they weren't (re)moved and that they are actually accessible?

If you don't have a key to use or another IP address to use to generate a key, then yes, you'll have to wait for a week to get a new one.

I don't know what specifically causes the error to appear though. I don't know if it's an actual refusal from the keygen server to generate a key, or if it can also be a consequence of the key server not being reachable. Check the server startup log, if all is well you'll see "Loaded private ID key_0.d0si for key_0.d0pk" or something similar.

(02-18-2013, 02:30 PM)Mr. Bougo Wrote: Eh, why would you remove them? Now you will have to wait a week, that's for sure. You should have looked for that line that I mention in my last paragraph.

(02-18-2013, 04:33 PM)Mr. Bougo Wrote: Oh okay. Come back next week then! And the week after for your second server!

(02-19-2013, 12:55 AM)Mr. Bougo Wrote: Eh, a keyless server works just fine. The only problem is that it can't send stats to XonStat.

(02-19-2013, 02:17 PM)Mr. Bougo Wrote: I don't know. Can you please check for the key loading line that I mentioned in post #4? Tell me what instances have this line and what instances have the keygen server error.

Running each instance as a different user will make no difference, except that managing them will give you headaches.

(02-19-2013, 05:17 PM)Mr. Bougo Wrote: Oh okay, so you have a key but it's not signed. No idea why.

I really don't know what's supposed to happen. I would have to check the source code for that, but I don't know when I'll have time for that.

1. New instance, keygen agrees to sign
   
   Code:

   Loaded public key key_0.d0pk (fingerprint: Xon//KssdlzGkFKdnnN4sgg8H+koTbBn5JTi37BAW1Q=)
Loaded public key key_15.d0pk (fingerprint: TEST5XYWfX09i5/ekwTd1cJkalvnR3A1AvBlFPijhE0=)
Generated private ID key_0.d0pk (public key fingerprint: vyWZEtxTY/0BQ2extPlVM2bWG3EnngH93fziMXk3xoQ=)
Saved unsigned key to key_0.d0si.temporary
Signature generation in progress...
(...)
Received signature for private ID key_0.d0pk (public key fingerprint: vyWZEtxTY/0BQ2extPlVM2bWG3EnngH93fziMXk3xoQ=)
Saved to key_0.d0si.temporary
2. New instance, keygen refuses to sign because I already had a key generated in the past 7 days
   
   Code:

   Loaded public key key_0.d0pk (fingerprint: Xon//KssdlzGkFKdnnN4sgg8H+koTbBn5JTi37BAW1Q=)
Loaded public key key_15.d0pk (fingerprint: TEST5XYWfX09i5/ekwTd1cJkalvnR3A1AvBlFPijhE0=)
Generated private ID key_0.d0pk (public key fingerprint: ub1CpAZIPwmKGRlxCE6thlprkvsagcI0ooFglAINS+Q=)
Saved unsigned key to key_0.d0si.temporary2
Signature generation in progress...
(...)
Error response from keygen server: Not allowed
3. Old instance, key already signed
   
   Code:

   Loaded public key key_0.d0pk (fingerprint: Xon//KssdlzGkFKdnnN4sgg8H+koTbBn5JTi37BAW1Q=)
Loaded private ID key_0.d0si.temporary for key_0.d0pk (public key fingerprint: vyWZEtxTY/0BQ2extPlVM2bWG3EnngH93fziMXk3xoQ=)
Loaded public key key_15.d0pk (fingerprint: TEST5XYWfX09i5/ekwTd1cJkalvnR3A1AvBlFPijhE0=)
there is already a signed private key for 0
4. Old instance, key not signed
   
   Code:

   Loaded public key key_0.d0pk (fingerprint: Xon//KssdlzGkFKdnnN4sgg8H+koTbBn5JTi37BAW1Q=)
Loaded private ID key_0.d0si.temporary2 for key_0.d0pk (public key fingerprint: ub1CpAZIPwmKGRlxCE6thlprkvsagcI0ooFglAINS+Q=)
NOTE: this ID has not yet been signed!
Loaded public key key_15.d0pk (fingerprint: TEST5XYWfX09i5/ekwTd1cJkalvnR3A1AvBlFPijhE0=)
Only need a signature for an existing key...
Signature generation in progress...
(...)
Error response from keygen server: Not allowed
5. Old instance, keygen previously refused but now accepts because 7 days have passed
   (I can't reproduce this one right now)
   

1. The IP is found in one of the following dns blacklists (dnsbl): torexit.dan.me.uk, aspews.ext.sorbs.net
   
2. The IP appears in the global banlist on rm.endoftheinternet.org (which is down so that's not it)
   
3. A signature request has been recorded from that IP into the local database in the past 7 days
   

(06-13-2013, 10:48 AM)end user Wrote: Ok so ran into another issue.

I noticed that if i change git branches, compile and run the server with the same sessionid i get the keygen error. Is this normal when changing branches? If so is there a way to merge the server stats from the previous server to the new one like with player stats?

(06-13-2013, 03:13 PM)Mr. Bougo Wrote:

(06-13-2013, 10:48 AM)end user Wrote: Ok so ran into another issue.

I noticed that if i change git branches, compile and run the server with the same sessionid i get the keygen error. Is this normal when changing branches? If so is there a way to merge the server stats from the previous server to the new one like with player stats?

That doesn't seem normal to me. Your server has its files in ~/.xonotic, right, not in the clone?

You should keep a backup of your server keys anyway. If you notice keygen errors, restore the keys from backup.

If you want to merge the server in the stats, post in the relevant thread, same thing as player IDs.