Change your service's onvoroa.com subdomain
Rename your service's free onvoroa.com address, like my-api.onvoroa.com, from Settings. What happens to the old name, the 30-day hold, and what to update.
To change your service’s default address, open the service, go to Settings → Custom Domains, and
select Change subdomain under Default subdomain. Type the new name - for example my-api for
my-api.onvoroa.com - and select Change and redeploy. Voroa redeploys the service on its own, and
the new address is live when the deploy finishes. The old address stops working at that point, and the
old name stays reserved for your workspace for 30 days before anyone else can take it.
When to change your subdomain
Every web service and static site on Voroa gets a free address under onvoroa.com, built from the name
you gave the service when you created it. That first name is often a working title - a repository name,
test-app, or a long description - and you may want something shorter to share, to put in a README, or to
point a CNAME record at.
If you want your service on a domain you own, like myapp.in, you do not need to change the subdomain:
add a custom domain instead. Your custom domain and your onvoroa.com address
both keep working side by side.
| You want | Do this |
|---|---|
A shorter or clearer onvoroa.com address |
Change the subdomain (this page) |
Your own domain, like myapp.in or www.myapp.in |
Add a custom domain |
| To rename the service in the dashboard only | Change Name under Settings → General - the address does not change |
Step 1 - Open Default subdomain
Open the service and go to Settings → Custom Domains. Scroll to Default subdomain. It shows the service’s current address with an Enabled badge, and a Change subdomain button.
Background workers and cron jobs have no public address, so they have no subdomain to change.
Step 2 - Enter the new name
Select Change subdomain and type the new name. Type only the name: Voroa adds .onvoroa.com for you.
The name must:
- be 1 to 30 characters long;
- use only lowercase letters, numbers and hyphens;
- start and end with a letter or number, with no two hyphens in a row;
- not already be in use by another service;
- not be a name Voroa keeps for itself, such as
www,api,adminorstatus.
If the name breaks a rule or is taken, Voroa tells you which, and nothing changes.
Step 3 - Change and redeploy
Select Change and redeploy. Voroa saves the new name and redeploys the service, because the address a service answers on is set when it starts. The deploy appears in the service’s deploy history like any other.
When the deploy finishes, open the new address to check it. HTTPS works straight away - every
onvoroa.com address is covered by Voroa’s certificate.
Step 4 - Update anything that used the old address
The old address stops working as soon as the new one goes live. There is no redirect. Update:
- links in your README, documentation, emails or social profiles;
- webhooks and OAuth callback URLs you registered with other services;
- environment variables in your other services that called this one by its old address;
- any custom domain whose CNAME record points at the old address - change the record to the new address at your registrar.
What happens to the old name
The old name is held for your workspace for 30 days. During that time no other workspace can take it, and you can change back to it if you need to. After 30 days it is released and anyone can use it.
The hold exists so that old links and bookmarks never land on someone else’s service the moment you rename yours.
Common problems
| What you see | Likely cause | What to do |
|---|---|---|
| That name is already taken | Another service uses it, or it is still held for another workspace | Choose a different name |
| That name is reserved | Voroa keeps the name for its own use | Choose a different name |
| Nothing was changed with a build minutes or free hours message | The change needs a redeploy, and you have no build minutes or free hours left this month | Wait for the monthly reset, or upgrade, then try again |
| The new address does not load right after the change | The redeploy is still running | Wait for the deploy to finish in the deploy history |
| A custom domain stopped working after the change | Its CNAME record still points at the old address | Point the record at the new address |
| This service has no public address to rename | It is a background worker or cron job | Nothing to change - these services have no public address |
Frequently asked questions
Does changing the subdomain cost anything?
No. The change itself is free. The redeploy it runs uses build minutes from your plan, like any other deploy.
Will my service be down during the change?
Your service keeps running during the redeploy. The old address answers until the new deploy is live, then the new address takes over.
Can I change back to my old name?
Yes, within 30 days, because the old name is held for your workspace. After that it may be taken.
Can I remove the default address completely?
Not today. Every web service keeps a Voroa address, even when you also use a custom domain.
My service has a getvoroa.com address. Is that still right?
Yes. Services created before Voroa moved default addresses to onvoroa.com keep their getvoroa.com
address and also answer on onvoroa.com. A rename gives the service an onvoroa.com address. See
New Voroa services get an onvoroa.com address.