gsadmin/pulse
1
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-09-10 02:25:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document agent URL updates when the server address changes

Browse Source 
Restoring a configuration backup onto a Pulse instance with a new address
makes every agent vanish until each agent's configured --url (PULSE_URL for
containers) is updated, because agents dial the address they were installed
with. The post-migration checklist covered the token but not the address.

Refs #1813
This commit is contained in:
rcourtman
2026-08-31 06:41:11 +01:00
parent 1cce814ad3
commit bad717f16e
2 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/MIGRATION.md
+5
View File
@@ -66,6 +66,11 @@ Because local login credentials are stored in `.env` (not part of exports), you
3. **Update Agents**:
* **Unified Agent**: Update the `--token` flag in your service definition.
* **Containerized agent**: Update `PULSE_TOKEN` in the agent container environment.
* **New server address?** Agents dial the address they were installed
with (the `--url` flag, or `PULSE_URL` for containerized agents), so
agents disappear from the new instance until that value is updated in
each agent's service definition. Fronting Pulse with a DNS name
instead of an IP address makes future moves invisible to agents.
* *Tip: Use **Settings → Infrastructure → Install on a host** to generate updated install commands.*
4. **Relay/Pro/legacy Pro+/Cloud**: Re-activate your license key after migration (license files are not included in exports).
frontend-modern/public/docs/MIGRATION.md
+5
View File
@@ -66,6 +66,11 @@ Because local login credentials are stored in `.env` (not part of exports), you
3. **Update Agents**:
* **Unified Agent**: Update the `--token` flag in your service definition.
* **Containerized agent**: Update `PULSE_TOKEN` in the agent container environment.
* **New server address?** Agents dial the address they were installed
with (the `--url` flag, or `PULSE_URL` for containerized agents), so
agents disappear from the new instance until that value is updated in
each agent's service definition. Fronting Pulse with a DNS name
instead of an IP address makes future moves invisible to agents.
* *Tip: Use **Settings → Infrastructure → Install on a host** to generate updated install commands.*
4. **Relay/Pro/legacy Pro+/Cloud**: Re-activate your license key after migration (license files are not included in exports).