I've set up a wordpress network with the sub-domain feature in an IIS server. While the process is difficult because IIS doesn't support wildcards very easily, I have gotten wildcard subdomains to work in the past.
When I create a site in the network and try to access it, I just get an error saying the site can not be found. Not a 404 from IIS, but like the DNS record could not be found.
I have DNS set up on the server with the wildcard A name record, in the same instance as two other sites where the wildcard redirect works. I even tried giving it a Cname record, but it's still not finding it.
Issue was with DNS setting from the name server. Counterpart stated they had made change when they had not.
Related
I'm using Web Platform Installer and WebMatrix to set up a WordPress site running locally (Windows 7 Professional). It's the first time I've ever used WordPress and the first time I've ever used WebMatrix, so it's possible I'm missing something really basic.
Several times, I've had a problem where I hit 'Run' in WebMatrix. It opens the browser pointing to the correct URL - http://localhost:10268/ - thinks for a second or two, and then redirects to a different port - in this case, http://localhost:52925/ - which returns 'This web page is not available'
I have absolutely no idea where that second port is coming from, or why it's redirecting. I've searched the IIS Express config files (C:\Users\dylan.beattie\Documents\IISExpress) and the source code of my WordPress project, but can't find that port number 52925 anywhere.
Is this a built-in PHP / WordPress thing? Some sort of security feature, maybe? I'm completely stumped. One slightly odd detail - that may well be unrelated - is that I think this only happens after I start using revision control. The site will work fine when it's first created, but then when I open it from GitHub, things start going weird. Any ideas?
Solved it. It looks like there's a setting in WordPress that needs to match the IIS Express configuration - and when you check out a site via revision control or set up a new site from an existing folder in WebMatrix, it doesn't use the same IIS Express settings. In my case, I'd downloaded the code and restored the database from work I'd done earlier on a different machine, and so ended up with IIS listening on port 10268, but the WordPress site configured to listen on port 52925.
The IIS settings are in C:\Users\user.name\Documents\IISExpress\config\applicationhost.config, and the WordPress options are records in the wp_options table where option_name == 'siteurl' or 'home'
Two ways to fix it that I've found:
In WebMatrix, Site, Settings, change the site URL to wherever you're being redirected to.
Edit the wp_options table and change the settings to match the URL in WebMatrix/IISExpress.
I have two sites configured on my IIS 7 server. One is the default web site and the other we will call www.othersite.com. The default web site runs a few different Applications running ASP.NET and the other site is a ColdFusion 8 web site.
The default site is configured to pull from the default web location at C:\inetpub\wwwroot while the other is set to pull from C:\sites\othersite.
The bindings are set to send all unassigned traffic to the Default Web Site, but www.othersite.com is set to a specific IP address. This is the same as I have it on other servers, which work perfectly well, but for some reason when I load www.othersite.com it is looking for its files in C:\inetpub\wwwroot instead of C:\sites\othersite even though the physical path is clearly defined in the basic settings.
Anyone have any idea why this might be and how I can get it to point to the proper directory?
Under IIS >> Bindings, you can see a place to put in "Host name". Leaving blank will result in all traffic to IP or host, but by specifying a host name (www.othersite.com) will direct traffic to that dir/site.
I am new to the web world, so I apologize if this question is silly.
I have an ASP.NET web site I wish to deploy.
The server has IIS 7 deployed on it, and I've added the site
to that IIS server as a web site.
For the time being I don't have a domain mapped to the site,
I would like the users to browse for the site directly by using the server's IP.
Is that even possible? because I failed to do it.
The only option that worked so far is using the hosts file to declare
a fake domain.
It would be nice if someone could clarify that issue for me.
Thanks a lot,
Omer
If you set the site bindings to IP address: All Unassigned on port 80, and do not provide a host name, then any request that makes it through to IIS should be served by that site. Make sure you stop any other sites that might have that binding (e.g., "Default Web Site" is normally bound to this).
In order to access the site by IP, you can't have the host name populated in IIS. Your best bet would be to use the "Default Web Site" that's already in IIS, and point that to your application.
Using IP is possible, but you need to make sure your users can see this ip from their machines.
I yesterday received a zip file containing an old asp site from 2005. Its came in a folder called ivx.
I've unzipped ivx to c:\inetpub\wwwroot and then created an application in IIS called ivxapp and pointed it to c:\inetpub\wwwroot\ivx. Now when I type http://localhost/ivxapp, I am able to access the index page.
My problem is, whoever designed that site, designed it when IIS5 or IIS6 was around. He's used paths like more... which leads to http://localhost/new_posts.asp and not http://localhost/imagevertex/new_posts.asp
The whole site is some 21000 lines of code and contains many many references like this. Then comes the problem with <!--#include virtual = "/common/adminverify.asp" -->
Instead of having to manually edit the entire code, do you know a way to get things going?
This site worked perfectly well on a production server. Right now it's on my local machine on Windows 7 64 home premium.
Yes, you need to give this site a root-URL of its own, and not run it in a subdirectory of your localhost.
This is more of a web-administration question, but what you need to do is either run it under "localhost" directly, or add a domain-name to your network to run this site under.
The easiest for you right now is probably the first option.
If you aren't running a different site under localhost already:
Go to the IIS manager and click the 'localhost' site. On the right side of the IIS interface you can change the basic settings. Point the physical path to the ivx directory. You can reach the site directly on http://localhost.
If you are already running a site under localhost you need to keep:
Now, if you -are- already running a site on your localhost, the second easiest option is to run the ivx site under localhost, but on a different port. To accomplish that, click on the current ivx site in IIS, change the path in the same way as descibed above, and after that click on "bindings" in IIS, and change the PORT for the ivx site to something other than 80, for example 81.
The ivx site will then run on http://localhost:81, your current localhost will still run on http://localhost.
The hard way: adding a host to your network or PC:
The last option is to add a new hostname for the site to your network. You can add an A-record in your DNS for the ip-address of your server or add a host name to your HOSTS file in Windows on your server ("server" in the sense of the machine that runs the site, which can also be your local machine)
You can add a made-up name to the ip-address of the server, and in IIS' bindings add that name under "host name". this way you can run two different sites on the same machine, the "host name" seeting in IIS will make sure that calls to that specific hostname will reach the correct site. Adding it to the DNS of your network, or the HOST file in Windows will make sure the name is resolved to the correct machine (your webserver).
This last option is a little tricky of you've never done something like this before, but the first option works just as well.
Good luck!
Erik
I have a domain www.foo.com purchase with NameCheap.
I pointed that domain name to my VPS's static IP address and created a web application in IIS7 and it's working correctly.
Now I created another separate web application and set it's binding to forums.foo.com.
However the browsers doesn't enter the site and it seems the binding isn't doing quite what I expect it to do.
In Firefox, I get:
Server not found
Firefox can't find the server at forums.foo.com.
Is there some sort of special configuration I have to do in order for the subdomain to correctly point to my folder in inetpub?
Don't you have to configure the subdomain with namecheap first?
Who is serving dns for the subdomain?