Hope you are all well. I a new to IIS and was wondering if you could help me with an issue I am stuck with
the site is accessible using IP address, and via the shortname http://sitename However, when I try to access the site with an FQDN its complaining a 403 permission denied error. I checked and the permissions are all in place as needed. I did read online that it could be to do with DNS so upon checking I can confirm DNS also resolves fine. it is set up as a server farm with 2 other servers and I have checked the IIS log and I noticed that the request is routed to other servers in the farm and I see that the user account used is as below
Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 403 0 0 3
I dont have Firefox installed on the machine. I'm a bit lost here if anyone could help me please.
Thank you in advance
re-created the site with no luck
re-added the permissions of IIS user with no luck
checked dns
checked folder permissions
Related
I have a windows server 2019 VM in Azure.
On this server I have multiple web sites running.
One web site has two URL's
For example https://api.oldcompanyname.com (192.1.1.5) and https://api.newcompanyname.com (192.1.1.6)
I have certificates for both, each has its own binding, and each has its own IP address.
Locally on the machine I can access both sites with no issue.
However remotely the old site URL pulls up just fine, but the new site URL gives me a 503 error.
I have checked the IIS logs and I don't see any of the 503 errors listed in there.
I checked the windows logs and there are no crashes with the AppPool and again running locally (with FQDN) works just fine so the site is loading.
Windows firewall is turned off.
In Azure we do have this server behind a Traffic Manager, PF Sense, and App Gateway.
I want to rule out any issues on this server before I go searching in one of these areas
Funny thing is that even from another machine inside the network I get the 503 on this one binding and I don't think that that connection would go through any of above items as it is an internal address it is using.
Any ideas?
I am new at SharePoint and have installed and configured everything, on the local machine (where SharePoint is installed), I connect with the PC name, and everything is working, I can access the front-end and the Central Administration. I have a dns record that points to the ip of the computer. So on another machine, I use the url (intranet.domain.com) to connect. Central Administration works (intranet.domain.com:12548) but when I try to access the front-end (Port 80 - intranet.domain.com) I get the following on my screen
I presume something on my IIS is not setup correctly.
Any advise how I can fix this?
Turns out, I need to create a new Web Application for the new Site Collection
My domain was previously hosted in another place (some years ago) and was connected to Azure. Some days ago I successfully changed the dns to a different hosting company but it seems I still get a webpage related to Azure when I try to access the website on my browsere. This is what is displayed:
Error 404 - Web app not found.
The web app you have attempted to reach is not available in this Microsoft Azure App Service region. This could be due to one of several reasons:
The web app owner has registered a custom domain to point to the Microsoft Azure App Service, but has not yet configured Azure to recognize it. Click here to read more.
The web app owner has moved the web app to a different region, but the DNS cache is still directing to the old IP Address that was used in the previous region. Click here to read more.
btw. I clicked the links and they are not helpful.
I have no idea how Azure works, but I have access to the login information. When I log in on portal.azure.com everything seems to be empty, there are no apps, only a canceled subscription and really nothing to see.
If I click "All resources", I get "No resources to display".
My first thought is that this is some kind of a cache problem, but I have cleared the cache in my browsers, tried different ISP and different computers in different continents, but I always get the same error message.
If I check whois.com and who.is I can see that the new dns is correct and the only thing that should be displaying is the temporary index.html page that is currently in the htdocs folder for the new host.
Do you know what I need to do to remove any connection to Azure and display my new website?
It's solved.
I just needed to edit my dns entries. For some reason, they were still pointing to an old IP.
I have a web application on my local computer on a domain that works on IIS 7.5. When accessing this web app through localhost it works fine, but if I try using my IP address instead, It asks for my credentials and when I don't enter them, I get Error 401.2.
I already have Annonymous access and windows authentication enabled.
Please help me.
I was able to make it work. Instead of using my IP address to access the web app, I used my computer name.
I configured the Default website in IIS for SSL by creating a CSR using the IIS itself, submitted it to a CA, and assigned the issued certificate as the server certificate. That's all is required in this world to setup server SSL. But when I open the https url it says "Internet Explorer cannot display the webpage". Which pillar should I bang my head against to get it working? The only help from microsoft I could find is that useless arcicle http://support.microsoft.com/?id=290391 that presupposes you are configuring a non-default website for SSL and goes on and on about port conflict. I'm using default website for https.
I'm using windows xp, IIS 5.1 and Microsoft Management Console 3.0.
Please help or courier me a shotgun for shooting myself.
Edit: After I configured IIS for SSL, the Apache Tomcat server which had been configured on port 8080 has suddenly stopped working. The 8080 urls just timeout. What is the connection?
Edit: Because I can't live without Tomcat on my machine, I used another machine to setup IIS SSL after stopping the tomcat there. I face the same problem there, "Internet Explorer cannot display the webpage". Please help before I shoot myself.
Don't shoot!
XP has given me fits with SSL... have you tried setting the application pool to high/isolated setting up the website with an identity under COM?
That seemed to solve some issues for me.
Also - did you make sure to set it up in the correct stores? Is this an application that is running under your account or a service account? If it is a service account you may need to do a RUN AS on the certificate management console and add under that user's personal store as well as under the appropriate store for the machine/computer.
Good luck.