OpenSimulator · EN

Hosting and connectivity troubleshooting

A step-by-step method: DNS, NAT, firewall, logs, CPU, RAM and storage.

Educational guide with fictional examples. Verify OpenSimulator versions, networking and security before running a production grid.

Identify the failing path first

Does the viewer fail to reach ROBUST, or does login succeed before a region handshake failure? Are all visitors affected, only LAN users or one particular region? Record time, DNS name, region and exact error, then inspect relevant logs before changing ports.

External connections fail

Check public IP, possible CGNAT, DNS resolution, home forwarding and PC firewall. Inspect actual listening processes: an open router rule is not enough when nothing listens on the host. Test from a genuinely external network, not only from the LAN.

Local fails while outside succeeds

Suspect NAT loopback/hairpin and local DNS, but do not assume they are the only cause. Compare LAN access to private IP and public hostname, then inspect the addresses returned by grid and region services. Hosts-file edits should only be tried with an understanding of their limitations.

Region handshakes and UDP

Login can work while regions remain unreachable because UDP region ports or advertised external addresses are wrong. Check Regions.ini, actual ports, HTTP listeners and firewalls. HTTP/TCP checks do not prove UDP reachability; retest with a real external viewer.

Slow simulator, scripts or missing textures

Inspect CPU, RAM, swap, storage latency, inodes and networking. Physics or scripting may saturate one core despite low aggregate CPU usage. Missing assets might come from FSAssets storage, SQL, a missing mount or caching; read logs before altering data.

Illustrative example: adapt to the actual installation.

# Linux : contrôles de première intention
ss -lntup
free -h
vmstat 1 5
df -h
df -i
findmnt
# Logs ROBUST et simulateurs : adapter les chemins réels.

SSH unreachable after a firewall change

Do not add more random rules. Use provider emergency console or KVM access when available, then inspect effective rules and logs. Always arrange out-of-band access before changing firewall rules on a remote server.

Prepare a useful diagnostic report

Describe topology (PC/router/VPS/VM), masked private/public IPs, DNS, configured TCP/UDP ports, possible CGNAT, results from LAN and internet and relevant log lines. Never post passwords, tokens, keys or unnecessary personal and sensitive network details.

Further reading