Manual configuration

If you cannot install the Colitu app on a device (a router, an OpenWrt box, a NAS, a Linux server) or you prefer another client, you can download a ready-made configuration file instead. The file connects to Colitu servers with your plan, the same way the app does.

#Create a file

1. Open colitu.com → Manual configuration.
2. Give the export a name that tells you where it will be used, for example "Home router".
3. Choose a server, or All servers, and a format (see below).
4. Press Create and download.

You can also copy the content, and for Share links the page shows a QR code you can scan with a phone client.

#Keep the file secret

The file contains a secret that gives access to your VPN, like a password. Do not share it or upload it anywhere public. Each export has its own secret, so if one leaks you cancel only that export and your other devices keep working.

#Device slots and limits

• Every export counts as a device and uses one of your plan's device slots, exactly like an app. If all slots are in use, creating an export fails with "Device limit reached".
• You can have up to 10 exports at a time.
• If your plan gets fewer slots, an export can be paused like any other device. Remove a device or upgrade your plan to use it again.

#Cancel an export

On the same page press Cancel next to the export. Its secret is removed from the servers right away: whatever uses that file can no longer connect. Cancelling cannot be undone; create a new export if you still need one.

#Download again and updates

Press Download again to get the file again; it always carries the same secret. A file is a snapshot of the server list at the time you download it. If a server changes its address, the old file may stop working: download it again and import it again.

#Formats and how to import them

sing-box (JSON)

1. Save the file, for example as colitu.json.
2. Run sing-box run -c colitu.json.
3. Point your apps at the local proxy 127.0.0.1:2080 (HTTP and SOCKS).

The first server is the default. To use another one, change the "default" value of the proxy selector in the file. Hysteria2 and TUIC servers are included.

Xray (JSON)

1. Save the file, for example as colitu.json.
2. Run xray run -c colitu.json. Use a recent Xray (v24.11 or newer) so the XHTTP servers work.
3. Point your apps at the local SOCKS proxy 127.0.0.1:10808.

Xray sends everything to the first server in the file. To use another one, change outboundTag in the routing rule to that server's tag. Xray cannot connect over Hysteria2 or TUIC, so those servers are left out of this format.

Clash / mihomo (YAML)

1. In Clash Verge, mihomo Party or similar: Profiles → New → Local file (or drag the file in).
2. Select the profile and pick a server in the PROXY group.
3. Turn on the system proxy or TUN mode. The local mixed port is 7890.

XHTTP servers are not available in Clash profiles.

Share links (v2rayN, NekoBox, Hiddify)

The file is a text file with one link per line (vless://, trojan://, hysteria2://, ss://, tuic://). Copy the content (or use Copy links) and import it from the clipboard:

• v2rayN: Servers → Import bulk URL from clipboard (Ctrl+V).
• NekoBox / NekoRay: Server → Add profile from clipboard.
• Hiddify: New profile → Add from clipboard.
• A phone client: scan the QR code on the page, one link at a time.

Which protocols work depends on the client; if a client does not understand a link it skips it.

OpenWrt (HomeProxy, PassWall)

Use Share links, because these add-ons import links and set up routing for you:

• HomeProxy: Node Settings → Import share links → paste the links → Import, then pick the node on Client Settings.
• PassWall / PassWall 2: Node List → Add the node via the link (import) → paste the links, then choose the node in Basic Settings.

#What a manual file does not include

Manual files only connect you to a server. The app's kill switch, split tunnelling, automatic server choice, Multihop and ad blocker are app features and are not part of these files.

#If it does not connect

• Check the date and time on the device; a wrong clock breaks encrypted connections.
• Make sure the export is still listed and not paused on Manual configuration.
• Try another server or format, or download the file again.
• See Connection problems or contact support.