You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -399,6 +399,14 @@ The FRP client-server connections, i.e. the connection from the above FRP client
399
399
}
400
400
```
401
401
402
+
> **Note:** These FRP certificates are valid for `HP_FRP_CERT_VALIDITY_DAYS` days (default `5000`, ~13 years) and are
403
+
> not renewed automatically. The FRP connection uses mutual TLS, so once a certificate expires the tunnel stops
404
+
> working. To renew them, stop HaRP, delete its `/certs/frp` folder, and start HaRP again, then re-copy `client.crt`,
405
+
> `client.key`, and `ca.crt` to each external Docker Engine and restart its `frpc`.
406
+
>
407
+
> ExApps deployed through HaRP embed these certificates at install time, so after regenerating them you must
408
+
> **remove and re-install each ExApp** for it to pick up the new certificates (a restart is not enough).
409
+
402
410
## Adapting ExApps to use HaRP
403
411
404
412
> We strongly recommend starting support for `HaRP` in ExApps from the start of Nextcloud `32`, as the old `DSP` way will be deprecated and marked for removal in Nextcloud `35`.
0 commit comments