Troubleshooting

Symptoms

The app says the server is older or newer than it works with

The app and the server differ in the first number of their versions, or by more than one in the second, so sharing pauses until one of them is updated; nothing is lost. Server older: an administrator updates it; server newer: update the app. See Version mismatch.

The server is unreachable, or links do not open from outside

Nothing on port 443 at your public address means no forward or a firewall; something else answering means the forward leads to another device. Open Servers, the server, Domain & Connectivity… and run the check, or hyperdrop domain status. See Router forwards.

The browser warns about the certificate, or HTTPS never comes up

HTTPS needs port 443 to reach the server and, for your own domain, both A records, files.<domain> included; one missing record leaves both names without a certificate. The first issue can take a few minutes. See The two DNS records.

Links stop opening behind a reverse proxy

The proxy's address is not listed, or it is listed and sends no PROXY header. The server log names the address and the reason. See the proxy guide.

Links answer "not found" in one browser and work in another

A wildcard certificate on another of your sites covers the HyperDrop name, and the browser reuses that site's connection. Keep the name outside the wildcard. See the proxy guide.

The Domain screen says port forwarding cannot work

Your ISP shares one public address between many homes (carrier-grade NAT). Ask them for a public IP address, which many ISPs grant on request or sell as an option; a dynamic one is enough. If they cannot, install on a VPS. See Carrier-grade NAT.

I lost my authenticator

A recovery code works in place of the 6-digit code, once each. Without them, choose Can't get a code?, then Reset with Server Management…, which turns the factor off over SSH. On a Synology NAS, stop the package in Package Center, run this over SSH, then start the package again:

sudo -u hyperdrop env HYPERDROP_DATA=/var/packages/hyperdrop/var/data /var/packages/hyperdrop/target/bin/hyperdrop-server reset2fa <account>

On DSM 6 the data folder is on the volume the package is installed on (replace volume1 if yours differs):

sudo -u hyperdrop env HYPERDROP_DATA=/volume1/@appdata/hyperdrop/data /var/packages/hyperdrop/target/bin/hyperdrop-server reset2fa <account>

Both run as hyperdrop, the package's own user, so every file the reset writes stays readable by the package; run as root, an interrupted reset could leave files the package can no longer open. An administrator is asked to set up a new factor at the next sign-in.

I forgot the admin password

In Server Management, run On a VPS against the same box: it finds the existing administrator and asks; choose Set a new admin password. Every share and link is kept. A box set up with the installer takes HYPERDROP_RESET_ADMIN=1 on a second run. See the installer.

Package Center refuses the package

On DSM 6, set Package Center's Trust Level to Any publisher first; on DSM 7, answer the third-party warning with Agree. "Invalid file format" means the package is for another DSM version or processor: download the right one.

If it still refuses, install from the NAS terminal. Turn on SSH in Control Panel → Terminal & SNMP, sign in as an administrator, cd to the folder holding the .spk file and run both lines with your own Admin username (the one you gave Server Management), password, address and file name:

sudo wizard_admin_user=admin wizard_admin_password='your password' wizard_ddns_name=alice /usr/syno/bin/synopkg install hyperdrop.spk
sudo /usr/syno/bin/synopkg start hyperdrop

For your own domain, use wizard_domain=share.example.com in place of wizard_ddns_name=alice. Type the password in the NAS terminal only, never in a chat; write a ' in it as '\''. DSM 6 prints only error = [263] on a refusal; the reason is in /tmp/synopkgmgr.log-hyperdrop.

apt or dnf refuses the HyperDrop repository

apt says The repository 'https://gethyperdrop.com/downloads stable InRelease' is not signed: the key is missing or unreadable at the path the source file names. Download it again to /usr/share/keyrings/hyperdrop-packages.asc with the command on the command line page, then run sudo apt update.

The first dnf install asks whether to import a key, once for the repository and once for its packages: accept it only when the fingerprint reads 9D09 3499 BE6A DB30 C38F 3DAE 80AC 6826 B880 0F72. A signature or checksum error just after HyperDrop published an update means the indexes were fetched mid-publish: run sudo dnf clean metadata or sudo apt update again.