Solarius Compute Cloud
Identify regional compute hostnames and inspect hosted connectivity.
Solarius Compute Cloud provides the hosted capacity managed through Infra.
Its compute hostnames use the compute.solarius.me domain and a regional code.
Select a hosted region at Compute → Droplets → Create droplet → Region. For a self-hosted installation, first authorize a Connector. The region selector shows the locations and resource classes available to the selected organization.
Regional hostnames
The hostname format is a<number>.<region>.compute.solarius.me. For example,
a1.eu.compute.solarius.me is the a1 compute hostname in the eu group.
The numeric label identifies a host; it does not define an availability zone,
hardware class, or failover order.
The regional host labels in this table have the suffix .compute.solarius.me.
| Region code | Location | Host labels |
|---|---|---|
au | Australia | a1.au, a2.au |
br | Brazil | a1.br, a2.br |
cn | China | a1.cn, a2.cn, a3.cn |
eu | Europe | a1.eu, a2.eu, a3.eu, a4.eu, a5.eu, a6.eu, a7.eu, a8.eu |
in | India | a1.in |
ke | Kenya | a1.ke |
na | North America | a1.na, a2.na, a3.na, a4.na, a5.na |
sg | Singapore | a1.sg, a2.sg, a3.sg, a4.sg |
za | South Africa | a1.za |
Use the region and zone identities shown by Infra when configuring placement, replication, or residency. Hostname groups alone do not establish independent power, network, or storage failure domains. Resource availability and prices depend on the selected region's catalog and the organization's access.
Connection endpoints
Open Installation settings → Connectors → Connector to inspect the configured hosted service endpoint and connection health. Use that endpoint for Connector configuration and its required outbound access. The compute-host directory is not a list of required Connector destinations.
Guest SSH, application traffic, and load-balancer access use the resource's assigned network addresses. Inspect them at Compute → Droplets → Droplet → Networking or Networking → Load balancers → Load balancer → Overview.
Inspect DNS resolution
Run DNS checks on the machine experiencing the connection failure. For a Connector failure, use the Connector host and its configured service hostname. For a compute hostname reported in a diagnostic record, resolve that exact name:
dig a1.eu.compute.solarius.me ATo check the same hostname for an IPv6 answer, run:
dig a1.eu.compute.solarius.me AAAARecord the resolver, answer, TTL, and lookup time with the affected operation ID. An empty AAAA answer alone does not indicate a failure when the service uses IPv4. Successful resolution establishes name lookup; connection and authorization must be checked separately through the affected resource or Connector.
Use DNS answers for address inspection rather than copying a fixed IP from this reference. Where an egress policy requires IP rules, apply the destination requirements supplied for the connection and review the rules when those requirements change. See Connector delegation for authorization failures and troubleshooting for operation recovery.