Author |
Message |
ProfAitch
Joined: 2021-10-06 18:03:51 Posts: 17
|
I am running version 43 in Windows 7, and up until two days ago had no issues logging into FireAndIce grid.
Starting yesterday, the login page shows the last-logout screen with a black central message "waiting for seed" and goes no further.
Quitting and trying again produces the "you seem to be already logged in..." message, and trying again usually works.
Today even after 8 attempts it still gave the waiting for seed message.
I finally cured it by logging into SecondLife, which it did instantly, then logging out and logging into FireandIce, which is also did instantly.
Is there a better workaround?
|
2021-10-06 19:17:20 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5545
|
This kind of issue is usually a network related one (bad routing, for example) or a server issue.
The "waiting for seed" message happens when the viewer tries and connects to the login region (i.e. the login to the grid itself has already been successfully performed): the server of the region in question could be having network issues...
There also has been the issue with the Let's Encrypt root certificate that went deprecated a few days ago (maybe the Open Sim grid is still using it for its own certificate, based on the deprecated root certificate one ?... They would then need to update their Let's Encrypt certificate).
A log file would help figuring out what is going wrong, but I very much doubt it is viewer-related...
|
2021-10-06 20:23:04 |
|
|
ProfAitch
Joined: 2021-10-06 18:03:51 Posts: 17
|
Ok, I'll wait until the next time it sticks and save the log.
I agree it seems to coincide with the lets-encrypt saga, but Singularity, Dayturn, Firestorm all connected Ok so I'm less certain it's a certificate issue.
ETA: I have a log file containing the fail and my subsequent quit:
Where should I send the log file?
Last edited by ProfAitch on 2021-10-06 20:43:39, edited 1 time in total.
|
2021-10-06 20:40:03 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5545
|
On the contrary... They use the old LL certificate file, unlike my viewer (which always adopts LL's latest CA bundle). You may attach it (after zipping or taring it) to a forum message in this thread.
|
2021-10-06 20:42:45 |
|
|
ProfAitch
Joined: 2021-10-06 18:03:51 Posts: 17
|
Ok, attached log file
|
2021-10-06 20:45:33 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5545
|
The relevant log lines are here: Definitely a network issue (no reply or bad reply from the server): nothing actionable viewer-side, I'm afraid...
|
2021-10-06 20:49:20 |
|
|
ProfAitch
Joined: 2021-10-06 18:03:51 Posts: 17
|
Ok, thank you very much for your oversight, I'll go with the workaround of logging into SL first for the time being and ask the grid owner if they're dealing with the lets-encrypt issue.
|
2021-10-06 20:59:09 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5545
|
To rule out the certificate issue you could also try and replace the ca-bundle.crt file (in the app_settings/ sub-directory of the Cool VL Viewer installation directory) with an older one from the other viewers (which might be present inside another sub-directory for them)...
|
2021-10-06 21:37:10 |
|
|
ProfAitch
Joined: 2021-10-06 18:03:51 Posts: 17
|
I might have found the reason for this little spate of errors, I had downloaded version 43 but was trying to log in with 42. (My habit is to always login with the last working version to get the region admin done before upgrading just in case the newer version needs a bit of tweaking).
I've had no subsequent problems.
|
2021-10-09 14:50:25 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5545
|
There is strictly no difference between those two versions, aside from a fixed rendering issue in 1.28.2.43 (which got no impact whatsoever on login/connections)... Which tends to demonstrate that it was just a transitory network/routing issue...
|
2021-10-09 16:22:24 |
|
|