v0.3.11-alpha

New

• Easier first run. A fresh install starts with one working inbound: udp-obfs on a random free UDP port, printed at the end of the install. A panel installed together with its node (install both) already knows the server address and the subscription endpoint, so Publish works without visiting Settings first.
• The panel says what blocks a save. It opens the fields that need attention, moves to the first one and shows how many are left. Keys, path and cookie fill in by themselves when you pick tls, ws or fronted.
• Xray form: it says what is still missing, and choosing Xray without the add-on tells you how to install it. The default port is 2053, away from 443, which other panels often hold.
• Publish to apps appears right after you apply an inbound change. Apps only get new ports or transports after a publish.
• Setup checklist on the dashboard: inbound, server address, endpoint, publish, first user. It hides when all are done.
• Tunnels are easier to find. Links between servers are now called "Tunnels and links", and the docs guide is "Tunnel: a server in Iran in front of a foreign server".
• Rarely needed fields moved under Advanced, and the Persian panel uses the words people already use: اینباند, ترنسپورت.
• Docs: a Quick start, an FAQ (same server as x-ui, iPhone, routers, leaks, family use) and a newcomer-first menu.

Updating

Run sudo bash veilway.sh update both, or update node on a server without the panel. Existing servers keep their config: the new first inbound is only for fresh installs.

Docs: https://veilway-project.github.io/veilway-docs/
Questions: https://t.me/VeilwayGroup

v0.3.10-alpha

Veilway Panel v0.3.10-alpha. Still an alpha: no outside security review yet.

New

• Rules can name a country. geoip:tr, geoip:de and so on in a rule's destination network match every address registered in that country. Each release carries the list as veilway-geoip.txt, built from the five internet registries' public files, checked by the node and signed like the other files, and veilway.sh installs it. On an entry server, send your country's sites out the Direct exit and everything else abroad.
• Node links find their own MTU. A link tests the largest packet its path carries in both directions and lowers its MTU to that, within a minute of coming up and every 10 minutes after. This fixes links where pings worked but large transfers hung. The configured MTU stays the ceiling. Both servers need v0.3.10; with an older one the link keeps its MTU as before.
• The panel's link cards show the MTU in force, and whether it was found by testing or is the configured one.
• New guide: reach a home server through your VPS. The entry node guide now covers running both servers from one panel, picking the link's transports, keeping domestic sites on the entry and what each link state means.

Fixes

• The veilway command runs with a larger stack, which a Windows debug build had outgrown.

Updating

Run sudo bash veilway.sh update node twice, or update both twice for a server with the panel. The first run still uses the installer you have, which does not know the country list. The second run installs it at /usr/local/lib/veilway/geoip.txt. A rule that names a country does not validate until the list is there.

Docs: https://veilway-project.github.io/veilway-docs/
Entry node guide: https://veilway-project.github.io/veilway-docs/guides/entry-node/
Home server guide: https://veilway-project.github.io/veilway-docs/guides/home-server/
Questions: https://t.me/VeilwayGroup

v0.3.9-alpha

Veilway Panel v0.3.9-alpha. Still an alpha: no outside security review yet.

New

• A new installer menu. sudo bash veilway.sh shows what is installed and running at the top, groups its items, and takes the arrow keys or a number. Logs, Restart, Admins and Restore offer a list to pick from. An install shows its steps and a summary before it changes anything, and Uninstall and Restore ask you to type the word. Commands with flags work as before.
• Web server in the menu. Set up a web server for a panel that has none, check it, edit the decoy page, or remove it.
• Add to this server's web server. In the panel, a button under a ws or fronted transport's Web server lines puts its path into the web server that veilway.sh set up. The host checks each path, tests the config, reloads the web server, and takes the change back if the web server refuses it.
• A Generate button for a transport's path.

Fixes

• The transport on/off switch sits on its own row, so its hint reads in full.
• The node card in the sidebar no longer cuts off its last row.

Updating

Run sudo bash veilway.sh update both once from a terminal, or use the panel's update buttons. The update adds the helper that the Add to web server button needs, and the line the site file needs to include its folder.

Docs: https://veilway-project.github.io/veilway-docs/
Guide to the decoy site: https://veilway-project.github.io/veilway-docs/guides/decoy-site/
Questions: https://t.me/VeilwayGroup

v0.3.8-alpha

Veilway Panel v0.3.8-alpha. Still an alpha: no outside security review yet. This release is for the panel. The node and the apps only change their version.

Changes

• Rename the borrowed-site profile. Its name now starts with the name you give the inbound's other profile on Profiles, and " (borrowed site, alpha)" stays at the end. Before, it always started with the inbound's tag, and renaming the other profile did not reach it. A long name is cut so the whole name fits in 64 characters.
• No profile for a link's inbound. An inbound that a node link connects to no longer gets a profile. Before, Publish profiles would have offered users a connection they could not use.

Updating

sudo bash veilway.sh update both, or the panel's update buttons. After updating, open Profiles and choose Publish profiles to rename the borrowed-site profile.

Docs: https://veilway-project.github.io/veilway-docs/
Questions: https://t.me/VeilwayGroup

v0.3.7-alpha

Veilway Panel v0.3.7-alpha. Still an alpha: no outside security review yet.

This release only follows the core version. Nothing changed in the panel apart from the version: v0.3.7-alpha is a desktop app fix (the app now says when the kill switch is blocking the internet). See the core release notes: https://github.com/veilway-project/veilway/releases/tag/v0.3.7-alpha

Updating

sudo bash veilway.sh update both, or the panel's update buttons.

Docs: https://veilway-project.github.io/veilway-docs/
Questions: https://t.me/VeilwayGroup

v0.3.6-alpha

Veilway v0.3.6-alpha. Still an alpha: no outside security review yet. This release is mostly for servers and the panel.

Important when you update

• Users can now reach your server's own public addresses. Earlier versions always refused them. If other services listen on the server's public IP (another VPN panel, a database, an admin page), add this routing rule to block them:
  {"tag": "no-self", "ip": ["host:self"], "action": "reject"}
  You can combine host:self with the usual rule conditions, for example to allow one port for one user. Loopback stays blocked, so the panel itself (on 127.0.0.1) is never reached through the tunnel.

New

• Speed limits per user. Set a download and an upload limit in the panel (in Mbit/s), one user at a time or in bulk. All of a user's devices share it. TCP is slowed smoothly; other traffic over the limit is dropped. DNS and the app's control connection are never dropped. Each server enforces the limit on its own. Apps do not show it.
• A built-in WireGuard outbound. Paste a WireGuard config (Mullvad, a home server, any wg-quick peer) and an exit leaves through it. The node runs the tunnel itself: no wg-quick, no system setup. It goes down and up again by itself, and nothing leaves around it while it is down. Guide: https://veilway-project.github.io/veilway-docs/guides/wireguard-outbound/
• Other providers (upstreams) work like the apps. Automatic connection choice with failover across the provider's connections, a transport choice, the provider's exit switched without reconnecting, and the app's status in the panel: quota, account expiry and notices.
• Self-signed node links. A link can use the server's own certificate, trusted through its pin alone, so a second server needs no domain. The node now works out the pin of every certificate, the panel adds it to link offers, and the node warns when a certificate's key changes. A link whose key no longer matches shows "pin mismatch", not "unreachable".
• Link chaining, opt-in. A link's traffic may continue through another link when you turn on "Let this link continue through another link". At most three links in a row; never through another provider.
• Connection order. Order the connections in subscriptions on the Profiles page, and per user on the user's page. Servers now follow their position.
• 64 devices per user (was 16).
• The apps' local proxy is faster through far exits, and the server's TCP stack now slows a sender down instead of buffering in memory when a destination is slow.

Fixes

• The panel refuses an exit the server does not have, and refuses removing an exit that users still name. Before, the server refused every later user change and nothing said so; now a red banner on every page says when the server refused a push, with Push again.

Updating

sudo bash veilway.sh update both, or the panel's update buttons. The desktop and Android apps need no update for this release, apart from the faster local proxy.

Docs: https://veilway-project.github.io/veilway-docs/
Questions: https://t.me/VeilwayGroup

v0.3.5-alpha

Veilway v0.3.5-alpha. Still an alpha: no outside security review yet. This release is about the desktop and Android apps.

New

• Pick a transport, or leave it Automatic. A connection with several transports now has a Transport list while disconnected. Automatic, the default, tries them and keeps the one that works, and moves on when one is blocked. A picked transport is used alone, which helps on a network where you know what gets through. The app remembers the pick per connection. A transport weaker than the connection's best still asks for your yes first, and the borrowed-site transport still needs Alpha transports in Settings.
• The card names the transport in use once connected, such as ws.
• The connection list is grouped by subscription, under each provider's name.
• Download mirrors for the Xray add-on in the desktop app, under Settings, for when GitHub is blocked: up to 4 https:// addresses with the layout of GitHub releases. The download is still checked against the version built into the app, so a mirror cannot hand over another file. The app sends them with the install; its background helper never reads them from its environment.
• Menus stay inside the window, with long descriptions wrapping.

Updating

Update the desktop and Android apps for the changes above. The panel and servers have no user-facing change; sudo bash veilway.sh update both keeps them in step.

Docs: https://veilway-project.github.io/veilway-docs/
Questions: https://t.me/VeilwayGroup

v0.3.4-alpha

Veilway v0.3.4-alpha. Still an alpha: no outside security review yet.

Fixes

• Windows: the internet works again right after you disconnect. Names could stay unresolved until you turned the network off and on, because Windows kept the lookups the kill switch had blocked while the tunnel closed. A disconnect now empties that cache once the kill switch is gone, and so does the cleanup after a crash. Until you update, ipconfig /flushdns does the same.

New

• Two-step sign-in is a choice at install. A fresh install of the panel asks whether to ask for an authenticator code at sign-in. The answer is yes unless you say no, and the question says what no costs. --no-two-step says no for a script. A panel that is already installed keeps its setting. Not recommended for a panel with real users.
• Xray-core v26.10.21 on servers and in the desktop apps, up from v26.3.27. This release of Xray trusts only the root certificates built into it, and its freedom outbound refuses private and loopback addresses unless told otherwise; Veilway uses neither, so nothing changes for its traffic.
• veilway.sh --help shows every flag again.

Updating

Update the panel and every server: sudo bash veilway.sh update both. Update the Windows app for the fix.

Servers with the Xray add-on: run sudo bash veilway.sh addon xray install right after the update, or run sudo bash veilway.sh update both a second time. The node starts only the Xray-core it pins, so until then Xray's users cannot connect. The update runs with the installer that was already on the server and saves the new one for next time; from this release on, update installs the add-on again by itself when the pinned Xray-core changes.

Docs: https://veilway-project.github.io/veilway-docs/
Questions: https://t.me/VeilwayGroup

v0.3.3-alpha

Veilway v0.3.3-alpha. Still an alpha: no outside security review yet.

New

• Android: a quick settings tile and a home screen shortcut. Both turn the last connection on or off without opening the app. Add the tile from the quick settings editor, or touch and hold the app icon and drag Connect or disconnect to the home screen. Touch and hold the tile to open the app. Both need one connection made from the app first. On Xiaomi phones, turn on Autostart for Veilway, or the phone does not let them start it while the app is closed.
• A different plain page on every server. Every install used to serve the same page, so a search for it found Veilway servers. The installer now draws one for each server (topic, text, dates, type and colors). sudo bash veilway.sh update replaces the shared page if you never edited it. A page of your own is still the best cover.

Updating

Update the panel and every server: sudo bash veilway.sh update both. Update the Android app for the tile and the shortcut.

Docs: https://veilway-project.github.io/veilway-docs/
Questions: https://t.me/VeilwayGroup

v0.3.2-alpha

Veilway v0.3.2-alpha. Still an alpha: no outside security review yet.

New

• A domain install needs no trip to Settings. When you open the panel at your domain for its first setup, it sets the node address to that domain and adds the endpoint main at https://<domain>/sub/main as the default. A setup at an IP address leaves both to you, since that endpoint needs a pin. Panels set up before keep their settings.

Fixes

• Two tests that failed now and then on the macOS and Windows build machines are fixed. Nothing changes for users.

Updating

Update the panel and every server: sudo bash veilway.sh update both. Apps need no update. See v0.3.1-alpha for the decoy fixes, if you skipped it.

Docs: https://veilway-project.github.io/veilway-docs/
Questions: https://t.me/VeilwayGroup