I am new to Hetzner so I am sorry if my question doesn't make sense.
Long story short, this is my situation:
I have 2 WordPress Websites and each of them is hosted in a different hosting, from a different hosting provider (not Hetzner).
My goal is to host both of my WordPress Websites in one account on Hetzner (one hosting).
I asked this question before and I got told that I should buy Web Hosting Level 9 package, so that I can add both of my sites as add on domains and that they can be literally 2 different WordPress Websites but they would have the same hosting (site1.com and site2.com , but same host).
And I did just that. I purchased Web Hosting Level 9 package and during the purchasing process I had to claim a free domain. I did that and used "aisolutionmontenegro.com" , but I don't plan on don't anything with this particular domain.
Now after that I added the domain my first WordPress Website as a add on domain, and it showed up.
The problem that I am facing is that I want to install WordPress to this first add on domain, but I can not see the option "WordPress" on the Services part, like I see it when I am on the main domain that I claimed for free "aisolutionmontenegro.com".
The domain I claimed for free
Remember, I don't need aisolutionmontenegro.com at all, I just want to add two add on domains and on each of them install WordPress. Is that possible and how?
The domain of my site
Thank you in advance!
I found out what the problem was.
When I added the "main" domain with I claimed for free while buying Web Host Level 9 package from Hetzner, I had to go to "Products" and then select the "main" domain.
After I selected the main domain, in the left side menu, go to Services and you can see there WordPress. We click WordPress and then go to the installation process.
During the installation process you have to choose a root directory for your site, and here is where you need to be careful.
If you want to install your WordPress site on an add on domain (let's assume its called "site1.com") then you need for the root directory to create a new folder called the name of your site (in this case create a folder "site1").
After that you can continue with the installation process normally.
And for every add on domain that we want to install WordPress on we do the same thing, we click on the "main" domain, and then we click WordPress. During the installation process as the root directory we create a new folder called like the add on domain (for example our second add on domain is called "site2.com", we create a folder called "site2").
Related
The title is purposely generic as I have no clue to formulate my question in any different way.
I have made an MVC 5 project using .NET 4.7.
My goal is to use IIS 10 to point to a domain so I can use that as a testing ground.
I have already edited my host-file to point my localhost ip to the domain I have in mind.
After that I have followed every step mentioned in the video below meticulously.
However I keep ending up on the 403.14 error page.
I have adjusted security to no avail, checked the app-pool to use the correct .net version... I'm all out off ideas.
https://www.youtube.com/watch?v=IwbKquNBNgQ
I hope someone here has some idea of things I have not thought of myself, so feel free to ask anything you think might make the change I need to make this work. I will edit this message (and title) as much as needed to keep up to date as possible.
EDIT: I have followed the full guide that I have marked as an answer. I had 3 differences.
Difference 1 was in Windows Features. I think I just plain didn't correctly mark all the needed features..
Difference 2 was in Security. I did not have IIS_IUSRS added, only IUSR
Difference 3 is one I have purposely keep a difference and that is Directory Browsing. Without this being enabled, it works for me.
I hope that if anyone ends up on this page in the future, the answer provided below will be as helpful as it has been to me.
make sure you enabled below iis features:
please follow the below steps to publish your MVC project in iis.
1)open the visual studio. Select your site and right-click on that-> Click publish.
2)in pick up publish target Select folder option and create choose destination where you want to publish the site. (make a new folder and publish a site in that folder) and then select publish.
3)open IIS manager.
4)expand the server name and right-click on sites and select add a new site.
5)enter the site name, physical path, and site binding details.
ip address: select your machine ip address.
port: 80
domain name: your domain name
6)make sure you enabled directory browsing in iis.
7) The application pool is running under application pool identity, a version is correct and using the integrated pipeline.
8)anonymous authentication is enabled.
9)iis_iusrs and iusr have full permission to access the site folder.
host file enry:
bind your machine IP dress with a hostname of the site.
after doing all the changes refresh the site in iis and browse.
Much to my surprise, it is not a five minutes-task at all. Spent almost a day without achieving anything...
My existing website notgoodname.com is running well for months. And I want to change it to goodnewname.com (already bought it) . Ideally, I would like to do it the way that impact users least (least downtime, 0 data lost), SEO n others are second priority.
Initially, I was thinking about having goodnewname.com and notgoodname.com sharing same IP, same hosting ressource (php code, mysql db), then gradually retire notgoodname.com. However, Googling can't help, godaddy support neither, both gave me confusing guides.
Please lend me some guidance/good links.. (my background: ~10 year as software developer but just few months webmaster : cpanel/WHM/hosting/dns kinda stuff)
Firstly, I would like to congratulate you on goodnewname.com, what a find. :P
The easiest hassle free way to use the new domain is to add it as a parked domain under the cPanel account of the existing website, you would also need to change the nameserver to point at WHM's/YourHosts nameservers, or, and a root A record pointing the domain to your web server's IP.
If the website is quite straightforward (PHP, CSS, HTML, no databases etc..) you could instead of adding it as an addon, create another hosting account for the new name, copy all the files across from wwwroot (public_html) on the old account to wwwroot (public_html) on the new account and then delete the old account and add old bad name as an addon.
I have a website www.mysite.com. I created a mobile site for the same which is mobile.mysite.com.
Now the problem is I want to move the mobile and make it accessible via www.mysite.com/m/.
I am working in Codeigniter framework. If I have to do it so, then what things should I take care of? Any suggestions will be helpful.
For this you need to create a sub-domain of your site www.mysite.com and name it as "m". Shift all the folders and files of your mobile site into "m". Now www.mysite.com/m would be accessible.
*Note: Don't crate sub folder in your main site.it wont work.you have to make sub-domain.
I have an issue deploying my Orchard based web site on my web hosting.
I need to run 2 Orchard web sites on my web hosting. To do so, I have created 2 sub-directories that are set-up as both application & virtual directories of their own rights :
~/site1
~/site2
Finally I have set-up two domain names :
mysite1.com pointing to my host's vdir ~/site1
mysite2.com pointing to my host's vdir ~/site2
My page works when I go to mysite1.com main page, or mysite1.com/Admin (hard path ?!).
But they don't work when the page slurp points to Orchard dynamic pages/content.
It then gives me lots of :
HTTP 404. The resource cannot be found
Do you have any ideas what could be happening please ?
ps: I have also posted more details on the Orchard forum
They don't just need to be vdirs, they need to be full IIS applications, under a ASP.NET 4.0 integrated pipeline app pool, with full trust. (please don't cross post)
We've installed Windows Search Server Express on one of our servers, which apparently runs on top of sharepoint.
Sharepoint was installed on port 80, where our "normal" intranet runs. When I disable the intranet and run the sharepoint site, everything works as intended. The intranet is linked in many places it would be a pain to move it, so I'm trying to move sharepoint to another "place" (hoping this is less of a pain), either a different port or as a virtual directory under the main site.
First, when I make any of these changes, it fails to get access to the intranet root. Not sure what it is looking for there, but ok, I give "Network service" (the acocunt the "Sharepoint 80" application pool is running under) access to the intranet root. This gets me one step further, I am stumped:
When I move the Sharepoint website to another port, it complains that it can't find default.aspx (there is none, but also it doesn't need it when running on port 80)
When I move it to a sub folder of the existing site, and try to open the global.asax in the browser, ti tells me that this extension is prohibited, even though the "Application configuration" is - as far as I understand - identical to that of the Sharepoint site, and allows GET, HEAD, POST, DEBUG for .asax.
Any suggestions?
Sharepoint sites should be able to run on any port- if you go into Sharepoint Central Admin and create or delete web applications without a problem.
Is it your intention to run heterogenously with Sharepoint and your regular site both on Port 80? I know that you can create a web application on 80 and then not have a root site collection ( Sharepoint applications consist of a Web Application that runs on a certain port and any number of Site Collections within that, each of which has it's own directory path and can contain lists, libraries, other Site Collections and so on ) just creating one on a different path, but I don't know for sure how that would work alongside an existing web site on the same port- it may not play nice. Again, you can create and delete site collections from the Sharepoint Central Admin page, which is linked from your Administrative Tools list on your server.I would try this first, as if it works it's an easy solution.
Is Windows Search Server Express related to Sharepoint's own search facilities? If it is you may find that it expects to run using some of the Shared Service Provider facilities, which even Sharepoint doesn't expect to be running on the same port as the sites it's providing services for.
An even better way would be to create another alias (cname) in your DNS for your server, just set a different host header for each web site.
for example, in DNS your machine might be named 'intranet'. Create an alias for that machine named 'sharepoint'
In IIS, create a new website for sharepoint, and set the host header for that site to 'sharepoint.domain.com', where domain.com is your domain.
Do the same for the intranet website, but set the host header to 'intranet.domain.com'
That way, your users don't have to use another port in the URL.
Thank you! I found the option in the sharepoint administration website.
I add this response to detail the steps I have taken - maybe they are useful for someone else.
In the sharepoint administration website (running flawlessly on another port), I chose "create or extend web applications", then "extend existing web application".
There, from the the drop down "Web application", "change web application" opens a popup with the web applications available. Search server was installed as "Sharepoint 80", so I selected that.
Then I selected "Create new IIS website", with a new name and a new port. All the other options looked fine to me as default.
Clicking OK, this creates a new web site in IIS, which was configured correctly. it doesn't work via the IP address of the server (http://192.x.x.x:8080), only using the server name - but that's ok with me :)
I still had to make some adjustments with the access rights, but the full crawl is running and I can find a few documents already. Yay!
This is much easier when you first backup your site and then create a new site from the central admin with a new port number and then restore the backup to it(overwrite)