While debugging a timezone issue with Railo and Postgres, I opened up the Railo Server Administrator and happened to notice the "Web contexts" section at the bottom. I recognized all the entries except for one:
What is "http://azenv.net:80"? Is that something that comes with Railo, or is my server <GULP /> hacked?
Your server isn't hacked. What it looks like is that the domain http://azenv.net/ is pointing to your server. It could be or someone has a redirect pointing to your IP on their machine.
Now when your Railo server started up, usually the web contexts are blank (until it gets some domains) Railo doesn't know what the URL is at all. It got hit and went to the default context (webapps/ROOT) and it now thinks that is the default in your listing.
Maybe nothing to worry about, apart from why that domain is pointing to your server.
Related
I’m getting HTTP 404 when I access this url from one of the web servers, but works fine on the other. The deployed code is exactly the same on both servers because it’s deployed using CICD. The web.config is identical between both servers as well. I compared the IIS configs between the two servers, they are same. It should be something on the server that I’m not able to figure out. Vendor says it’s not an application issue because it works elsewhere and something on the server needs to be fixed.
https://serverIP/AppName/Resource.axd?r=DS.Web.UI.WebControls.Callout.js&h=20E547C24AB98AD419C9CC78656FC871
Stack: IIS, ASP.NET, Windows Server 2016
Note: Server IP and App Name is obscured in the url mentioned above.
We're moving an instance of a third party, .NET-based website to a Win2016 server, IIS 8, from an external hosting service. Under the site, there's a WCF web service in a subfolder. There are no virtual directories or apps.
mysite.../Order/v4/service.svc
When I browse to pull the wsdl (https://MySite.../Order/v4/Service.svc?wsdl ), it is redirecting to Login.aspx (https://MySite.../Order/v4/Login.aspx).
Browsing to https://MySite/Order/v4/Service.svc?wsdl redirects to https://MySite/Order/v4/Login.aspx .
IIS has no default document set / web.config's defaultDocument is commented out.
Vendor indicates
That would be a redirect that was setup either on IIS or another
appliance that is doing that.
Same behavior occurs running on the server itself (localhost) and sys eng confirms it shouldn't be leaving the network to hit any firewall.
There are no other .config files on the server with any reference to "Login.aspx".
This still feels like it is some piece of configuration but even doing things I shouldn't need to do like restarting the server just to make sure no caching of settings is hanging around isn't affecting it.
Any guesses on what might be attempting to redirect?
Following Rich-Lang's suggestion in comments provided the information to identify that the global.asax file was handling an error in the web.config. Since the code in this case was in codebehind in a dll, and the vendor indicated their code does not redirect, I had not seen that culprit before. Removing the global.asax and turning off customErrors allowed me to see the underlying issue.
So I was migrating a website from an older sql box to our new SS 2008 r2. I copied the files into the correct folder. turned off the service in IIS on the old box. created a new website on the new box in IIS. The binding's are correct. The site worked on the old box. It's running in the ASP 4.0 app pool. (I also tried letting it have it's own. no change.) The Domain users have rights to the box. So does the impersonated service account. which is also a memeber of IIS_users. I can ping the server. nsLookup shows the right IP address. But when I try to browse to it, whether through IE, or even by clicking the link on the far right of the window in IIS7, "Browse Web Site", which has the correct ip, name, port 80..., I get the error
Under Construction
The site you are trying to view does not currently have a default page. It may be in the process of being upgraded and configured.
Except that I do have a Default.aspx page in there, and it ran fine on the old server. I've got two other sites on this server, neither gave me any problems when I moved them. Other than the ip they're listening for, they're set up identically.
Any thoughts on what might be wrong, or what further steps I can take to trouble shoot?
Just making sure that you checked your IIS Default Document settings.
Open IIS Manager, expand the left menu and select your web app, open Default Document. Make sure that list contains the name of your default doc and that your default doc is in the root of your application.
So... Turns out we were missing an IP entry in our NIC on the virtual server... as soon as we entered it on the host, everything worked just fine. Anyone who wants details can contact me.
I have a web site opened in VS 2008 . I try to run it from VS2008 and the asp.net development server starts up.But the browser returns the following error
Firefox can't find the server at www.localhost.
The web address in browser is http://localhost:2921/WebSite2/Default2.aspx
There is no such thing as www.localhost, and nothing built-in to asp.net will redirect you automatically (unless you tell it to). Sounds like you have code that looks at the url and redirects to a www version if you're not there. You shouldn't do that, and instead use relative urls internally that work no matter which way a user hits a page.
Check following :
Are your proxy settings correct in your Firefox browser. Firefox->Tools->Options->Network->Settings.
Are you browsing the correct address, everytime you run/debug your website a dynamic port is assigned unless explicitly specified.
I have developed an app on a dev machine using ASP.Net MVC and all is fine and it works. I have moved it to the Prod Server and when I type http://mydomain.com I get the error:
The incoming request does not match any route
If I then make a request to http://mydomain.com/pagename I then get a IIS 7 404 page.
It is hosted in a Full Trust Mode and Integrated Pipeline according to Softsys hosting who its hosted with.
I am currently accessing the site via a temporary DNS name eg/http://mydomain.com.serv7.temphostspace.com and my host believes this might be it.
From the support ticket this is what they say *"I believe, this is caused since you are access your website through temporary URL http://mdomain.com.serv7.temphostspace.com/ and relevant setting might be missing in your configuration."
Any ideas?
Thanks
Your host is probably barking up the wrong tree, unless the site isn't configured. I'd try and request a static file you know is there to be certain. As for the problem at hand, how are you wiring up the routes? Could something in production be failing before this and prevent this from happening?
Anyhow, first place I would start is by using the ASP.NET Routing Debugger to see what routes your app thinks it has.
Similar problem: ASP.NET MVC running IIS7 deployment problem
Resolution from there: http://haacked.com/archive/2008/11/03/bin-deploy-aspnetmvc.aspx
Turns out it was trust issues not configured right