I want to create a Cpanel account for a subdomain which the main domain also hosted on the same server.
" The domain “sub1.example.com” already exists in the userdata"
There is a WHM tweak setting called 'Allow cPanel users to create subdomains across accounts'. Make sure this is set to 'on'.
But, the specific error makes it sound like the subdomain was already created elsewhere. If you have created a dns zonefile entry for sub1, or if you have already added sub1 to another cpanel account, you won't be able to create a new account of it. Make sure that subdomain is removed from any other accounts before you try to re-add it.
Related
I created an image that is uploaded to WDS, with an answer file used for joining the Device to a Domain. Whenever I deploy, a new user is created on the new machine for this Domain user, called DOMAINNAME.Username. I would like to set it up in a way that this Domain user uses the useraccount called Username, which is also on the machine and has all the data of the sysprepped image.
I know it can be done, as I also have images that use the local account that was sysprepped as the domain account of the deployed machine.
Can anyone tell me what step I am missing that leads to what I am experiencing?
I have a domain name which i need to to point to a sub domain of my existing website. Both the domain name in question and website are held with the same host so i have CPanel for the website (which has its own domain name and is currently online. Note the host does not provide CPanel (or similar) for domain-names only (i.e. without hosting).
I have seen subdomains and addon domains but from the description in CPanel i cant figure which if either will do what i want ... or even Aliases.
How can i point the domain name to a sub-domain? if possible. I do not want the existing websites domain name to appear in the url when visiting the sub-domain pointed to by the new domain name.
Thanks.
Since you're using cPanel... https://documentation.cpanel.net/display/ALD/Setup+Edit+Domain+Forwarding
If you just deal with a registrar instead of a provider, typically you point '#.domain.com' to 'http://sub.domain.com' - where #.domain.com represents the direct name, domain.com.
I'm looking to point a new domain name to my website sub domain address.
So would all I do is buy the new domain name address and use httaccess to tell my site when the new domain name is entered to go to www.newdomain.mydomain.com. How might I go about doing that?
But I'm hoping to have the new domain name address still be shown when they are on my sub domain as this is for a festival I am helping with and they don't need to buy hosting for this short period.
Any help is appreciated.
One way to get the url to stay as the one a user typed in instead of showing up as your subdomain is to put the whole site in a frame that loads your subdomain inside of it. Some registrars will do this for you so you don't need to pay for extra hosting. If you go with this option, you don't really need a subdomain, though, as you could just put the new pages in a folder off of your main site since visitors won't see the address anyway.
A slightly more elegant solution would simply be to use virtual hosts, if your server has the capability. If you have your own server, they are not hard to set up. If you have a hosting package from a company like godaddy, the company website will often give instructions on how to do this. The idea is that the server will handle the responsibility of routing a query to a specific folder based on the url of the request. Then all you need to do is set up the folder. If you give more specifics about what your hosting setup is, it will be easier to give guidance in this respect.
To get your new domain name to point to your website you need to:
configure your domain name to point to your web site IP address
configure your web server to serve your website when it receives requests to that new domain name
The company from which you buy your new domain name will provide you with a web interface to configure your domain name and make it point to your IP address.
If you're managing your web server yourself, you will need to edit its configuration to add a new named virtualhost for your new domain name (virtualhost directives don't go into .htaccess files). If you're using a shared hosting company, they probably also provide a web interface to configure your web site, so that it accepts requests to your new domain name.
Currently, if we create a customer in the admin panel / backend of our site, that customer is unable to login using the email address we used in creating the customer profile. Even after resetting the password using a custom and self -generated one.
I looked at the database and noticed that customers’ emails that sign-in through the front are placed in the api_user table and customers created in the backend are placed in the customer_entity table.
Anyone know why this is? Is it a latency from 1.3.2 and is hiccuping from our upgrade to 1.4.0.?
Thanks again for any and all help.
Well dibbly do. I solved this issue by going into:
Configuration > Customer Configuration > Share Customer Accounts > Global
Then, in the backend admin account creation I made sure to select the proper store for the customer being created.
When a new user signs up, many sites create a new domain, something like newuser.example.com
Does this mean that they have separate directories for every user, and copy the code base into the newly created directories and create sub domains? What is the best way to do this?
Refer here:
When you auto-create subdomains on user signup does it create a new website or gives appearance of a website?
Surely a DNS rule of * -> IP address would take care of adding the subdomains quickly. Then its up to the web server to deal with the different host headers.
I would then create a new Apache directive for each different host header I needed (one for each subdomain) and have them be aliases for real website.
You can setup a wildcard domain *.yourdomain.com and handle the differences within your code if the application is pretty much the same between subdomains. Everyone comes to the same application and you just parse out the subdomain and store it in a variable which can be used to lookup different data in your database and / or render different templates / themes, etc.
I.e. subdomain_fu