Documentation/Connecting/Your own panel/If something is wrong·4 / 9
If something is wrong
Start with two commands: sudo veli panel shows the panel's state, and sudo veli doctor on a node's server shows why a device does not connect.
The panel does not open
sudo veli panel on its server shows whether it runs. Open port 443, and with a domain 80 too, in the host's firewall if it has one of its own.
No certificate was issued
The domain must point at the panel's server and port 80 must be open. The last error is shown by sudo veli panel. With no domain the panel is set up by IP: --host.
The server does not download the command
Our site may not open from some countries, Russia for one. Download the veli file to a computer, copy it to the server — scp veli root@<address>:~ — and run the line without the curl part. For a node over SSH — nodes add with --from and --node-from.
nodes add stopped
It names the reason in words and puts the server back as it was, so running it again is safe. It needs root (--ssh root@address) and a fingerprint that matches: if it does not, the address is wrong. A script gives the fingerprint beforehand — --fingerprint.
A node is silent or “has not reported yet”
On the node's server sudo veli panel shows when the last report went. The node needs to reach the panel at its address — check curl -I https://panel.example.com and port 443. Then run the same nodes add.
A client does not see a new node
A node comes with the next refresh of the subscription — refresh it in the app. Check the client's group too: the node may not be in it.
A token is lost
It is shown once. Revoke it — sudo veli token revoke site — and issue a new one.
A client or a node is gone
Bring the panel back from a copy — sudo veli panel restore.
API
Common errors of the API and the webhooks, and what to do about them.
400 name- The name is empty, longer than 40 characters, has control characters, is of the form c_ and 12 characters or is a word of the API: bulk, find
400 taken- That name is taken
400 none- No client, node or group by that name
400 bad- A value out of bounds, an unknown group or node. field names the field, max the limit
400 main- The mini-panel's main node is never turned off or taken away
401 token- No token, or it is revoked or expired. veli token list on the panel's server shows whether it still exists
403 rights- The token lacks the rights: for example, only “All” can delete clients. GET me shows the rights
404 none- Something that does not exist, or an unknown call
409 idempotency- This Idempotency-Key was already used by another request. A key is for one action: extending and creating get different keys
411 length- A body without Content-Length (chunked): send it whole
413 big- The request body is over 1 MB, max is the limit. Split a change of many into parts
429 wait- Over 300 requests a minute on the token, or ten wrong tokens from this address within 15 minutes. Wait as many seconds as Retry-After says
500 db- The panel could not save the change — repeat, with the same key
“Not found” for every request
A wrong API address: check the domain, the secret path and /api/ — veli token add prints the API address with the token.
A CORS error in the browser
That is on purpose: the token is for your servers, a page in a browser does not ask the panel. Let the page go to your server, and your server to the panel.
The signature does not match
Almost always the body was already parsed and built anew. Take the raw bytes: in Express — express.raw, in Flask — request.get_data(). And check that the secret is this webhook's: a webhook added anew has another secret.
No events at all
The webhook is not in veli webhook list, the event you need is not named in --events — or the panel is not running: sudo veli panel on its server shows that.