Panelica Community Forum
Welcome to the official Panelica Community Forum — the central hub for server administrators, developers, and hosting professionals. Register a free account today to access technical discussions, product announcements, feature requests, and direct support from the Panelica team. Be part of the growing community shaping the future of server management.
Solved Addon Domain
- Thread starter Drakon
- Start date
Hi Drakon, thanks for the suggestion — this is a good one, and it is already on our list.
To be upfront: it is not a trivial addition on our side. Because every account on Panelica is fully isolated, letting one domain point at another account and serve the same document root has to be done carefully so it does not weaken that isolation. We would rather get it right than bolt it on, so it needs a bit of proper work.
That said, we do plan to take this on and ship it in the near term. I will update this thread once it lands. Thanks again for helping shape the roadmap.
To be upfront: it is not a trivial addition on our side. Because every account on Panelica is fully isolated, letting one domain point at another account and serve the same document root has to be done carefully so it does not weaken that isolation. We would rather get it right than bolt it on, so it needs a bit of proper work.
That said, we do plan to take this on and ship it in the near term. I will update this thread once it lands. Thanks again for helping shape the roadmap.
Hi Drakon,
Thank you for your patience, and again for the suggestion. As promised, here is an update.
We looked closely at addon domains. cPanel's addon domain has no exact one-to-one equivalent in Panelica, and it is not needed in the same form: every account here can already hold several domains (as many as its plan allows), each with its own site and document root.
For the case you described, a second domain showing the same site and files, we built Domain Aliases and have improved them since. Rather than letting one account serve another account's files, which would weaken the isolation between accounts, the second domain is added as an alias of the site it should show:
With these improvements we believe your request is covered, so we think this thread can be closed. If anything is still missing for your use case, please let us know; we will be glad to look at it.
Thank you again for helping us improve Panelica.
Thank you for your patience, and again for the suggestion. As promised, here is an update.
We looked closely at addon domains. cPanel's addon domain has no exact one-to-one equivalent in Panelica, and it is not needed in the same form: every account here can already hold several domains (as many as its plan allows), each with its own site and document root.
For the case you described, a second domain showing the same site and files, we built Domain Aliases and have improved them since. Rather than letting one account serve another account's files, which would weaken the isolation between accounts, the second domain is added as an alias of the site it should show:
- An alias is an extra hostname that opens the same site as one of your domains: the same files, with no separate document root or account and nothing to copy by hand.
- Add it on the domain's Aliases tab (
https://your-server:8443/domains/edit/<domain-id>#aliases) or on the Domain Aliases page (https://your-server:8443/domains/aliases). Enter the bare domain name and point its DNS to the server. - If the domain uses a Let's Encrypt certificate, the certificate is reissued right away to cover the new alias, as long as the alias's DNS already points to the server.
- Aliases work in every web server mode, whether nginx serves the site alone or passes requests to Apache.
- A name that is already used on the server as a domain, subdomain or alias is refused, so two sites can never claim the same hostname. If the domain currently exists as a separate site, remove it there first and then add it as an alias.
- To send visitors to a different address instead, use Redirects.
With these improvements we believe your request is covered, so we think this thread can be closed. If anything is still missing for your use case, please let us know; we will be glad to look at it.
Thank you again for helping us improve Panelica.
They would be fine if they worked properly. Every time I use one I get an error on the site saying:
No input file selected
Then I have to result to using Nginx Conf file to make it work right. Also what is the purpose of making a auto created users account myaccountkerbkjdfhvauhfrb? Can it be changed without messing things up if say I only wanted myaccount as the username?
No input file selected
Then I have to result to using Nginx Conf file to make it work right. Also what is the purpose of making a auto created users account myaccountkerbkjdfhvauhfrb? Can it be changed without messing things up if say I only wanted myaccount as the username?
Hi Drakon,
Thank you for coming back with the details — and we're sorry this hasn't been smooth. You're right to raise it.
On the "No input file selected" error with aliases: that is clearly something wrong on our side in how an alias is wired up to PHP, and it should not require you to edit the nginx config by hand. We're sorry for the hassle. Rather than guess, we want to reproduce it and fix it at the root, so we'll investigate this in detail and follow up here.
On the auto-generated username (e.g. myaccountkerbkjdfhvauhfrb): the random suffix is there to guarantee a unique, collision-free system user on the server, but we completely understand you'd prefer a clean name like "myaccount". We'll review how this is generated and whether we can make it cleaner, and come back to you.
Panelica is still a young project and we're improving it steadily — feedback exactly like yours is what drives that. Thank you for your patience; we'll update this thread once we've looked properly into both points.
Thank you for coming back with the details — and we're sorry this hasn't been smooth. You're right to raise it.
On the "No input file selected" error with aliases: that is clearly something wrong on our side in how an alias is wired up to PHP, and it should not require you to edit the nginx config by hand. We're sorry for the hassle. Rather than guess, we want to reproduce it and fix it at the root, so we'll investigate this in detail and follow up here.
On the auto-generated username (e.g. myaccountkerbkjdfhvauhfrb): the random suffix is there to guarantee a unique, collision-free system user on the server, but we completely understand you'd prefer a clean name like "myaccount". We'll review how this is generated and whether we can make it cleaner, and come back to you.
Panelica is still a young project and we're improving it steadily — feedback exactly like yours is what drives that. Thank you for your patience; we'll update this thread once we've looked properly into both points.
Hi Drakon,
Following up - and thank you again for the details.
On the "No input file selected" error with aliases: we reproduced it and sorted it out. On the current build an alias correctly serves the same site as its target domain, PHP included, so that error is gone and there is no need to edit the nginx config by hand. (On older builds the alias hostname was applied to nginx but not fully to the site's handler, which is what produced that error on PHP sites.)
On the auto-generated username with the random suffix: newer versions already create a clean username - a plain name, with only a numeric suffix if there is a clash - so new accounts will look the way you expect. Renaming an existing account's system user in place is risky (home paths, PHP-FPM pools and file ownership all depend on it), so we don't rename live accounts, but anything you create from now on will be clean.
Both of these are part of the update going out today, after it clears our tests. Once it reaches your server, could you please update, check your aliases again, and let us know how it goes?
Thank you very much for the feedback - it genuinely helps us improve, and we'd love to hear how it works for you after the update.
Best regards,
Panelica Team
Following up - and thank you again for the details.
On the "No input file selected" error with aliases: we reproduced it and sorted it out. On the current build an alias correctly serves the same site as its target domain, PHP included, so that error is gone and there is no need to edit the nginx config by hand. (On older builds the alias hostname was applied to nginx but not fully to the site's handler, which is what produced that error on PHP sites.)
On the auto-generated username with the random suffix: newer versions already create a clean username - a plain name, with only a numeric suffix if there is a clash - so new accounts will look the way you expect. Renaming an existing account's system user in place is risky (home paths, PHP-FPM pools and file ownership all depend on it), so we don't rename live accounts, but anything you create from now on will be clean.
Both of these are part of the update going out today, after it clears our tests. Once it reaches your server, could you please update, check your aliases again, and let us know how it goes?
Thank you very much for the feedback - it genuinely helps us improve, and we'd love to hear how it works for you after the update.
Best regards,
Panelica Team