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: docs/guides/google-drive-sync.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,20 @@ for recovery.
33
33
Keep an exported backup file somewhere safe. A Drive copy cannot be
34
34
decrypted without its passphrase.
35
35
36
+
## If you forget the passphrase
37
+
38
+
There is no recovery key or encryption backdoor. If the Drive file is your
39
+
only remaining copy, it cannot be decrypted without the old passphrase.
40
+
41
+
If Admincraft still has the server profiles on this device, open
42
+
**Settings → Data & Sync → Forgot passphrase?** and choose **Replace Drive
43
+
copy**. Confirm a new passphrase and Admincraft will encrypt the local profiles
44
+
again, overwrite the inaccessible Drive file, and resume sync. This does not
45
+
recover anything that existed only in the old Drive file.
46
+
47
+
Choose **Disconnect Drive** instead if you want to stop sync without replacing
48
+
the remote file. The profiles on this device are kept.
49
+
36
50
## Web app notes
37
51
38
52
Drive sync works in the web app, but sign-in is tied to the exact site origin.
@@ -42,6 +56,18 @@ and third-party sign-in are allowed for the Admincraft site.
42
56
Profiles in the browser still depend on site storage. Drive sync or an
43
57
encrypted backup protects them if browser data is cleared.
44
58
59
+
### Profiles created with a self-signed certificate
60
+
61
+
Drive preserves a certificate configured on Android or desktop, but a browser
62
+
cannot use that certificate for pinning. When such a profile is downloaded,
63
+
Admincraft keeps it unchanged for native devices, stops the browser from
64
+
attempting an incompatible connection, and explains the required change.
65
+
66
+
Use **Public address, trusted certificate** with a hostname and certificate the
67
+
browser already trusts. If the browser reaches the same Minecraft server
68
+
through a different address, keep the self-signed profile for native apps and
69
+
add a second browser-compatible server profile. Admincraft will sync both.
70
+
45
71
## Troubleshooting
46
72
47
73
| What Admincraft shows | What to do |
@@ -52,6 +78,7 @@ encrypted backup protects them if browser data is cleared.
52
78
|**No Admincraft configuration exists**| Choose **Upload this device** on the device that has the profiles first. |
53
79
|**Sign-in was cancelled**| Try again and finish the Google account prompt. |
54
80
|**Could not decrypt**| Check that the passphrase exactly matches the one used for the Drive copy. |
81
+
|**Passphrase forgotten**| Use **Forgot passphrase?** to replace Drive from a device that still has the profiles, or disconnect while keeping its local profiles. A Drive-only copy cannot be recovered. |
Copy file name to clipboardExpand all lines: docs/guides/web-app.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,17 @@ The private tailnet address still works in the Windows and Android builds, which
28
28
29
29
## Self-signed certificates
30
30
31
-
Web pages cannot install or pin a certificate for a WebSocket connection. The **Self-signed certificate** option is therefore hidden in the web app.
31
+
Web pages cannot install or pin a certificate for a WebSocket connection. The
32
+
**Self-signed certificate** option is therefore not offered for new web
33
+
profiles. A synced native profile still shows its real mode, disabled, so the
34
+
web app does not silently reinterpret it as a public certificate.
35
+
36
+
If Drive sync brings in a profile that was configured with a self-signed
37
+
certificate on Android or desktop, Admincraft preserves it but does not try to
38
+
connect with it in the browser. Switch that profile to **Public certificate**
39
+
only when the same hostname presents a certificate the browser already trusts.
40
+
If the browser needs another hostname or port, add a separate browser profile
41
+
and keep the native self-signed profile unchanged.
32
42
33
43
If the browser or operating system already trusts the endpoint certificate, use **Public certificate**. Otherwise use the Windows or Android build, or place the WebSocket behind a publicly trusted TLS endpoint.
0 commit comments