Binding site address to port 80 in IIS breaks MAC Authentication - iis

We have a website hosted in IIS which works when no bindings are present.
However, when we bind our domain name to port 80 we start getting this error:
Validation of viewstate MAC failed. If this application is hosted by
a Web Farm or cluster, ensure that <machineKey> configuration
specifies the same validationKey and validation algorithm.
AutoGenerate cannot be used in a cluster.
We have set a specfic machineKey so I'm confused as to why this is happening.
Any ideas?

Related

Site not loading on WFE2 in SharePoint 2019

I have setup a SharePoint 2019 high-availability farm with 2 WFE's, 2 APP and 2 SQL Servers. All servers state is good and patched the farm with May 2022 Cumulative Update. We are running F5 load balancer and public IP of the load balancer (LB) is also added in the host file of both WFE servers.
We created a web application (its public facing site, so also added anonymous authentication) and added DNS to it. We have setup the AAM in central Admin and also added IIS binding for web application port and 443 (wildcard certificate is installed on both WFE servers).
When Load Balancer is pointed to WFE1, the application is loading perfectly fine, however when LB is pointed to WFE2, its showing a blank white page (with no JS or CSS loaded on the page, no errors). However, when we do IISRESET on WFE2, first time site loads on WFE2 and then goes blank if we refresh the browser or click on any link on the website. The application is working fine with server name on both the servers
We have tested on different browsers. Also added Disableloopbackcheck in Registry. All required firewall rules (ports) are open. Each server is getting pinged from one another, so there is no server communication issue. Even the required SharePoint files/folders are excluded from antivirus (Bitdefender). Also, there is no other web application on this farm which is using SSL/https.
I have also checked SharePoint ULS logs, Event Viewer logs and IIS logs, but it seems there are no errors.
Any help would be highly appreciated!

Domain creation on windows machine via IIS

I wanted to create and map a domain(ex: site1.domain1.com) locally to the server running on localhost with some port, I've been trying to do via IIS, but raising port conflict issue, unable to create and start site domain while web server is up since the port is already occupied and vice versa.
Could you please provide how to resolve this or any other simple way to create and map the domain with the server running on localhost.

How to deploy multiple Spring boot application with embedded tomcat on a single server

I have developed 2 applications in spring boot with embedded tomcat. I have one cloud server (Azure) and i have run both the applications in that server. First app running in port 80 and other one in 81. I have domain name registration in GoDaddy For example First app is www.abc.com and the second one is www.xyz.com. How do i configure in azure console that when request comes from www.abc.com then port 80 should serve the request else request would be served by 81. Please help me out configuring deployment.
You should be able to accomplish this by implementing User Defined Routes
https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview
Additionally, Azure offers Load Balancers and Traffic Mangers that you could implement as well to manage the traffic.
https://azure.microsoft.com/en-us/services/load-balancer/
https://azure.microsoft.com/en-us/services/traffic-manager/

Issue in accesing a website hosting on weblogic server through IIS

We are facing issue while configuring IIS setup for weblogic servers.
Following are the environment details:
IIS8.5 on windows 2012 R2 standard 64x, wls_plugin_12.2.1.2.0 for weblogic server.
We have done the following steps:
Created a new web site on IIS.
Enabling the authentication settings.
Enabling the Directory browsing.
Added the script mapping in Handler mapping and set the path of iisproxy.dll as executor.
ISAPI filter setting for the iisproxy.dll
We are able to view the directory structure while accessing the IP and Port, but the request is not redirecting to the weblogic ip and port what we have configured in iisproxy.ini.
Is there any web.config or handler settings required to process the request?
The issue is that we are using wls-Plugin12.2.1.2.0 whose iisproxy.dll is not working in IIS8.5 on windows 2012 R2 server. After using the lower version of the plugin, able to access the web logic instance through proxy the IIS.
After that we are able to view the login page of web logic instance but not able to login to the application as it through s "404 Not found error". For this we have to change the handler mapping settings --> Request restrictions --> Mapping --> uncheck the invoke handle, restart the iis application and try browsing again. You will be able to login to web logic applications.

Azure trying to use 127.0.0.1 when accessing clientaccesspolicy.xml and crossdomain.xml files

I have a typical Silverlight 5 application created on Azure with a web project that hosts the site hosting the Silverlight XAP file and another web project that hosts a collection of WCF Data Services.
Together the two sites run in a single Azure role but on different ports. Port 80 hosts the WCF Data Services and Port 8081 hosts the actual Silverlight application.
I am having a cross-domain issue with this configuration. In watching through Fiddler, it appears that when my Silverlight application calls the Service, it is, as expected, looking for the clientaccesspolicy.xml and crossdomain.xml files from the WCF Data Services site to be allowed cross-domain access. However, the Silverlight application is sending the request to http://127.0.0.1 and not the correct URI for the domain in which the WCF Data Services are hosted.
Can anybody explain to me why the application is trying to go to 127.0.0.1 and not the correct URI?
Thanks
Your Silverlight application has a file named "ServiceReferences.ClientConfig". That file has been created when you added the service reference. And because you added the service reference from 127.0.0.1, your file is configured that the service endpoint is on 127.0.0.1.
What you have to do, is to manually change the ServiceReferences.ClientConfig file, before you deploy, to fix the service endpoint address (and set it to the domain you are using).
Or you can use mine approach to handle this kind issues.

Resources