First viewer login and initial tests
The server starts: verify real avatar access and basic functionality.
Check that the region is ready
Wait for the region console prompt. Inspect registered regions, agents and logs. Startup messages may reveal an invalid URL or inaccessible service.
Adapt this example: verify paths, hostnames, permissions and settings.
show region stats show
Create or identify an account
Standalone first run normally prompts for the estate owner and credentials. The simulator console also provides create user. On a grid, ensure user and authentication services are correctly set up first.
Adapt this example: verify paths, hostnames, permissions and settings.
create user
Identify the correct login URI
For local Standalone, the repository shows http://127.0.0.1:9000. On Grid, the login URI is the configured ROBUST login service, often on its public template port. From a remote client, 127.0.0.1 refers to the viewer's own computer, not your remote server.
Add the grid in a viewer
In an OpenSimulator-compatible viewer, use its grid manager to add your installation's login URI. Enter the account's first name, last name and password. Exact menu names vary by viewer and version.
Verify essential services
Test walking, rezzing an object, saving an edit, inventory, appearance, logging in a second avatar and reconnecting. A single successful login does not prove the stack is fully operational.
Troubleshoot from another machine
If login succeeds but the avatar never arrives, inspect the region's ExternalHostName, published ports, firewall and NAT. If inventory is missing, inspect central services and database.
Before opening to the public
Add monitoring, log rotation, automated backups, controlled upgrades and separate administrative accounts. WebRTC voice and third-party modules are additional work, not prerequisites for first login.