Секонд лайф ошибка входа

There are a number of reasons why a login to Second Life might fail, including technical issues and account problems that must be resolved in order to continue. This article may help you identify your problem and choose an appropriate solution.

TABLE OF CONTENTS

• Error messages
  • Technical Issues
    • DNS could not resolve the host name
    • Waiting for region handshake
  • Account Issues
    • Your account is not accessible until (date/time)
    • You cannot log into Second Life from this location
• What might cause login failure?
  • Wrong password
  • The system is still logging you out
  • Linden Lab may have temporarily restricted all logins 
  • Account disabled due to delinquency 
  • Account on hold due to disciplinary action 
• How do I fix it?

Error messages

If you can’t log in to Second Life, the error message may indicate the source of the issue.

DNS could not resolve the host name

This error may also appear as:

• Host http not found 
• Login failed. Unable to connect to a simulator.

These messages indicate that your computer has a general networking issue with the domain name service (DNS) that translates numerical IP addresses into human-readable ones.  

Confirm that you can reach internet sites such as secondlife.com, Google, or others. If you have no trouble reaching other websites, it may be a specific routing issue between your system and Second Life’s login servers, not unlike a highway being closed between your home and your destination. Refreshing your DNS listings by restarting your system and router can often help by giving your system a new route to the Second Life servers, diverting around the outage.

It’s also a good idea to check whether there is a wider issue with Second Life, as described below.

Usually, restarting your computer and your router will resolve this issue. If not, please contact your internet service provider.  You may also wish to try using a different DNS server, like Cloudflare’s 1.1.1.1 service, to see if that will resolve the issue.

Waiting for region handshake

The «Waiting for Region Handshake» message occurs when the Second Life Viewer does not receive an acknowledgement from the server.  The usual cause of this error is a firewall blocking UDP packets. You’ll most likely need to reconfigure your firewall to resolve this problem.

For information on how to configure firewalls, see: Using Second Life with a firewall.

Your account is not accessible until (date/time)

There are two possible causes for the ‘not accessible until…’ error message:

• If the error states that you are already logging in (or out), then Second Life is still attempting to log out your avatar. Close Second Life, wait fifteen minutes, then attempt to log in again.
• If you see this error message: Login failed; Your account is not accessible until (date/time) 
  • This usually means that your Second Life account has been administratively blocked. Short-term blocks (less than an hour) may be the result of inappropriate behavior inworld. Longer blocks are typically the result of abuse. 
  • You will be unable to use Second Life until the indicated time; if that is more than an hour away, you will receive an email from the abuse team on the matter.  Be sure to check your spam filters.  
  • Linden Lab is unable to remove administrative blocks for abuse.

You cannot log into Second Life from this location

This error message may also appear as:

• Login failed.
• Second Life cannot be accessed from this computer.

These messages generally indicate you have been blocked from the Second Life servers by Linden Lab as the result of:

• Documented cases of fraud
• Use of Second Life by a minor
• Exceptionally flagrant abuse activity

Note that someone else in your household may be responsible for this activity, not necessarily with your account. 

If you believe that this is an error, submit a support ticket via the support portal. To help customer support determine what block has been placed and why, include in the ticket your Second Life account name and any Second Life accounts that log in from your location.

What might cause login failure?

Wrong password

Incorrect passwords are a common cause of login failure. Passwords are case-sensitive, so remember to check Caps Lock if you know you entered your password correctly. It may help to type your password in a visible location like Notepad or TextEdit, then copy and paste it into the viewer. You can also use a Password Manager software for a convenient and secure way to store a unique and complex password for Second Life; there are a number of excellent password manager options, including some that are open source and multi-platform.

If you’ve forgotten your user name or password, please follow the instructions in Account credentials to retrieve it.

The system is still logging you out

Your previous session must be logged out before you can get back into Second Life. Sometimes, usually after a recent logout or crash, Second Life mistakenly thinks you are still logged in. If you receive a login failure message stating that «The system is logging you out…,» try waiting a few minutes before logging in again. If you continue to receive this message, you may be a victim of «stuck presence,» which can be fixed by restarting the region in which your avatar is stuck.

Residents with Premium, Premium Plus, or Concierge level accounts may request a region restart via live chat, ticket submission, or phone support. Basic accounts do not have access to avatar-level support at this time.

Linden Lab may have temporarily restricted all logins 

Linden Lab might sometime restrict access to Second Life when its servers experience severe technical difficulties or require major maintenance. These outages affect all Residents and are not limited to your computer or account.

Check the status of the Second Life at http://status.secondlifegrid.net. This page lists any known issues.

Account disabled due to delinquency 

If you have an overdue account balance due to membership or land fees that exceeds the grace period allowed by the delinquency policy, your account and your alternate accounts may be disabled for delinquency. While your account cannot login to Second Life while there is a past due balance, you can login at secondlife.com to view your Account Dashboard to see any charges on your account and update your payment information, if necessary. For more information, please see our Delinquency Policy.

Account on hold due to disciplinary action 

If we find that a Resident has broken our Terms of Service, Community Standards, or other policies, we may place that Resident’s account on hold as a disciplinary measure. When we place an account on hold in this way, we send an email to the account holder at the address registered to that account.

How do I fix it?

If you’re not sure why you can’t log in, try these things:

1. Double-check your username and password. If you continue to receive an error message, try logging into the Second Life website. If you are unable to log into the website, the problem is likely to be your username or password. Follow the Forgot your login information? instructions on the website to reset your password.
2. Change your login location to a different region. See below for instructions on how to do this.
3. Restart your computer, modem, and router. When restarting, make sure to leave everything powered off for at least ten seconds before restarting. This step can often fix routing issues and other connection-related problems.
4. If you are still unable to log in, Premium, Premium Plus, and Concierge Residents may contact customer support via live chat, support cases (tickets), or telephone.  Basic customers may file a support case.  See How to contact customer support for more information.

Changing your login location

A starting location field appears on the login screen; you may choose to log in at your last location, your home, or you may enter the name of any Region in order to attempt to log into that Region directly.

If you’d like to always have a login location dropdown available on the login screen, you can set these preferences in the viewer:

1. Start Second Life. At the login screen, go to Me > Preferences.
2. Click the General tab.
3. Check the box marked Show favorite locations on login screen.
4. Click OK.

Don’t see what you need here? Please visit our Knowledge Base for a more comprehensive list of Support topics!

Ошибки входа в СЛ

Troubleshoot Your Second Life Connection

I made this post to avoid typing this information into the SL Forum a gazillion times. I was answering this type of question for the third time today. (Last updated April 2023)

There are a number of reasons one cannot log in or stay logged into Second Life. One of the more significant reasons is a poor connection. You may have a good Internet connection and a bad connection to SL. A poor connection can be caused by multiple problems in different locations. In this article, I try to give you some troubleshooting tips to help find where the problem is and who can fix it.

The problem may be in your computer, router, modem, ISP’s hardware, backbone hardware, Linden Lab’s hardware, or their software. We need to figure out which.

I’m Windows-based. So, this article is Windows oriented. But, all the same problems exist for Mac and Linux users. The Mac and Linux users will have to translate Windows commands. Sorry. I just don’t know them.

Troubleshooting

In the Viewer

If you can log into Second Life, do so. If not, check the grid status to make sure it is not a problem with Second Life. Or look at the concurrent user graph at Etitsup.com. You should see a smoothly curving line. An abrupt drop shows a general problem.

Also, try logging into a different region. Before logging in open Preferences->General->Start Location – Show at Login and enable the option. After closing Preferences, you’ll see a new field by the login button, ‘Start At:’. Try a Linden-owned region like Pooley or Furball. If you still cannot log in skip down to On Your End and SpeedTest.net.

Update: Jan 2018 – SpeedTest.net has changed. They no longer allow you to test to a city or server of your choice. So, for these tests, the site is was useless for our purposes. You’ll have to Google for an Internet speed test on a specific server and hope to find a good one. I’m looking… Found – see: Internet Speed Tests. – Update April 2023 – The Firestorm Viewer Team has information up on testing your connection speed HERE. The article has been updated but while they tell how little the Max Bandwidth setting will affect performance they also left all the advice for what it can affect from days of old. Don’t expect much from tweaking your bandwidth setting.

Once things rez to the point you can see anything, press Ctrl-Shift-1 to toggle on Viewer Stats. Look for Ping and Packet Loss. They should be <250ms and 0%.

If they aren’t good, look for Time Dilation (DT) and Physics FPS (PFPS) farther down the panel. These should be 1.0 and 44/45. If the values are below 0.8 and 30, the server hosting the region is lagging, which can be from any number of causes, which you can’t do anything about. If the region server lags significantly, it can distort the Viewer’s Ping making it unrealistically high and also cause packet loss.

If DT and PFPS are bad, move to another region. Use the World Map and look for Pooley or Smith. Look for a region without any people. Deserted is best. The less stuff there the better too. Pooley, Furball,  and Smith are in areas that are often deserted and that is the only reason to use them. Any empty region will do.

Check your Ping and Packet Loss again. If the numbers are still bad and DT and PFPS are bad too then you need to check the Grid Status. If there is no cause applicable to your problem try another region. Three bad ones in a row strongly suggest a connection problem over an SL problem. But, wait at least a couple of hours before you do anything drastic and keep checking grid status because it may still be SL. Etitsup.com will only show when general login issues are keeping people out.

On Your End

While still in the viewer and logged in click Help->About and get the server name and IP address, e.g., You are at 287,444.0, 265,656.0, 21.4 in Tuzandi located at sim9849.agni.lindenlab.com (216.82.45.183:13004). The last number is the IP address with a port after the ‘:’. You won’t need the colon and port number for testing your connection.

Update: March 2023 – Finding a server to test to has changed since I wrote the original post. The Lab has moved the servers into Amazon’s AWS server farms. They have changed the HELP->ABOUT… panel to obfuscate the IP Address. This means we are on our own to figure out which AWS server we are connecting to. To find which server you are connected to open HELP->ABOUT… copy the server name (e.g., simhost-0a538900f1ede4aee.agni) and add .secondlife.io to it. In a Command Window type, NSLOOKUP and press enter. Then enter the name you concatenated and press enter. You’ll get the server’s IP Address.

Use an IP Address lookup/geo-locate service to find the city in which it is located. Now you can tracert to the address and speed test to the City. In the USA (North America in general) that is usually Portland, Oregon.

SpeedTest.net will let you test your general Internet connection. Run it at its default settings or point it to San Francisco, Portland, USA (SF) for a basic test. If you have good numbers with that test, point it to the server name or IP address you got in Help (or the one above) and try it again as a more specific test.

If you get bad numbers to SF, the connection problem is either Linden Lab, you, or somewhere in the middle. You can open a command window and try tracert to see if it will show where the problem is. Google tracert with your Windows version for information on how to use the command and read the output. You can use the read-out in a trouble ticket to SL or your ISP.

The results of tracert are showing the time for a network packet from your computer to reach each router in your path to the SL servers. They start with your computer, router, and modem and move on to your ISP’s and then the backbone routers. Then into the SL network (now Amazon’s). Below is an output showing a good connection. It goes from my computer to COX, my ISP. Then to the backbone Above.net. Then it goes into LindenLab.com. The longest time is 43ms ( milliseconds). You see the time increase as the distance is farther. So the last value is the longest.

You can see in line 8 one packet had a little problem and took almost 3 times as long to get there and back (82ms). A bad connection will start to show long times. Lost packets or the routers refusal to answer pings will show as * in place of a time. One * in the line is not good but, not serious. Retest every hour to see if it persists. Two * are a problem and 3 * pretty much means a failure if all pings after show as *.

1    7 ms   8 ms  13 ms  [Removed my local stuff]
2    8 ms  11 ms   8 ms  [Removed my local stuff]
3   11 ms  15 ms  10 ms  [Removed my local stuff]
4   24 ms  26 ms  30 ms  paltbprj02-ae0.0.rd.pt.cox.net [68.1.0.235]
5   68 ms  36 ms  25 ms  xe-2-2-0.cr2.sjc2.us.above.net [64.125.31.70]
6   33 ms  23 ms  24 ms  xe-1-0-0.cr1.sjc2.us.above.net [64.125.30.137]
7   23 ms  26 ms  30 ms  64.125.26.25.available.above.net [64.125.26.25]
8   31 ms  82 ms  32 ms  xe-0-1-0.mpr3.phx2.us.above.net [64.125.28.69]
9   34 ms  32 ms  31 ms  64.124.161.254.allocated.above.net [64.124.161.254]
10  44 ms  42 ms  42 ms  sw-core0-83.phx.lindenlab.com [216.82.7.226]
11  42 ms  43 ms  41 ms  sim9849.agni.lindenlab.com [216.82.45.183]

If times, in this case over 30ms, were in my hardware, the first two lines, I would need to troubleshoot my hardware and settings. It won’t kill the connection by itself but it indicates a problem.

If the times for COX were long or showing lost packets then the problem would be with my ISP. I can complain to them.

If the long times and lost packets were in the backbone, Above.net, I would complain to my ISP and SL. In a way, the backbone is the ISP for COX and SL. You may have more backbone providers showing. I’m routing from San Diego to San Jose, a short hop. However, some may have more or fewer routers between your ISP and SL. fewer is better.

If the long times and lost packets are in the Linden Lab hops, I would complain to SL and include the output of tracert in the trouble ticket.

Fixing Your End

If the problem is on your end, restart your computer, router (if any), and modem/gateway. Repeat the test to SF. If that fixed the numbers you found the problem, you. It is either your modem, router, or computer.

If you have multiple computers using the connection, turn them off and see if that makes a difference. If you are wireless, make sure you have a password lock on your wireless connection. If it is an open connection, check to see if others are using your connection.  You’ll need to find out how to open the control panel on your access point device. It usually must be done via a wired connection. If you have people piggybacking you’ll need to secure your connection.

Update: On wireless routers made in the last couple of years  (~2012) WPS security has been breached. If you are using it, it may be compromised. Switch to one of the other security systems and disable WPS. On Linksys disabling WPS is an option, but it does not work. Look for firmware updates for your router. – In the router controls, you can usually see how much traffic is passing through the router. If you are not online and the traffic is high, you have probably been compromised. Google for more information.

Access points and routers have a limit on the number of connections they can handle. Each computer opens numerous connections and an SL connection opens way more connections than most programs. It is possible to overload some access points and routers. When restarting the router helps that indicates that overloading may be the problem. Allowing people to piggyback can use up available connections causing your SL connection to overload the router.

If you still get bad numbers and you have a router (not just a Cable/DSL modem/router but a separate device), remove it from the connection path. You will need to Google for instructions if you don’t know how to remove the router from the connection path. You will also need to have your operating system up to date and a working firewall. Putting an unprotected computer on the Internet is high risk. A computer with an open exploit can be found and infected in less than a minute. Once you are safe, try the test again without the router.

If removing the router solves the problem, you have found it. Routers and modems are tricky in that they may look fine and allow everything but Second Life to run. Second Life uses a lot of connections. About the only way to know if you have a router problem is to remove it from your connection path and connect to SL. If the problem goes away, you need a new router. You may be able to do a firmware update and save your current router. Google for the ‘How To’ on firmware updates. Use your router’s model and brand in the search.

If your modem/gateway belongs to the ISP contact them. They can test it in place. They may test it for you even if you own it. Ask in any case. Or borrow one and try swapping them out. These devices have settings in them. You need to know the settings to swap them out. And some ISPs will not allow you to swap your gateway. They will ONLY connect to the gateway device they recognize. Again, you can Google to learn how. You can call your ISP and ask if swapping devices will work or is allowed.

UPDATE: 7/18/2012 – Recent testing has shown that two router models are failing to handle Second Life, now that we are in the IPv6 era. The Belkin G Series and LinkSys WRT series routers have problems carrying Second Life. (Reference) This information was provided to Third Party Developers in an Open Source Dev meeting in July. So, if you have one of these, it is time to update. Routers from 2000 to 2005 are likely to have Network Address Translation (NAT) problems with IPv6. Older routers have no chance. 

DNS Problems

You may notice that some lines in your tracert output have no server name. Or maybe the route stops short of Linden Lab and you never see the LL server. All you get is *’s after a certain point. For whatever reason; your computer is not resolving names. Some routers have no name and some just refuse to answer pings, so it is not absolutely definitive. But, the ‘*’ can be caused by a bad DNS server. DNS problems are common on Mac’s trying to use SL… or so I’m told.

To correct DNS problems on a Windows machine open a command window and type ipconfig /flushdns. This will clear a bad name resolution and possibly allow the correct look-up to come in.

If that does not help, add a different DNS server to your DNS Server List. See this Google Public DNS page for help doing that. I have way fewer Internet problems with Google DNS Servers added in than when just using my COX DNS servers.

A DNS Gotcha

When you add the Google DNS servers to your DNS list be sure you keep at least one from your ISP. Some ISP’s have special addresses in their DNS servers for email services, support, and troubleshooting. If you do ever have to call your ISP for help, having removed those DNS servers can really confuse an ISP’s support staff. Plus your computer may not be able to find some URLs support tries to send you to.

Removing all the ISP’s DNS servers from your list may also break your ISP-provided email addresses. Your email client may suddenly not be able to find your ISP’s POP and SMTP servers.

Other Problems on Your End

Network cards and cables do go bad. Wireless connections can be subject to interference. If you have problems with everything Internet then the card or cable can be the problem. With wireless connections, fluorescent lights and the new Chinese curly lights can be a problem (the latter also being a fire hazard).

Fixing the ISP

All you can do is call them and work with them. The problem may be their hardware, the cables, and lines that connect you to them. Or it may be the Internet modem in your home/office. I suggest restarting the modem and computer before calling the ISP. Then recheck your connection again. If it still gives bad numbers, call.

Fixing Second Life

Make sure you are not fighting any known problem by checking the Grid Status page. Check it every hour or so while you are trying to track down the problem. They won’t post a problem until they know it is widespread and really their problem. That can take 2 to 4 hours.

Once you are sure it is the Lab, contact Linden Lab. See: Contacting Second Life/Linden Lab

Other Problems

There are various problems that will give you error messages about why you can’t log in or why you got logged off. They can be connection related or not as there are other causes. See: Can’t Login Second Life for more information on other issues.

You can post those error messages in the SL Forum and ask for help with specific problems. If you can log in, you can also ask in large in-world groups to see if others are having similar problems. If everyone is suffering then it isn’t your hardware.