I have yet to get in EVER! I've got a whole mess of stuff I bought waiting for me while I stay stuck

[Rynokat75]

Recieved all kinds of messages, dinked around with the firewall, got graphics updates, video card update, this that the other, still unable to log in. I know everybody's computer is different so things might not apply in all cases but I could also just be goofing a basic tech type of thing that should be a simple fix. Man I just want to put on my gear and go sail my boat already!!!

[Nalates Urriah]

When you ask a tech question include information about your computer and viewer. If the viewer will at least show the login screen, get the info from the viewer's Help-About... and paste that into your post with your question. Help->About... provides all the version numbers we need.  To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post.

You should always look at Second Life Grid Status Reports to see if a grid wide problem has come up. It can take a couple of hours for a problem to appear there. So, keep checking while you try to resolve the problem.

Specifically check your Second Life connection: Troubleshoot Your #SL Connection.

Check that your computer meets the System Requirements | Second Life.

Try this site to see if you can run SL. This is not perfect, but it should give you and idea. Can I Run Second Life?

[Rolig Loon]

Your first post suggested that you may have been getting an error message that says you cannot connect to a simulator.  If that's correct, try these possibilities:

• Your Internet Connection is Down Check whether you are able to connect to the 'net using a web browser; try to use it to visit a known website. If that fails, then the first thing to try is to unplug your modem/router for at least a full minute, then once plugged back in, allow then to go through startup, after which reboot your computer. If after this you are still unable to connect to the Internet with a web browser, you will probably need to contact your ISP to have your connection checked.

• Your Router and/or Modem has Problems Repeat the same things as above.

• Your Firewall is Preventing the Connection Try disabling your firewall software completely and then try to log in again. If you are successful, then you need to allow the viewer access through the firewall. Some tips on how to do that are here.  If you are on a college campus or behind a corporate firewall, you may not be able to disable or modify the firewall.  You'll have to talk with your IT department.

• Buildup of Open Notifications It is possible for a buildup of too many notifications to cause Firestorm to disconnect during or shortly after login. If you experience such disconnections repeatedly on Firestorm, then follow the instructions under “Firestorm Logs Out During Login” here.

• Domain Name Server (DNS) Issues Users of Firestorm may get “Unable to connect to simulator”, or a message specifically saying that there are issues with the DNS. In that case refer to this page for how to proceed.

• Region is Down It is possible that the region you are trying to log into is down. So try again but select a different region name at the log in screen. Some regions you can try: Hippo Hollow, Aich, Hatton, Pooley.

• Group Tag Preventing Login There are cases when your active group tag will prevent log in - most usually when the tag contains unicode characters (though there have been isolated cases where even standard Latin characters have prevented log in as well). If this happens, you can attempt to log in using a text based viewer such as Radegast or MetaBolt, and change your active group in that viewer (preferably to None), log out and then log in with your usual viewer.
  Should that not be an option, you will need to find a way to get word in-world, to the group owner, and have them either edit the group title tag or, should that not be an option, eject you from the group.
  If that too is not a viable option, then the only other recourse is to file a support ticket with LL and have them change your active group.
  This is a server issue, and is reported in this LL JIRA.