Cloud uploader setup

The Cloud Uploader uploads a guest’s finished content to the cloud account you connect, and turns it into a shareable link. It’s the foundation of link-based sharing — set it up first, before the other sharing services.

Currently supported cloud services: Dropbox and Yandex.Disk. Internet is required.

1. Authorize your cloud account

Open Cloud uploader settings, pick Dropbox or Yandex.Disk, and click Authorize. Authorization is similar for both:

• Dropbox — confirm that your Dropbox account grants this app permission; it returns a token.
• Yandex.Disk — if you’re already signed in, it authorizes right away.

Internet is required to authorize.

Do it yourself

Sign in and approve access directly in the service’s own window — never share cloud credentials in a document or chat.

12

1. Service (Dropbox / Yandex.Disk)
2. Authorized status

2. Set the upload path

Next to the service (Dropbox / Yandex), click Edit and set the Upload path:

1. Type the name of the folder you want to upload into.
2. Click Check path. If the folder exists and is reachable, it shows “Path is valid”.
3. If the folder doesn’t exist yet, click Create folder — the app creates it and marks it created.
4. Click Update to save. All new content now uploads into that folder.

Note

Paths are relative to the app’s own folder in your cloud (the app uploads into its own dedicated folder, not the cloud root).

How link-based sharing works (the link base)

12

1. Link options (link base size)
2. Redirect URL (default redirect link)

Content goes to the cloud — but venues don’t always have internet. To handle that, MixUp uses updatable links backed by a link base:

• The app keeps a base of links that it pre-fills whenever there’s internet, holding a supply ready to use.
• When a session ends, a link is already assigned to it — so the link is valid immediately and can be handed out right away.
• At first that link points not to the final content but to a default page you configure (your website, for example). Once the content finishes uploading, the same link resolves to the finished content.

Default redirect and base size

• Set the fallback page in Links options → Edit → Default Redirect Link — put your site (or anything) there. Until the content is uploaded, the link opens that page; after upload, it opens the content.
• In Edit Redirect Link Options you also set the size of the link base — how many links to keep pre-loaded when online.

How the buffer behaves

Each finished item takes one link from the base (base − 1). With internet, the base refills immediately. Without internet, the base is your offline buffer — you keep handing out valid links until it runs low, and it refills when internet returns.

Danger

Update Link Base resets the base. If you enter a new site and press Update Link Base, the old links already in the base are discarded and new ones are assigned. Do this deliberately, not mid-event.

Account

The link base and the cloud service use one unified account (KSuse) — a single token is enough. The link base does not use coins — it’s effectively free.

What you need

• Internet.
• A Dropbox or Yandex.Disk account. We strongly recommend a paid account: free accounts have API call limits (a cap on the number of API calls, not on storage size). MixUp minimizes calls, but a free account can still hit the limit quickly.

Why set this up first

The uploader powers most sharing: QR code, SMS, WhatsApp, Telegram, and even the email mode that sends a link instead of attaching the content. So configure the Cloud Uploader first, then set up the individual sharing methods.

Common uploader errors

Message	What to do
“Authorization error, check service authorization”	Re-run Authorize; the token expired or is wrong.
“Wrong cloud path, check upload path”	Fix the Upload path; use Check path / Create folder.
“No free cloud disk space”	Free up space on the cloud account.
“Connection timeout, check internet connection”	Check the booth’s internet.
“Api rate limit”	Free account hit its API limit — use a paid account; wait and retry.
“Cloud service issue”	The service is temporarily unavailable; retry later.

Next: Sharing methods →