We recently migrated a site to a new server. This site integrates with Barclaycard ePDQ, and was working fine on the old server.
Since migrating, however, ePDQ is unable to hit our Postback Url (which is an ashx handler). They are seeing a response http code = -1, which we're told means it's either exceeding the maximum timeout (20 seconds) or the url simply can't be accessed.
We checked the firewall on the new server, and it is allowing incoming traffic over ports 80 and 443.
I am also able to mimic the POST with the same request data to the Postback Url using Fiddler, and this works fine. So no timeouts, and it is accepting POST requests over port 80.
The site was migrated several days ago, and running a DNS propagation tool against the domain shows it universally resolving to it's new IP.
We're running Windows server 2012 on the new server. The old server was running Windows 2008 R2.
Does anybody have any ideas why ePDQ is unable to hit our postback url?
Thanks in advance
Related
I have a site that is used by a local company now for many years. In the last week, every time a user connects.... about 30 seconds after a data stream appears that fills their internet connection (Upload bandwidth since they are hosting the app internally) with 7Mbits of data.
The browser (Chrome or Edge) is not reporting any of this traffic. Just shows that the Web socket connection is established, and that it is listening. If I do something in the app to transfer data through the websocket, I see it in the debug window with the size at the bottom. The browser does not see all of this data coming to it....
With WireShark I can capture the data but it looks to just be all binary and can't make heads or tails of it....
It is hosted on Windows 2019
IIS
the site is .Net 4.8
The issue started without any site updates on my part....
Has anyone heard of something similar to this? Was their a Windows patch recently involving websockets? What can I include for anyone to help...?
A client has a Sharepoint 2013 farm consists of 2 servers acting as frontend and app and 2 SQL server (SQL14) all with windows server 2012.
My application is a windows application that calls sharepoint with CSOM requests.
All the environment was late by 10 min from the real time and for years everything was working, suddenly after fixing the time on the Domian sever so that it is fixed on all the severs and client machines, all the CSOM requests to sharepoint severs throws exception request aborted request timeout. Nothing is logged on the server and I couldn't find any reason.
Suddenly and by chance when I changed the IP on one of the PCs that holds my windows application to a one that was not in use, things started working again and I continued the same on all PCs.
But the client wants a clear justification on what was the problem.
Does anybody know how time is related to sharepoint and client.svc and is there any way the time keep cached on any level of the network
Actually it was not a problem of sharepoint.
The client was using a new NSX system and for unkown reason it was causing packets loss. Basically net tcp requests packages.
I'm encountering the following problem in production with an ASP.Net Core website that runs InProc on IIS. The installed .Net Core runtime is 2.2.8.
Following a push notification on Signalr, my clients are sending about a hundred requests to a particular URL, which is bound to a controller method that looks like this:
[HttpPost()]
[Route("Api/GetData")]
public string[] GetData()
After serving a few requests, the server suddenly stops responding for a few minutes, before serving all the responses at once. No errors can be seen in the app logs, and the IIS logs shows huge response times for the requests.
I have enabled Failed Request Tracing in IIS to analyse requests that take longer than 9 seconds and I see that the requests that take forever to respond are actual promptly processed by IIS.
E.g:
IIS log: 47952ms
2020-05-12 12:18:15 169.XXX.XXX.XXX POST /Api/GetData - 443 -
195.XXX.XXX.XXX Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko
200 0 0 79479 945 47952
IIS Failed Request Tracing logs:
I haven't used IIS Failed Request Tracing before and I'm not sure how I should interpret this. I first though of a lock in the code, but I haven't found it and I'm not sure how it would also affect requests to other URLs? What's your thoughts?
A maybe important note is that the clients are behind a proxy, so the server sees the same IP for them all. We have never encountered this issue before on another server.
UPDATE: We managed to reproduce the problem with a version of GetData() that simply returns a static array of string. We found that the size of the array mattered. We reproduced the issue with a response of 88KB, but not with a small one (2.5K). Looking at the .net core logs, it seems that the result of the method is computed promptly, but the response itself is hanging (we haven't figured out why). Upgrading to .Net Core 3.1 solved the problem...
I'm keeping the question open in case somebody can provide an explanation.
I have ASP.NET MVC website that runs on my local sever and I need to check mobile area.
So I decided to connect to it via Android Emulator (AVD)
As I read IIS server reject incoming requests from remote devices.
So from this thread I think I found solution
Post
I make all described on his github and get this
So as I understood it can receive external requests now.
And I tried to make request from AVD (192.168.2.106:3000)
And I get this
So as I understood it got path, but IIS still not receive external request.
Maybe someone faced this problem and can help me solve it?
I've got an issue where my IIS 7 C# server is configured but only reciving requests only when i use http://localhost:6547/ and not when i change the localhost to my own ip.
My question is : how do i make the server actually 'listen' to my port and recevie and return requests.
facts that might help:
im using Windows 7
i gave iUsr and IIS_USER permissions to server's directory
added listening to 6547 port, in both TCP and UDP
tried disabling the firewall totally, still haven't worked this way.
when i try using requests, im using the Advanced Rest Client of chrome, either when i try with my ip or with localhost as mentioned before.
I think its something else related to premissions of remote access. my IIS 7 doesnt have permission manager for some reason even though i really added all the IIS related features available in the windows control panel.
If any data is missing i would gladly provide it.
You need to confirm that your IIS is bound to all ip's (the * in picture below).
Open IIS Adminstration->click on iis->click on bindings and update appropriately:
Other leads: https://serverfault.com/questions/148439/how-can-i-control-which-ip-address-iis7-uses