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

docs: remove time references from password recovery sections

Browse Source
This commit is contained in:
Pulse Monitor
2025-09-04 10:34:16 +00:00
parent 3912f1db3e
commit cbfe1ecd4c
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/SECURITY.md
+1 -1
View File
@@ -354,4 +354,4 @@ curl -X POST http://localhost:7655/api/security/reset-lockout \
**Can't login?** Check PULSE_AUTH_USER and PULSE_AUTH_PASS environment variables
**API access denied?** Verify API_TOKEN is correct (use original token, not hash)
**CORS errors?** Configure ALLOWED_ORIGINS for your domain
**Forgot password?** Start fresh - delete your Pulse data and restart (takes 2 minutes)
**Forgot password?** Start fresh - delete your Pulse data and restart
docs/TROUBLESHOOTING.md
+2 -2
View File
@@ -8,7 +8,7 @@
**Solution: Start Fresh**
If you've forgotten your password, the recommended approach is to simply start fresh. Pulse is designed for quick setup - it takes just 2-3 minutes to be fully operational again.
If you've forgotten your password, the recommended approach is to simply start fresh. Pulse is designed for quick setup.
**Why no password recovery?**
- Adding recovery mechanisms creates security vulnerabilities
@@ -173,7 +173,7 @@ systemctl status pulse 2>/dev/null || systemctl status pulse-backend
#### Lost authentication
See [Forgot Password / Lost Access](#forgot-password--lost-access) section above.
**Recommended approach**: Start fresh. Delete your Pulse data and restart - takes 2 minutes to set up again.
**Recommended approach**: Start fresh. Delete your Pulse data and restart.
#### Corrupt configuration
Restore from backup or delete config files to start fresh: