After connecting to a SDL wallet, normally if one of the SDL servers doesn't work it connects to a randomly chosen server which was introduced some months ago and it worked perfectly fine.
However if you restore the wallet, for example, and one of the server that was chosen in setting is offline now it won't try to connect to another one, but instead will throw a Unexpected compression flag: 60 instead.
@oDinZuyou might want to have a look at your SDL server, because mine was also down very recently.
By the time I finished my writing your server got back online.
@duke now I'm confused because the reason for that might be a sticky server option that is enabled in my config file, I remember it should be in .silentdragonlite folder but it is not there, but only the wallet.dat and debug.log file.
@duke that issue was created because if you open your "normal" SDL it connects to another server even if you set up an inactive one from your settings, since dragon.nyami.org is online now I chose lite.hush.is that is not currently maintained by anyone. @hyp3r you can host your own SDL server on lite.hush.is, I will help.
So the idea is that if you remove .silentdragonlite folder but the inactive server is still in settings the choose-on-random feature will not work for restoring and creating a new wallet.
The following is what we normally see while connecting to SDL in case the server that was randomly chosen or set in settings was inactive. @hyp3r
doAutoConnect server= "https://lite.hush.is"
connect error: Connection refused (os error 111)
getRandomServer
Checking if lite server "https://lite.hush.land" is a alive, try= 0
doAutoConnect : Successfully connected to random server: "https://lite.hush.land"
And if we remove .silentdragonlite and start from scratch leaving inactive server in settings.
doAutoConnect server= "https://lite.hush.is"
litelib_process_response : Error: transport error: error trying to connect: tcp connect error: Connection refused (os error 111)
After connecting to a SDL wallet, normally if one of the SDL servers doesn't work it connects to a randomly chosen server which was introduced some months ago and it worked perfectly fine.
However if you restore the wallet, for example, and one of the server that was chosen in setting is offline now it won't try to connect to another one, but instead will throw a `Unexpected compression flag: 60` instead.
```
doAutoConnect : server= "https://dragon.nyami.org"
litelib_process_response : Error: grpc-status: Internal, grpc-message: "Unexpected compression flag: 60"
```
After changing the server **manually** it worked.
@oDinZu ~~you might want to have a look at your SDL server, because mine was also down very recently.~~
By the time I finished my writing your server got back online.
@duke now I'm confused because the reason for that might be a sticky server option that is enabled in my config file, I remember it should be in `.silentdragonlite` folder but it is not there, but only the wallet.dat and debug.log file.
@duke that issue was created because if you open your "normal" SDL it connects to another server even if you set up an inactive one from your settings, since dragon.nyami.org is online now I chose lite.hush.is that is not currently maintained by anyone. @hyp3r you can host your own SDL server on lite.hush.is, I will help.
So the idea is that if you remove `.silentdragonlite` folder but the inactive server is still in settings the choose-on-random feature will not work for restoring and creating a new wallet.
The following is what we normally see while connecting to SDL in case the server that was randomly chosen or set in settings was inactive. @hyp3r
```
doAutoConnect server= "https://lite.hush.is"
connect error: Connection refused (os error 111)
getRandomServer
Checking if lite server "https://lite.hush.land" is a alive, try= 0
doAutoConnect : Successfully connected to random server: "https://lite.hush.land"
```
And if we remove `.silentdragonlite` and start from scratch leaving inactive server in settings.
```
doAutoConnect server= "https://lite.hush.is"
litelib_process_response : Error: transport error: error trying to connect: tcp connect error: Connection refused (os error 111)
```
@onryo does this affect most users or only those doing weird things? I am still not sure what your exact bug report is. This is not a bug if you had stickyServer=1. It might be the case that if a server is up, but misconfigured, the code doesn't try another server properly.
@onryo does this affect most users or only those doing weird things? I am still not sure what your exact bug report is. This is not a bug if you had `stickyServer=1`. It might be the case that if a server is up, but misconfigured, the code doesn't try another server properly.
After connecting to a SDL wallet, normally if one of the SDL servers doesn't work it connects to a randomly chosen server which was introduced some months ago and it worked perfectly fine.
However if you restore the wallet, for example, and one of the server that was chosen in setting is offline now it won't try to connect to another one, but instead will throw a
Unexpected compression flag: 60instead.After changing the server manually it worked.
@oDinZu
you might want to have a look at your SDL server, because mine was also down very recently.By the time I finished my writing your server got back online.
@duke now I'm confused because the reason for that might be a sticky server option that is enabled in my config file, I remember it should be in
.silentdragonlitefolder but it is not there, but only the wallet.dat and debug.log file.@duke that issue was created because if you open your "normal" SDL it connects to another server even if you set up an inactive one from your settings, since dragon.nyami.org is online now I chose lite.hush.is that is not currently maintained by anyone. @hyp3r you can host your own SDL server on lite.hush.is, I will help.
So the idea is that if you remove
.silentdragonlitefolder but the inactive server is still in settings the choose-on-random feature will not work for restoring and creating a new wallet.The following is what we normally see while connecting to SDL in case the server that was randomly chosen or set in settings was inactive. @hyp3r
And if we remove
.silentdragonliteand start from scratch leaving inactive server in settings.@onryo does this affect most users or only those doing weird things? I am still not sure what your exact bug report is. This is not a bug if you had
stickyServer=1. It might be the case that if a server is up, but misconfigured, the code doesn't try another server properly.@onryo yeah, I still don't have dragon.nyami.org lightwalletd running yet. lite.nyami.org is up and running though. Sorry about the misunderstanding.
Closing because the issue is not clear. Even I do not understand what I meant. 😀