Cool VL Viewer forum

View unanswered posts | View active topics It is currently 2024-03-28 23:48:24



Reply to topic  [ 20 posts ]  Go to page 1, 2  Next
Cannot log in to SL with latest Cool VL Viewer - time out 
Author Message

Joined: 2011-12-13 14:11:38
Posts: 186
Reply with quote
Hello,

I've been trying to log in to SL with the latest Cool VL Viewer version, and I'm almost systematically getting a time-out in the logs. The log is attached; the time-out happens at line 1825. The weird thing is, while supposedly waiting for the answer from the login service, my bandwidth consumption is as high as it can get (which is like 2.5 Mbps, my internet is slow). Is this normal? What is being downloaded during this time?

Also, I tried to log in with Firestorm, and it worked without any problem.

Any idea about what is going on here?

Thanks!


Attachments:
CoolVLViewer.zip [18.84 KiB]
Downloaded 64 times
2021-05-18 07:08:48
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
In last version, IPv6 was disabled in Curl and OpenSSL, because SL (and OpenSim) only use IPv4 and DNS requests are faster when an IPv6 request is not sent prior to the IPv4 one: it may however pose an issue if your system uses some weird IPv4 over IPv6 scheme and relies on IPv6 name resolution (with IPV4 requests filtered out).

Verify that IPv4 is enabled and fully functional on your network adapter and/or DNS cache.


2021-05-18 08:23:17
Profile WWW

Joined: 2011-12-13 14:11:38
Posts: 186
Reply with quote
Sorry, but that doesn't seem to be the problem: I deactivated everything related to IPv6 on my internet router and my network preferences: it didn't change a thing, I still couldn't log in, same time-out in the log.
So I deleted everything related to Cool VL Viewer v1.28.2.23, installed back version 1.28.2.22 and tried again: same thing, I still can't log in, same time-out message in the log.
And I still can log in without any problem with Firestorm...
Any other idea?


2021-05-18 11:16:39
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
ErikaThorkveld wrote:
So I deleted everything related to Cool VL Viewer v1.28.2.23, installed back version 1.28.2.22 and tried again: same thing, I still can't log in, same time-out message in the log.
And I still can log in without any problem with Firestorm...
Any other idea?
Then this is not something that changed in v1.28.2.23 and, from what I understand, v1.28.2.22 that worked fine for you does not work any more now ?... Aside from a configuration change in your system (a stateful firewall blocking the Cool VL Viewer ?), I do not see any other explanation.

To diagnose the issue, you could start a Wireshark instance and see what happens on your network interface when you log in with the viewer (use the "dns" filter in Wireshark, if too verbose)...


2021-05-18 11:55:24
Profile WWW

Joined: 2011-12-13 14:11:38
Posts: 186
Reply with quote
Henri Beauchamp wrote:
Then this is not something that changed in v1.28.2.23 and, from what I understand, v1.28.2.22 that worked fine for you does not work any more now ?...

Yep, v1.28.2.22 used to work indeed, and now it fails to log in, just as v1.28.2.23.
Henri Beauchamp wrote:
Aside from a configuration change in your system (a stateful firewall blocking the Cool VL Viewer ?), I do not see any other explanation.

I certainly didn't change anything myself, but there has been a few system updates since I last managed to log into SL successfully.
Henri Beauchamp wrote:
To diagnose the issue, you could start a Wireshark instance and see what happens on your network interface when you log in with the viewer (use the "dns" filter in Wireshark, if too verbose)...

I tried that, after reinstalling v1.28.2.23, and making sure there was hardly anything else running than Cool VL Viewer to avoid noise as much as possible in the log. But I'm completely out of my depth here, I don't know how to interpret what Wireshark tells me...
But at least, from what I can understand, it doesn't look like it's a DNS issue, since I can see quite a few of these lines in the Wireshark log with the 'dns' filter:
Code:
20   3.943615199   192.168.3.20   192.168.3.1   DNS   84   Standard query 0x06aa A login.agni.lindenlab.com

which are always followed by a line like this, one or two lines later:
Code:
21   4.167425193   192.168.3.1   192.168.3.20   DNS   204   Standard query response 0x06aa A login.agni.lindenlab.com CNAME login1.agni.secondlife.io CNAME login1-agni-lb-ext.secondlife.io A 52.36.80.160 A 54.201.128.226 A 44.235.11.83

That should mean that it works, right?
So is there something else I should look for in the Wireshark log? I tried to keep it as short as possible by starting the recording just before I pressed the 'Login' button and stopping it right after I got the error message, but the log ends up being 26MB in size and more than 28000 lines long anyway...

By the way, when I was trying to log in, it did succeed a couple of times. The login process felt longer than it usually is, but it finally worked, and once in world, everything was as usual. I also got one time where I managed to actually log in, but I got stuck at the 'Connecting to the grid' phase for a few minutes, then I got an error message telling me it wasn't working. I didn't keep the logs for these sessions though - I was trying to get one that was failing for Wireshark -, but I can try again if needed.

Sorry, all of this feels like shots in the dark, but I really have no clue about what could have changed on my system that could cause this issue...


2021-05-19 06:49:52
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
There should not be any "noise" on the network as long as you run *only* the viewer when it waits for login... Anyway, simply filter out the Wireshark log as indicated in my last message (type "dns" in the input line with the "Apply display filter..." hint).

But yes, the reply you captured indicates a proper DNS resolution, which would hint for blocked network data at a different step.

Did you try to log in from a different region too ? And what is the region you are trying to log in from (could be a server issue that, maybe, I could reproduce myself with my Av) ?

I have once seen weird login issues (but saw them happening too with LL's viewer in this case, though I did not try Firestorm), where I could not log in with my main avatar (but just fine with alts) in my home region (but just fine in another), and the support had to restart the latter for my Av to get "unlocked" in it.


2021-05-19 08:37:23
Profile WWW

Joined: 2011-12-13 14:11:38
Posts: 186
Reply with quote
OK, so I did try to log into another region, but no luck: got the same error. But I also tried to log in in the same region with an alt of mine I hadn't used for ages and lo & behold, it worked. I tried again several times, and it consistently worked without problem. So the problem is definitely related to my main av.
I'll try to log in with the official viewer to see if I get the error too, and if I do, I guess it'll be time to try to contact the Lindens...


2021-05-19 12:04:48
Profile

Joined: 2011-12-13 14:11:38
Posts: 186
Reply with quote
Nope, no error when I log in with the official viewer. So it's only Cool VL Viewer that doesn't want to log me in. Bummer... I just don't know what I can try next now...


2021-05-19 19:59:25
Profile

Joined: 2016-06-19 21:33:37
Posts: 337
Location: Columbus area, OH, USA
Reply with quote
This is a wild stab, but I recently had a similar problem and lo', it turned out that I had an old password .dat file in my settings folder. I believe Cool VL Viewer stopped using them long ago (not sure why I had one hanging around). Once I deleted the file, I was able properly log in again.


2021-05-19 20:29:41
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
ZaneZimer wrote:
This is a wild stab, but I recently had a similar problem and lo', it turned out that I had an old password .dat file in my settings folder. I believe Cool VL Viewer stopped using them long ago (not sure why I had one hanging around). Once I deleted the file, I was able properly log in again.
Those old files are totally ignored by the viewer: their presence or absence won't make any difference.


2021-05-19 20:47:55
Profile WWW
Display posts from previous:  Sort by  
Reply to topic   [ 20 posts ]  Go to page 1, 2  Next

Who is online

Users browsing this forum: No registered users and 32 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software.