Support

How can we help?

Find answers to common questions, troubleshoot issues, or reach out directly — we're here to help you get the most out of Volans.

Contact

Get in touch

Choose the channel that works best for you.

Email Support

Send us an email and we'll get back to you within one business day.

GitHub Issues

Found a bug or want to request a feature? Open an issue on GitHub so the community can track and discuss it.

Follow on X

Stay up to date with releases, tips, and announcements. You can also DM us for quick questions.

Troubleshooting

Step-by-step solutions to the most frequently reported problems. Click any issue to expand the fix.

This usually means the Railway API is unreachable or your token has been revoked.

Open Volans → Preferences → Account and verify your API token is present.
Visit railway.app in your browser to confirm Railway itself is accessible.
Go to your Railway account settings and confirm the token hasn't been revoked or expired. Generate a new one if needed.
Remove the old token in Volans, paste the new one, and reconnect.
If the issue persists, check status.railway.app for any ongoing Railway outages.

Your Mac must have Touch ID hardware or an Apple Watch set up for unlock.

Open System Settings → Touch ID & Password and make sure at least one fingerprint is enrolled.
If you use an external keyboard without Touch ID, ensure Apple Watch unlock is enabled in macOS System Settings.
Quit Volans completely (⌘Q) and relaunch — this refreshes the Keychain session.

Log streaming relies on the Railway API and your internet connection.

Click the Refresh button (circular arrow) in the log toolbar.
Check that the service you're viewing is actually running — logs from a crashed or stopped service won't stream.
If no logs appear at all, check your macOS firewall settings: System Settings → Network → Firewall. Volans must be allowed outbound connections.
Quit and relaunch Volans to reset the log polling session.

macOS controls which apps can send notifications. If you dismissed the initial permission prompt, notifications will be silently blocked.

Open System Settings → Notifications.
Find Volans in the list and ensure "Allow Notifications" is turned on.
Check that the alert style is set to Alerts (not Banners, which auto-dismiss) if you want persistent notifications.
Make sure Do Not Disturb or Focus mode is not suppressing alerts.

A crash on launch usually means a corrupted preference file or a macOS version incompatibility.

Verify your macOS version is 14.6 (Sonoma) or later — Volans does not support older macOS releases.
Open Console.app, filter by "Volans", and look for the crash report to identify the exact error.
Reset preferences by running this in Terminal: defaults delete app.getvolans.Volans, then relaunch.
Re-download the latest DMG from getvolans.app/download and reinstall — your existing license and Keychain data will be preserved.
If the crash persists, send the Console crash report to support@getvolans.app.

The menu bar icon appears only when Volans is running. If it disappears after a reboot, Volans isn't set to launch at login.

Open Volans and go to Preferences → General.
Enable the "Launch at Login" toggle.
If the icon still doesn't appear, your menu bar may be overcrowded — hold ⌘ and drag other icons to make room, or use an app like Bartender to manage overflow icons.

Redeploy and rollback require sufficient Railway account permissions.

Make sure your Railway API token has write access — read-only tokens cannot trigger deployments. Regenerate the token from Railway account settings with full permissions.
Check that you are an owner or editor of the Railway project — viewer-only members cannot trigger deployments even with a valid token.
If the action appears to do nothing, wait 10–15 seconds and pull to refresh the deployment list — Railway queues deploys and the status may not update instantly.