You can set up aliases, i.e. additional domains running on the webhosting, only for NoLimit and NoLimit Extra webhostings. LowCost does not support aliases.
To change the web hosting tariff, follow the instructions Webhosting - Change tariff.
In this guide you will read:
- What aliases are for
- How to add or remove a web hosting alias
- How to set up an alias for:
- Common problems
- Frequently Asked Questions
Web Hosting Aliases
You can direct 3 more domains as aliases to each NoLimit and NoLimit Extra Webhosting space. If you need to host more domains, you can increase this number by purchasing the additional service Unlimited Aliases. LowCost web hosting does not support aliases.
With aliases, you can run several different websites on one Webhosting. These sites share:
- Web Hosting Performance: Individual sites on a Webhost share processes dedicated to the entire Webhost and thus place higher demands on optimization.
- Mailboxes: the space for emails and individual mailboxes is shared for aliases. For more information, see the chapter Email mailboxes for different domains.
Alternatively, you can use aliases for HTTPS redirection. For more information, see HTTPS Redirection.
Adding and removing an alias
Before you add an alias to your web host, make sure that:
- The (sub)domain being added is not the name of an existing alias, Webhost, Mailhost, or WebSite service. If you already have such a service in your customer account, remove its alias or rename it according to the instructions Webhosting - Rename, Mailhosting - Rename, or WebSite - Rename.
- The domain you are adding is at least temporarily in the same customer account as the Webhosting you are adding the alias to. If it is not, move it according to the instructions in Services - Move between accounts, or Domains - Move between accounts using an authorization password. This restriction only applies to domains registered with VEDOS, you do not need to move domains registered elsewhere. Alternatively, ask the customer in whose account the domain is located to grant you permissions to it by following the instructions in Administration - Authorized User.
Until these conditions are met, the system will not allow an alias to be added.
Alias Management Interface
To manage aliases, follow these steps:
- Log in to the customer administration ⧉.
- From the top menu, select Hosting Services Webhosting.
- From the list of web hosts, select the service to which you want to add an alias.
- Select Aliases from the left menu.

We also recommend using WEDOS DNS servers for the domain. This can automate part of the process.
Adding an alias
Changes in the system are reflected within 30 minutes, changes in DNS records within 1 hour.
Enter the alias domain in the form domena.tld. Avoid a name that contains the subdomain www.
To add an alias to your Webhosting, follow these steps:
- Access the alias management interface as described in the Alias Management Interface chapter.
- In the New alias box, fill in the alias domain.
- Decide on automatic DNS setup and Let's Encrypt certificate generation.
- Click the Add Alias button.

If you use WEDOS DNS servers, you can have the domain automatically redirected to a web host with an alias. The option to make changes on our DNS servers for the alias domain is automatically selected. The system will automatically change the A, AAAA and MX records for the (sub)domain. The DNS record changes will take effect within 1 hour.
If the domain is directed to the web host from an earlier time, you can automatically include the alias domain in the Lets Encrypt certificate. If the domain is not previously routed, the system will wait 10 minutes for the DNS to be resolved and then attempt to generate a certificate when this option is checked.
Removing an alias
To remove an alias, follow these steps:
- Access the alias management interface as described in the Alias Management Interface chapter.
- In the Alias Overview, click the cross icon next to the name of the alias that you want to remove.
- Confirm the deletion of the alias.

Setting an alias
You can use Alias to run multiple websites and emails on one Webhosting, or to redirect (with HTTPS).
Multiple websites on one Webhosting
By default, aliases display the contents of the www folder on the FTP Webhost. So you can see the same content on the domain and subdomains of the alias as on the main domain (if you have its content in the www folder).
Detailed instructions for setting up separate alias sites can be found in the article Webhosting - Separate sites for aliases.
Email boxes for different domains
By default, Webhosting mailboxes are shared by alias domains. For example, the info@domena.tld mailbox is shared (identical) with the info@alias.tld mailbox.
If you need to distinguish the mailboxes, you can set up an identity in WebMail &boxbox. You can find detailed instructions in the article WebMail - Alias mailboxes (identities).
Redirection with HTTPS
Basic domain redirection does not support https because the redirection server does not (and cannot) have an SSL certificate for the domain. You can issue a certificate for the alias domain (and its subdomains) on your own Webhost.
For instructions on how to redirect a domain with HTTPS, see Webhosting - Redirect a Domain with HTTPS.
Common problems
Common problems with setting up aliases include:
- A domain cannot be added as an alias
- Domain in another customer account
- Problem adding to Let's Encrypt certificate
- URL in the format domain.tld/domains/domena.tld
A domain cannot be added as an alias
Problem: Error: domain cannot be added as an alias - there is a separate webhost for the domain.
Cause: the domain is already assigned to another service - Webhosting, WebSite, or Mailhosting.
Solution: rename the conflicting service according to the instructions for renaming WebHosting, WebSite, or MailHosting, or remove the conflicting webhosting alias.
Domain in another customer account
Problem: Error: domain is in another customer account.
Cause: if the domain name is registered by WEDOS, you can only use it for security reasons if it is (at least temporarily) in your customer account or you have set permissions to it.
Solution: Arrange for the domain to be transferred to your account by following the instructions in Services - Transfer between accounts. After adding an alias or renaming, you can move the services back to your customer accounts in the same way.
Alternatively, ask the customer whose account the domain is in to grant you permissions to it by following the instructions in Administration - Authorized User.
Problem adding to Let's Encrypt certificate
Problem: Error: The following domains have encountered a problem when adding them to a Let's Encrypt certificate.
Cause: the problem with adding a certificate to Let's Encrypt is most often caused by a DNS pointing error. More rarely, it may be a temporary failure or CA downtime.
Solution: Make sure that DNS records are correctly directed to the web host. For example, you can use the domain/webhost diagnostics to do this. Caution - if the DNS servers (NSSET) have changed in the last 48 hours or the DNS records have changed in the last hour, the results may not be up to date.
If errors occur , complete the HTTPS setup manually according to this guide.
URL domena.tld/domains/domena.tld
Problem: The website displays the folder address in the browser address bar.
Solution: Make sure you check the current path in your PHP code using the variable $_SERVER[„REQUEST_URI“]
.
If you are using an editorial system, make sure you have the correct base address set up, for example, following the community guidelines for:
Frequently Asked Questions
How many websites can I run on one Webhosting?
This amount is determined by the performance of the web hosting plan and the consumption of the application. While the performance of the Web Hosting is clearly given, the requirements of the application depend on its optimization and traffic. Thus, during off-peak hours, several WordPress sites can run on the service without a problem, but during peak hours or during an attack, even one relatively undemanding site can end up with Error 503.