REFERENCE
Troubleshooting.
Find your symptom below. If it isn't here, email us.
A link won't open#
Your computer serves the file, so the link only works while your computer is on, online and running the xposed daemon. Check, on the computer that made the share:
xposed daemon status
It prints daemon running with a process ID and uptime. (It starts the daemon first if it wasn't running.) Then list your shares:
xposed list
If the share isn't there, it was closed or it expired: links last 24 hours on Free (up to 7 days on Pro). Share the file again. If it is listed but the recipient still can't open it, make sure you're signed in on this computer (xposed login) and that your monthly transfer allowance isn't used up. What the recipient sees also tells you a lot: a page saying the link closed, expired or reached its download limit means exactly that.
"not invited yet"#
xposed login ends with:
error: not invited: no invite matches this email yet; ask the owner for one
Invites belong to an email address, and you signed in with one that hasn't been invited. Sign in with the GitHub or Google account that uses the address your invite went to. If you don't have an invite, request one at getxposed.link, or ask a friend to invite you from their dashboard. The dashboard says "You're on the waitlist" for an email that isn't invited.
Computer limit#
error: computer limit: this account's invites don't cover another computer
Your account is already using all the computers your plan allows: 1 on Free, 3 on Pro. Remove one you no longer use from the dashboard (the Remove button next to it), then run xposed login again.
File too large#
error: movie.mkv is 3.4 GB; files can be up to 500 MB
The file is over your plan's per-file limit: 500 MB on Free, 1 GB on Pro. Nothing was shared. Send a smaller file, or split or compress it. See Plans and limits.
Monthly allowance used#
When your monthly transfers are used up, xposed share still makes a link but warns you that downloads may be refused until the allowance resets, and shows the date. Downloads stop until then. Your dashboard's usage meter shows how much you've used and when it resets. Pro has a bigger allowance; you can upgrade from the dashboard.
"this install isn't set up"#
xposed share says this install isn't set up: run `xposed login` when this computer hasn't been signed in yet. Run xposed login. If you moved to a new computer, sign in there too.
xposed login can't open a browser#
xposed login prints a code and an address, then tries to open the address with xdg-open. If nothing opens, for example over SSH or on a system without xdg-utils, open the address yourself on any device with a browser, sign in, and type the code shown in your terminal. The command waits and finishes when you do.
The dashboard is on port 9767#
xposed serves its dashboard at http://xposed.localhost on port 80. Port 80 needs a capability that the packages grant to the daemon. If something else already holds port 80, or the capability is missing, the daemon uses http://xposed.localhost:9767 instead, and everything xposed prints uses that address. xposed open opens the right one, and xposed daemon status prints it.
To get port 80 back, grant the capability again (replacing the binary drops it) and restart the daemon:
$ sudo setcap cap_net_bind_service=+ep "$(command -v xposedd)"
$ xposed daemon stop
While xposed runs it holds port 80 on your loopback addresses, so another web server that wants port 80 on all addresses won't start until you run xposed daemon stop. Set XPOSED_PORT to make the daemon use a port of your choice instead.
Links don't come back after a reboot#
The daemon starts at login through an autostart entry, /etc/xdg/autostart/xposed.desktop, which runs xposed daemon start. That needs a desktop that supports XDG autostart, such as GNOME, and a graphical login. On a session without it, run xposed daemon start yourself, or add that command to your session's startup. Any other xposed command starts the daemon too. Check the entry is there:
ls /etc/xdg/autostart/xposed.desktop
"Share with xposed" isn't in the Scripts menu#
The right-click action is for GNOME Files. If you installed a package by hand, add the action for your user; the steps are on the Linux install page. Other file managers don't have it; use xposed share <file>.
Update problems#
xposed updatesays the binary wasn't installed from a release: you're running a build you compiled yourself. Update it the way you built it, or install a release with the installer.- It can't find the package manager that installed xposed: run the installer again, which updates in place:
curl -fsSL https://getxposed.link/install.sh | sh. - It won't install a release whose signature or checksum doesn't match. If you see that, don't work around it; tell us.
- To see what you have and what's available:
xposed versionandxposed update --check.
Contact support#
Email support@getxposed.link from the address on your account. Tell us what you ran, what you saw, and the output of xposed version. The daemon writes a log at ~/.local/share/xposed/daemon.log; we may ask for its last lines.