I have noticed that my app is receiving requests to https://gearssdk.opswat.com/ even though I never registered this url
I'm building asp.net core web app with asp.net.core 3.1 framework
screenshot
edit:
this happens both on my PC during debugging and on staging instances
this url is not resolving when app is not running.
It looks to me like your app might be intercepting traffic intended for some security tool that's installed on your machine.
If you run nslookup gearssdk.opswat.com from your machine, you should get a response of 127.0.0.1, which is the local loopback address. You could try listening on a different port
Related
If I create two ASP Core web services in VsCode and implement a SignalR hub in one which is connected to by the other (Dotnet 5, SignalR client library 5.11). This works fine. I can push these services up to Azure and it still works fine.
If however I open these webservices locally in a VsCode dev container and configure them to connect using the default Docker bridge network and the default forwarded port, I get a Connection Refused exception on the HubConnection.StartAsync call.
Why is this and how do I fix it?
I've tried a few things, using the http and https ports, disabling SSL verification in the client service but nothing works so far. I think I need some information on why this isn't working in the first place before I have much chance of coming up with a solution.
The problem was that that Kestrel was still listening on the default network interface inside the Docker container and I needed to reconfigure it to listen on all interfaces for the connection to work.
So in launchsettings.json I needed to change applicationUrl from "https://localhost:5003;http://localhost:5002" to "https://0.0.0.0:5003;http://0.0.0.0:5002" and then everything worked pefectly.
I would like to ask if it is save to publish .net core web project to production IIS server directly through WebDeploy or Folder publish profile.
What about already running http requests ? Would it be better to stop the IIS website first, update codes and start website again ? But I don't know if stopping the IIS website will wait for running http requests or stops them by force. Does the publish profile handle this by default (for example it happens often with folder publish profile that files are being in use by IIS process and the publish operation fails) ?
What is your publishing process, do you stop the website instance ?
The configuration file will be saved when directly publishing the .net core project to IIS.
When publishing a .net core application, the web is not running in iis, but as a separate out-of-process console application, using Kestrel components. AspNetCoreModule is hooked to the IIS pipeline early in the request cycle, redirects all traffic to the following Core application, and all requests are forwarded to the Core process.
Requests come in from the Web and int the kernel mode http.sys driver which routes into IIS on the primary port (80) or SSL port (443). The request is then forwarded to your ASP.NET Core application on the HTTP port configured for your application which is not port 80/443. In essence, IIS acts a reverse proxy simply forwarding requests to your ASP.NET Core Web running the Kestrel Web server on a different port.
So I suggest you stop the website while publishing and restart it then. Files in the deployment folder are locked when the app is running. Locked files can't be overwritten during deployment. I recommend that you take the original application offline when you publish a new web, which is also recommended by Microsoft. More details can refer to following documents。
Taking an Application Offline before Publishing.
Locked deployment files
I'm developing a Web App with Dache, Thanks the author for the fantastic library.
Unfortunately, I have a big problem with it.
In previous version of 1.5.6, it was worse. but in 1.5.6 it's better but still I get The following exception:
There are no reachable cache hosts available. Verify your client settings and ensure that all cache hosts can be successfully communicated with from this client.
In developing, I get the exception after 2 or 3 times build, and I have to restart cache service and stop IIS Express to remove the exception.
In the web app after some hours the clients disconnect from cache service. and I have to restart the cache service and web sites to remove the exception.
I hosted dache on windows service.
I think the problem is for comunications between dache host and dache clients.
So, Is it possible to host dache cache on IIS like a WCF service instead of windows service?
You can host Dache in your own process using the Nuget package. More information available on the Dache wiki:
I am using ver 0.5.3 of SignalR assembly in my silverlight application. I use connection.Start().wait() to start the connection:
Some of my observations are, which are really strange:
I run the application (In-Browser) mode via Visual Studio and I am able to establish the connection with the SignalR hub
If I deploy the app in IIS and then try accessing the application using the IP address of the machine, the call to connection.start().wait() never returns. I checked the Fiddler and figured out that the call never goes to the SignalR hub
If I use the application in OOB mode (Out of Browser mode), application works without any issue.
My requirement is that it should work in in-Browser mode.
Can somebody throw some light, what could be the issue?
Thanks,
Alpee
It appears to me that you are running into Silverlight's cross-domain request restrictions when run in-browser. You can either host the silverlight application on the same domain that is running SignalR, or you could add a clientaccesspolicy.xml or crossdomain.xml file to the root of the domain running SignalR as suggested in the above link.
I have a Windows 2003 server, with IIS6 + .Net 4 installed.
I created a site running on port 8002. It could be accessed locally but not remotely. I have done following tests
I used server's local broswer to access http://192.168.1.107:8002/WebForm2.aspx and I can get page successfully.
I opened a broswer on remote machine to access http://192.168.1.107:8002/WebForm2.aspx, browser waited for long time and eventually displayed timeout, web page not available message.
I tried telnet 192.168.1.107 8002 from client machine, and the connection could be established. I believe I have Windows 2003 server firewall turned off, otherwise the port should be blocked.
I ran ping 192.168.1.107 from client machine and got response.
While remote browser is waiting for response, I shut down the site (not IIS) and brwoser got not available right away. It looks like broswer connected to the site, but just something is hanging there.
What could cause such problem?
what are your dns settings? is the ip bound to this domain / host header?
recheck your settings in iis and check your firewall.
It sounds like you were able to reach the server, but I can only guess that based on what you're saying you tried already.
i would also make sure that nothing else is using that ip.
OK, strange thing. I created the site in VS2012 and forgot to change target framework back to 4.0, so it was compiled as 4.5. But server has no 4.5 installed.
Once I changed the target framework everything works.
I just don't understand one thing, hwy it worked locally in 4.5.