Page 1 of 1

local uberserver, can't register

Posted: 08 Sep 2018, 13:03
by constatinus
I just started uberserver (fedora 28 x86_64 ), with and without virtualenv, and this is the same result i get when i try to register from springlobby:

2018-09-08 11:19:12 INFO Protocol._new:208 [1] Client connected from 192.168.0.14:2367
2018-09-08 11:19:12 INFO Protocol._remove:235 [1] disconnected from 192.168.0.14: Connection was closed cleanly.

and sometimes it is:

2018-09-08 11:19:12 INFO Protocol._new:208 [3] Client connected from 192.168.0.14:2369
2018-09-08 11:19:13 INFO Protocol._remove:235 [3] disconnected from 192.168.0.14: Connection to the other side was lost in a non-clean fashion: Connection lost.

I tried from different springlobbys on different machines, when pressing register and saying yes ( yes,no or cancel produce the same result ) the error in springlobby is:
[12:55:53] ** Server ** Disconnected from server, chat closed.

This a part of the server.log from the beginning:

2018-09-08 11:15:54 INFO DataHandler.detectIp:425 Detecting local IP:
2018-09-08 11:15:54 INFO DataHandler.detectIp:427 192.168.0.18
2018-09-08 11:15:54 INFO DataHandler.detectIp:429 Detecting online IP:
2018-09-08 11:15:54 INFO DataHandler.detectIp:437 **********************
2018-09-08 11:15:54 INFO server.<module>:39 Starting uberserver...
2018-09-08 11:15:54 INFO server.<module>:54 Using 25 client handling thread(s).
2018-09-08 11:15:55 INFO ChanServ.__init__:23 [0] <ChanServ> logged in (access=ChanServ)
2018-09-08 11:16:09 INFO Protocol._new:208 [1] Client connected from 192.168.0.14:2321
2018-09-08 11:16:09 INFO Protocol._remove:235 [1] disconnected from 192.168.0.14: Connection was closed cleanly.
2018-09-08 11:16:09 INFO Protocol._new:208 [2] Client connected from 192.168.0.14:2322
2018-09-08 11:16:09 INFO Protocol._new:208 [3] Client connected from 192.168.0.14:2323
2018-09-08 11:16:09 INFO Protocol._remove:235 [2] disconnected from 192.168.0.14: Connection was closed cleanly.
2018-09-08 11:16:10 INFO Protocol._remove:235 [3] disconnected from 192.168.0.14: Connection to the other side was lost in a non-clean fashion: Connection lost.

Re: uberserver can't register

Posted: 09 Sep 2018, 09:05
by Silentwings
Which version(s) of uberserver and SL did you use?

What happens if you try to register the same username twice?

Re: uberserver can't register

Posted: 09 Sep 2018, 10:53
by constatinus
Silentwings wrote: 09 Sep 2018, 09:05 Which version(s) of uberserver and SL did you use?

What happens if you try to register the same username twice?
0.266 from windows/192.168.0.14 and 0.264-79-gc6c036d58 from host on linux ( compiled ), gives the same result

latest uberserver, af3b0b2 ( even tried older ones! )

As shown in the log, i there were two ( or maybe 3? ) attempts to register. Just as if nothing has happened, springlobby redirects me again to the tab with the register button and says Disconnected from server,chat closed. Sometimes on windows it, after i click yes on the certificate verification, it spams infinite tabs of the verify certificate window until SL crashes.

Re: uberserver can't register

Posted: 09 Sep 2018, 16:41
by Silentwings
For now, you'll need to downgrade your Springlobby from 0.266 to 0.260, and connect to your local uberserver without using TLS, because of this bug https://github.com/springlobby/springlobby/issues/828

Re: local uberserver, can't register

Posted: 09 Sep 2018, 17:21
by abma
@constatinus:

please try again with springlobby >=0.267, should be fixed there.

Re: uberserver can't register

Posted: 09 Sep 2018, 17:44
by constatinus
Silentwings wrote: 09 Sep 2018, 16:41 For now, you'll need to downgrade your Springlobby to 0.260, and conect to your local uberserver without using TLS, because of this bug https://github.com/springlobby/springlobby/issues/828

http://springlobby.info/windows/SpringLobby-0.260.exe
Thanks, now it works!

btw, i can't register (but can logjn ) with tls on because springlobby thinks that im trying to login ( as seen by the log of uberserver ).

Re: local uberserver, can't register

Posted: 09 Sep 2018, 19:06
by constatinus
abma wrote: 09 Sep 2018, 17:21 @constatinus:

please try again with springlobby >=0.267, should be fixed there.
Oops, looks like i didn't see your post before posting my latest!
Works :)