Jump to content

MBeatrix

Resident
  • Posts

    677
  • Joined

  • Last visited

Posts posted by MBeatrix

  1. https://status.secondlifegrid.net/incidents/5j0rbt0s8j4t

    Besides Germany and Denmark, you can add Portugal.

    This has been a recurring issue for the last month or so. Right now, and as it always happens, I can login my alt account but not my main, although both accounts use the same PC, viewer and broadband internet connection.

    I already changed  the DNS servers but the issue persists.

    Due to what has been happening, I'm starting to suspect that something is very wrong with the SL login system. I mean it. Really.

    [EDIT] ping to login.agni.lindenlab.com is consistsent, no failures; traceroute shows normal results.

    [EDIT 2] This feels like I'm talking to myself. I finally logged in my main account but I'm still feeling quite aggravated by the whole thing. Last Saturday, I could only DJ at a club using my alt account. Can someone who knows more explain me why one account logs in just fine and the other can't? Sometimes, according to my timings, the issue only has disappeared next morning, "magically".

  2. Can't login any of my accounts. I changed the DNS servers but the problem persists.

    I can access my web dashboard, though.

    [EDIT] Of course that the message I get is the usual generic one, and there's nothing on the GSP about it so far.

    image.jpeg.e933c39441714d10d10597f08b25f11a.jpeg

  3. 13 hours ago, Mariposa Rayna said:

    As I've already commented, I'm able to log in using an alt, but not on my main profile. It's been going on for the last 2 days. I was able to log in the first day, and was inworld for a good 3 or 4 hours before logging. I came back to it yesterday, and today and still not able to log in on the main profile with the error message everyone else has already mentioned. Here's my info:

    Firestorm 6.6.17 (70368) Dec 10 2023 18:36:33 (64bit / SSE2) (Firestorm-Releasex64) with Havok support
    Release Notes

    CPU: AMD Ryzen 7 2700 Eight-Core Processor           (3200 MHz)
    Memory: 16335 MB (Used: 376 MB)
    Concurrency: 16
    OS Version: Microsoft Windows 10 64-bit (Build 19045.4046)
    Graphics Card Vendor: NVIDIA Corporation
    Graphics Card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
    Graphics Card Memory: 4096 MB

    Windows Graphics Driver Version: 31.0.15.3623
    OpenGL Version: 4.6.0 NVIDIA 536.23

    RestrainedLove API: RLV v3.4.3 / RLVa v2.4.2.70368
    libcurl Version: libcurl/7.54.1 OpenSSL/1.1.1l zlib/1.2.11.zlib-ng nghttp2/1.40.0
    J2C Decoder Version: KDU v8.4.1
    Audio Driver Version: FMOD Studio 2.02.18
    Dullahan: 1.12.4.202209142021
      CEF: 91.1.21+g9dd45fe+chromium-91.0.4472.114
      Chromium: 91.0.4472.114
    LibVLC Version: 3.0.16
    Voice Server Version: Not Connected
    Settings mode: Firestorm
    Viewer Skin: Firestorm (Grey)
    Window size: 1840x855 px
    Font Used: Deja Vu (96 dpi)
    Font Size Adjustment: 0 pt
    UI Scaling: 1
    Draw distance: 512 m
    Bandwidth: 1450 kbit/s
    LOD factor: 3.625
    Render quality: Medium-High (4/7)
    Advanced Lighting Model: No
    Texture memory: Dynamic (3360 MB min / 10% Cache / 10% VRAM)
    Disk cache: Max size 6208.0 MB (11.0% used)
    Built with MSVC version 1937
    March 13 2024 14:07:11 SLT

    Besides the DNS issue that had been happening some time ago, it may also be an inventory problem. File a support ticket because if the problem is your inventory, they will fix it easily.

  4. 1 hour ago, Gavin Felisimo said:

    I am currently having this issue the last week or so, and see that there are "Login investigations" in process, but it is wierd that I can Login with an Alt, but not my main username. How do we find out if we have other issues? Wouldn't my IP address be the same for my Alt as for me? ...so, not an IP blocking issue?

    It can be an inventory issue. Or maybe a DNS problem. Try using different DNS servers and if that doesn't work you better file a ticket.

  5. 12 minutes ago, Qie Niangao said:

    Yes. But also, as much as we users may keep up, the accumulated platform "evolutions" have made it just crazy complicated for new users even when the changes themselves are simplifications. Eventually they'll need to know what "BOM" means and why it's a thing, and which appearance sliders work and which don't, and why there are heads and bodies and *system* heads and bodies, and alpha masks and alpha slices and hair and hairbases (some system and some EvoX) and shoes as footwear and shoes as height adjusters… and bumpmaps and normalmaps and PBR glTF normalmaps and and and.

    No idea what to do about it but an ever growing learning curve is a barrier. 

    Ha! Ha!

    That is partially true. And it's only partially because there are loads of good, attractive content that is ready to use without needing to know all those details. Details will come with time, if the new users stick around.

    Anyway, that's one of the reasons why communities are important: they provide help.

    • Like 1
  6. 1 hour ago, Extrude Ragu said:

    [...] Many residents are so old that the platform changing to get with the times just isn't appealing to them because they're so invested in how SL works now.

    Exactly. Also, who has the time and patience to wait for years to have a new virtual world working more or less as it should?

    SL evolves slowly enough for us, users, to keep up with the changes. And how it has changed since I joined, back in 2011!

    Comparing SL to any game is a a mistake. Although it can be seen as a game, it is not. It's all about building your identity and shaping how your virtual life is.

    • Like 3
    • Thanks 1
  7. 9 minutes ago, Riodan said:

    Ironically, it was but it fell flat on it's face. I think this is probably attributed to the fact that you couldn't bring over your assets from SL, and it was a little too unfamiliar for most Second Life users.  People generally don't like too radical of a change when it comes to things like this, it's one thing to have better graphics and smoother performance, it's another when you put learning curves in front of someone just logging in for the first time...]

    You're probably right but also consider that this is a niche, and possibly the number of people who can actually spend time learning a new thing after using something for years is possibly even smaller.

    I think the Lab learned from Sansar, not only technically but also as a business. What do people say about trying something a second time and expect a different outcome?

    • Like 5
  8. 3 minutes ago, Riodan said:

    That's an interesting response, can you elaborate? I'm curious as to your concerns on the subject and this seems like a perfect time to gain understanding on how people are thinking about the situation?

     

    For me, to put it simply, it's a matter of trust in general.

    • Like 2
  9. On 5/10/2017 at 6:53 AM, Callum Meriman said:

    I tested this not so long ago.

    It doesn't work.

    I banned a friend of mine, then asked him to try to get his alt in, his alt was able to enter without an issue.

    An alt account can get in the region right after the other account has been banned. I've seen it happen a few times in Innsmouth.
    Apparently, there is some delay before all accounts are banned.

    [EDIT] Oh, I just read what Whirly wrote about it, and it makes sense. So, before all accounts are banned the one that has just been entered to the ban list has to try getting in again.

  10. 1 hour ago, DAli Davidov said:

    I have the same problem "login failed. despite of........" but it happened only with two of my accounts the others can login normally

    Try what is suggested on the Grid Status, which is use different DNS servers than you have set at the moment.

    I had that problem a couple days ago. I couldn't login my main account but could enter with my alt. After talking with Support (they said it's a known issue but there is no ETA for a fix) I changed from Google's DNS servers to my own ISP's DNS, and it's been fine so far.

    • Like 1
  11. 1 hour ago, Ardy Lay said:

    Some network operators, access and transit, discard UDP traffic in times of congestion, perhaps thinking that only BitTorrent still uses UDP.

    Right.
    Logging in was fine, the problem was connecting to the cloud, where SL really is, as you know. Now I'm wondering if all the other people who experienced the issues use the service of ISP's belonging to the Altice group (my ISP is a company that is owned by that group).

  12. 8 hours ago, xXJupiterHeightsXx Starchild said:

    can you follow up on how cloudflare worked?? 

    It's all good. Google DNS is working too.
    May have been some network in the way that was slow or blocking traffic. As the Lindens don't say what it was, all we can do is guessing.

    [EDIT - a lot of editing, as not being a techie it takes me quite sometime to have an idea about it all and I'd hate to be unfair to any of those involved]
    Here's some info gathered from a traceroute to a403.b.akamai.net I was asked to perform on that horrible day compared to how it is right now (have a look at that particular slow hop):

    then >
      4     6 ms     6 ms     5 ms  lis1-cr1-be10-200.cprm.net [195.8.30.237] 
      5    27 ms    41 ms    41 ms  akamai1.cprm.net [195.8.10.110] 
      6     6 ms     6 ms     5 ms  a95-100-100-10.deploy.static.akamaitechnologies.com [95.100.100.10] 

    now (while staying in-world) >
      4     6 ms     6 ms     6 ms  lis1-cr1-be10-200.cprm.net [195.8.30.237]
      5     8 ms     6 ms    13 ms  akamai1.cprm.net [195.8.10.110]
      6     6 ms     5 ms     5 ms  a95-100-100-17.deploy.static.akamaitechnologies.com [95.100.100.17]

    akamai.net is a cloud services provider. cprm.net is my ISP. Hmmm... It looks like my ISP was having trouble accessing the cloud. But what about the other ISP's? (France, Germany, UK and Brazil, at least)

    But why an SL unscheduled login maintenance that seems to have solved the problem? Was it the login system routing some connections (ISP's) though a troubled network? Yeah, I'm totally clueless.

    (yes, only now I had the time to look at it more closely)

    • Like 2
  13. The issue is intermittent now. I could login fine about an hour ago at my home parcel and teleport around for a while... until it's back.

    [EDIT] I was logged out and now I get stuck waiting for region handshake, no matter where I try to login.

    [EDIT 2] Yes, it comes and goes away. I'm back in and could teleport to a store.

    • Like 1
  14. 1 minute ago, Brilliant Price said:

    I agree , but there is no discernable reason why it works on one machine for the same account with the same ISP and not on the other. And if FS isn't the problem then it surely must be SLs servers that are hoodwinking the engineers.

    As the evening progresses I am hearing of more and more people suffering the same trouble. But not a whisper from the lab other than Monty's notes earlier.

    Yeah, LL seems ready to discard whatever they might be responsible for. Anyway, I'm off to sleep. We'll see how it goes tomorrow and the next few days. I'd hate to cancel my membership but if I can't enjoy SL, I'll find some other entertainment and maybe even save some money.

  15. 6 minutes ago, Brilliant Price said:

    Now here's the odd thing.

    I Cleaned out my tired old iMac and loaded FS 6.6.17 onto it. (Just for desperations sake) And to my surprie I was able to get in-world to my home. Without any region handshake conectivity problems. Twice in fact. But I am afraid to try to teleport and I'm not going to because I want to keep channels open for my customer queries.

    However on my more modern Macbook Air the original problem persists. This tells me that at least my fibre internet connection is not the issue. And now my finger points back to my laptop and to Firestorm. I suspect a file or something got corrupted during the installation. A file that other viewers also need access to.

    But hey I'm no techy - far from it but surely  this is a clue.

    My Firestorm 6.6.17 worked fine between about 9:30 and around 2 am SLT. Doesn't make sense to me that at some point it would change whatever might be needed by other viewers.

    [EDIT] Unless it's an inventory problem. Hmmm...

  16. 4 minutes ago, mygoditsfullofstars said:

    It might be interesting to know whether or not if any of the affected people are using VPN's (some AV software like Norton, and I am sure there are others also includes a VPN service that runs in the background, often without the end users knowledge its even rerouting their network traffic).

     

    No VPN here. I only use the built-in Windows security tools. And all Firestorm and Second Life Viewer critical folders are whitelisted.

  17. 2 minutes ago, mygoditsfullofstars said:

    It could be a problem with an intermediate network carrier somewhere along the network path into Amazon that's having issues and those who are unlucky are being routed via that carrier.

    Yes! That's the only thing that makes sense to me.

    • Like 1
  18. 15 minutes ago, Aishagain said:

    This is a silly question and one that may have already been adressed but is there any corealation between this login stalling issue and the Operating system for are using?  Like is it just Mac or are all OSs being affected?

    I ask because I am still completely unaffected.

    I'm using Windows 10 up-to-date. And as I wrote before, it all worked just fine early today.

    Support seems to be out of solutions. Now they recommend that I contact my ISP, which isn't the same ISP people with the same problem in the UK, France, Germany and Brazil (and who knows where else) have.

    My PC is hardwired to the router, as it's always been. That was another suggestion from Support besides recommending me to contact my ISP.

    If this issue persists over time, I will be forced to cancel my membership and take out all the money stored in my Tilia account.

×
×
  • Create New...