I'm experiencing a strange behavior when running automated tests with Katalon studio.
The problem occurs across all browsers.
When running a test all calls going to the first url/domain (e.g. google.com) are fine. All calls going to any other domain fail.
The error in console is:
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
If I open a new tab and try to load any other page I get the same error.
Calling any endpoint on the same domain works fine.
The issue occurs on a specific machine. All works well on 2 other machines.
Related
I have an API in a .NET project that I'm running with Visual Studio Mac (8.4.3). I run it in release mode, and it opens a browser window with localhost:5000. The browser window says "ok". However, when I try to hit endpoints in that API, it fails very quickly. When I ran this API (ie. same code) from another server and accessed it via proxy, it ran fine. For example, when I ran it on a server whose IP was 162.250.198.98 and proxied into it, I would hit an endpoint like 162.250.198.98:3000/api/user and it would work, but now when I try to run localhost:5000/api/user, either from my app or from Postman, it fails almost instantaneously. When running it in Postman, I tried what it suggested by turning off 'SSL certificate verification' in Settings, but no change.
Can anyone advise me on how to approach troubleshooting this?
Wait, so You are saying that while trying to call API on 162.250.198.98:3000/api/user You are fine but while trying to do the same thing on localhost:5000/api/user You are getting an error? Would it might be possible You have Your API configured to receive calls at 3000? :)?
No, but really - please chech it out, maybe it is that simple, I'm couting on it :).
You can change/check it in Visual Studio: main project > Properties > Debug > App URL.
I have an app that we are slowly trying to migrate to Azure's Resource Manager model. Last Friday I published the main web app to an App Service. And when I tested it in a browser after publishing, it loaded just fine, I could log in, etc.
Then, over the weekend, it occurred to me that I had published from the wrong branch. So this morning, I came in, changed branches in VS, and re-published. This time, when I tested the app in a browser, it immediate threw an error.
[InvalidOperationException: An error occurred when trying to create a controller of type 'Response.Controllers.LogOnController'. Make sure that the controller has a parameterless public constructor.]
I've seen this error before. It's a Dependency Injection error. The app uses Unity for D.I. The thing is, I can fire up this branch on my local dev box straight out of VS with no problem.
To trouble shoot, I deleted the entire web app in Azure, and re-created it. Then, I reverted VS back to the original branch that I published on Friday, and re-published from that same branch.
I get the same error. In other words, what worked on Friday now throws this DI error on Monday. Nothing has changed. I've looked in the Global.asax file, and the dependency that the error mentions is registered. I have no idea what's going on, but I think the actual error might be a red herring.
And again, everything works just fine when running on my local dev box doing a debug from VS. And the same app runs fine with published to our (soon-to-be-old) server on RackSpace.
You can see the error here:
http://response-web-toyota-staging.azurewebsites.net/LogOn
Well, for what it's worth, I solved this by ftp'ing into the App Service, and manually clearing out all files inside of the 'site' directory. Then I (again) deleted the App Service, re-published, and voila. Now it works again.
I would have thought that deleting the App Service would have done the same thing, but I guess not.
Weird.
On localhost, the app works just fine.
On EC2, the app runs behind nginx. It loads into the browser, but nothing shows up. The browser console displays an Error
TypeError: 'undefined' is not an object (evaluating 'Package["service-configuration"].ServiceConfiguration')
I have no idea how to tackle this problem. Any help appreciated.
EDIT
NGINX is not the problem. The same behavior if I access meteor server directly.
Running "meteor add service-configuration" does fix the above mentioned error, but the absence of the error does not fix the observed behavior, that the app does not render on EC2 whereas it does render when started on localhost. (The error message was the only visible difference between EC2 and localhost. So I suspected that would be the cause. Now that hypothesis must be wrong.) So the problem still persists.
Problem Solved. The Lesson:
Meteor has a debug mode and a production mode. The two may behave differently. On localhost, meteor runs in debug mode per default. On deploy to meteor.com or per mup, the default is production mode. To run meteor in production mode on localhost, run meteor --production.
It looks like you're trying to access the service-configuration configs on your browser.
These are not available client side. This also affects your localhost app but it doesn't break your app (doesn't give you a blank page) because meteor is in debug mode.
In debug mode Meteor files are not concatenated so an error like this would go unnoticed, even if it is thrown on your js console. In production mode the error would halt the rest of your script (since everything is concatenated into a single file)
You need to ensure the code that is doing this only runs on the server side. In general it's not a good idea to have access to the service configuration data on the client side.
Looks like Arunoda and crew are adding a buildOptions.debug setting to the next version of MUP, which should allow you to deploy via MUP and have it act like it's running on localhost. See Arunoda's answer to a related question and (at least for now) documentation for the development version of MUP.
I developed a little .ashx handler that returns an image so I could do
<img src="myhandler.ashx?query=string">
It worked perfectly on my dev machine. I moved it to the production server (IIS on Server 2008) and it broke. By "broke", I mean it no longer returns a valid image. The handler calls an external application to generate the image - I had the path wrong, fixed it, and all that accomplished was to make the warnings stop showing up in the event log.
I know it has permission to run the program. I manually ran the command I'm passing it and successfully generated an image. There are no errors in the event log and the IIS log says it responds with a 200/OK. I'm a little lost as to how I should go about debugging this further.
So, got it solved.
The discrepancies between my dev environment and the production server led to the need to double-escape a special character that .NET is fine with but my external program interprets specially. The entire problem was unrelated to the handler.
Thanks for the help, though.
I have an application that runs perfectly fine locally using the VS 2010 application server, however, when I deploy to our web app machine startup just spins and spins and never loads. We have other apps on this same machine that load just fine (this is a debug deployment of same app in product).
I have been spinning my wheels on this for days and I am at a loss as the problem could be.
Here is what I did
Create a new directory (same level as other apps)
Copied over our existing test (www.domain/test/) and it works fine
Build and publish new debug app (www.domain/test/) and it just spins trying to load first form.
I know the diretory is "working" as the 'test' application I put there works fine.
If it's killing the App pool, you might get something in the event log. Fiddler (www.fiddlertool.com) is great http debug tool which let you see if you're in a redirect loop. Also Firefox shows a more meaningful error, something about exceeding the max redirect count.
It does sound like something is looping, but not quick enough to cause a stack overflow, which is odd, because you'd expect it to fail every time.
Simon
Do you have the ability to remote desktop into the machine? If so try running process explorer and look at the process details for the worker process that is giving you issues. Definitely look at the TCP connections being created. If your processor is pegged at 100%, and memory usage is rising then you probably have an endless loop running.
It sounds like it's more related to IIS than ASP.NET. What about the identity that the website is running under? Is it possible that the user the site's running under a bad user, or maybe the password needs to be re-entered?
I did a quick Bing search
There are a lot of postings regarding the error message you described above. Most if not all point to code in your app that is crashing. I know I had a similar problem when I used an automated/threaded daemon utility in my web application. Make sure your code is not bringing down the server, sometimes the VS2010 web server is a little more foregiving than an actual IIS deployment.
If that doesn't work try running a Remote Debugging Session to try and catch any errors being thrown but not handled.
Lastly you could try to setup a new local IIS server to see if you have the same problems. Scott Gu has a nice article about using IIS Express to do this.