Network and Certificates
Configure connectivity, domain names, hotspots, and certificates
Table of Contents
About this guide
Users need a reachable address, working name resolution, and a trusted certificate to access Edge securely. Use the addresses assigned during deployment; the standard Edge domain names resolve to your appliance through your local network configuration.
Application addresses
| Service | Standard Edge name or access pattern |
|---|---|
| Workspace | https://chat.edge.asksage.ai |
| API | https://api.edge.asksage.ai |
| Appliance Manager | Deployment-specific management hostname or address, commonly on port 11100. |
| Local documentation | https://docs.edge.asksage.ai where installed, or the supplied local address / Manager’s Documentation link. |
Custom domains can replace these names. Some kits use a direct Manager address such as http://appliance.asksage.local:11100; see kit addresses. Use the exact hostname and protocol in your handover record.
Coordinate user-network access and management-network restrictions with the network administrator. Permit only the required paths. Cloud inference, update retrieval, SSO, and connectors have separate connectivity needs; there is no single internet-access requirement that covers every deployment.
Wi-Fi hotspot
A supplied kit router can provide Wi-Fi for browser devices; join using the actual QR code or details on the router or credential card. That router’s Wi-Fi is separate from an appliance-hosted hotspot. See kit setup.
On equipped appliances, an admin can manage the appliance’s hotspot in Network.
- Review whether the hotspot is enabled and confirm site policy allows it.
- Set the Network name (SSID) and a password meeting the form’s requirements.
- Select Save changes.
- Reconnect authorized devices with the new credentials or the displayed join QR code.
- Review Connected devices to confirm the expected clients.
Changing the hotspot configuration can disconnect the workstation making the change. Keep wired or local console access available. Disabling the hotspot removes that access path; it does not shut down the appliance’s wired services. A hotspot connection also does not guarantee internet access.
Change a domain or certificate
Where available, use the admin controls in Settings. Before changing the domain, coordinate the new DNS records, matching certificate, identity-provider redirects, and API client configuration. Review any preview supplied by the Manager, then apply the change during a maintenance window.
For certificate replacement:
- Obtain the certificate, required chain, and matching private key through your organization’s certificate process.
- Confirm the certificate covers every hostname users will access and is valid for the intended period.
- Open the certificate controls in Settings, supply the requested material, and select Upload & apply certificate.
- Wait for the web service to reload.
- From a user workstation, verify the workspace and API hostname, certificate trust, and sign-in.
Application ingress certificates and the Manager’s direct port may be configured separately. Replacing a workspace certificate does not establish that every management endpoint now uses the same certificate.
For an internal certificate authority, install the approved trust chain on client devices through the organization’s normal process. An isolated deployment still needs a plan for certificate expiration and renewal.
Moving to a different network
Record current addresses and arrange console access before the move. Shut down gracefully, reconnect on the new network, and confirm all expected nodes, any interconnects, addresses, gateway, DNS, and time services. Update client DNS records or reservations as required.
Changing an address can affect cluster services as well as browser access. Follow the platform’s network reconciliation procedure supplied by your deployment team. Appliances with the asksage-console tool may offer a Network menu for this work; hotspot settings are not a general static-IP editor.
If the page no longer loads, use Troubleshooting. Check the expected name and certificate before changing application or model settings.