Cloud Account Compromised? The X-plore Session Clean-Up Checklist
Suspect a compromised cloud account? Contain it at the provider first, evict every session and token, inspect the damage, then rebuild your X-plore connections.
Suspect a compromised cloud account? Contain it at the provider first, evict every session and token, inspect the damage, then rebuild your X-plore connections.
Ten minutes, the same layout, four verdicts for every file. A weekly dual-pane routine that stops Downloads turning into archaeology.
LAN, the FTP server, and Wi-Fi sharing move files in different directions with different trade-offs. Pick by direction, privacy, and convenience, not habit.
WebDAV over HTTPS encrypts your credentials and files in transit and proves your server’s identity. Move X-plore entries off HTTP and read warnings properly.
Turn a drive of camera dumps into a family archive the TV can browse: year-and-event folders, a Favourites set for guests, and players chosen per format.
Duplicates hide by name and breed in Downloads and chat folders. Map first, search by extension and size, prove each copy, and quarantine before deleting.
Give a Raspberry Pi a fixed address, enable SSH, add Samba, and save both SFTP and SMB connections in X-plore for a reliable home server.
Sharing links grant access to one file or folder without exposing your account, if you choose the lowest access, set expiry where offered, and revoke links afterwards.
A freeze has an address. Work the layers in order — the TV itself, X-plore’s cache and data, then the drives and shares — and the culprit identifies itself.
Never edit the only copy. A rescue duplicate, one change at a time and an immediate test make X-plore’s small editor safe for configs and subtitles.