Support

Check the last check-in and reported error in the dashboard. Confirm the target device is awake, has internet access and has its updater service installed. List installed hosts and inspect the logs:

ipalive list
ipalive logs router

Replace router with your own host. If its service needs reloading, use ipalive repair router; macOS or Windows may require administrator privileges. For an alternate service domain, use the full hostname, such as router.ipsteady.link.

Tokens are tied to one hostname. Use browser approval during setup, or generate a replacement token for the affected host in its dashboard. To replace a locally saved token, use ipalive update router. Rotating a token invalidates its previous copies, so update every device using that host.

The service is rate limiting requests. Let the next scheduled updater run proceed instead of repeatedly starting manual updates. If the error persists, send support the time and affected hostname.

DNS resolution only confirms an address record exists. Check your router’s port forwarding, firewall, carrier-grade NAT and the service running on the device. A VPN or proxy can cause the updater to report a different public address. IPAlive does not open ports or provide a tunnel.

ipalive add
ipalive list
ipalive remove router

Create a host in your dashboard before connecting it. Remove stops that device’s local updater and removes its local credential; it retains your dashboard host and DNS record. To invalidate credentials on other devices, rotate the token in your dashboard.

Use Forgot password? on the sign-in page and check your spam folder. Reset links expire after 30 minutes; verification links expire after 24 hours. Request a new link if needed. Contact support from your account address for help; we may need to verify ownership.

A site update and an updater software update are separate. Use the site banner’s Update now button to refresh the dashboard/PWA. For a host’s updater, use its dashboard Update now button or ipalive upgrade on that device. Dashboard commands wait for its next check-in; inspect its progress before retrying a failed update.

Check the delivery log and your endpoint’s availability. Your receiver must accept public HTTPS requests without redirects and verify the signature against the exact request body. After fixing the endpoint, use Retry now when available. An expired event or a changed endpoint configuration requires a fresh test instead.

The default inactivity alert is after 24 hours with weekly reminders. Premium accounts can choose their timing and recovery notifications. Missing check-ins do not automatically delete your hostname or DNS records.

Email support@ipalive.link. For account requests, use your account email where possible. For abuse, include the hostname and a description with relevant dates; do not include secrets or sensitive content unnecessarily.