my asp application(deployed in local server) is not running if proxy is enabled in a browser, if remove proxy application is working fine, can any one tell me the solultions please...?
Most browsers have an option for bypassing proxy server for local addresses, so you need to make sure that is checked. In internet explorer, for example, you can get to this by going to Tools/Internet Options and selecting the connections tab. Then click the Lan Settings button, and there is a checkbox for "Bypass proxy server for local addresses".
By "local server", I assume you mean your own machine. If that's not the case, then the other thing you can do is click the Advanced button (on the same screen as above) and you can add an exception to the "Do not use proxy server for addresses beginning with" section. You can use wildcards here, like *mylocalserver*, for example.
By the sounds of it you just need to tell your browser to not use the proxy for local addresses, e.g. localhost.
Related
We've been trying to implement SignalR for a browser MMO, and so far it works great. We managed to separate client from server, and even have them on separate computers. The thing is, this works when both computers are on the same network. We just change the IP to which it the client points to, and it works like a charm.
Now, the issue arises when the host is on another network. Namely, our server is an Amazon Web Service virtual machine, but we've even tied hosting ourselves on other IPs. We can't seem to find a way to point to the local address within the public address. By pointing to a global IP, we're only pointing to a router, but we want to be able to access a computer within that address.
How do we get around to doing this? Can we specify global address AND local address? Do we need to configure a forwarding rule?
In the very specific case of AWS, there's a somewhat obscure option for inbound rules. Once logged on the AWS homepage, you'll be taken to the management console. Then, choose "EC2 - Virtual Servers in the Cloud", and click on "Security Groups". If you don't have any security groups created, you'll need to create one - there's a detailed tutorial for that on that same screen. Choose a group, and then click on the Actions icon (right next to the "Create Security Group" button), and from the drop-down menu, select "edit inbound rules". You then have click "Add Rule", choose a "Custom TCP rule", select the port on which the rule to be created, and any source IPs that apply to this rule (usually "anywhere" is the desired option). Finally, hit the save button, and this rule should be in effect immediately.
Hope this helps someone!
I installed an ASP.net application on a windows Azure VM (IIS 7). SSL certificate is installed, configured and the application works correctly. I have removed Http binding and http endpoints.
The issue I am having is that if I use the cloudapp.net link (using https), the application still opens with a mismatched certificate.
What can I do to deny any user from opening my application using https://xx.cloudapp.net/x?
It seems really silly that people are saying this isn't the right place for this question, since some of the solutions could be code related. ie: In your application, check the host and if it's cloudapp.net, do a URL redirect.
There's a few different options here but it sounds like what you're looking for is just the ability to prevent someone from viewing the application using that URL.
What I would do is set up a site in IIS that uses Host Header resolution to look for xx.cloudapp.net. If that URL is recognized, do a redirect using the HTTP redirect settings to the https version of your app. Don't bind the SSL port to this site or you'll run into SSL errors like you showed above.
The other option is to leave it out entirely and simply use the Host Header resolution to filter out requests for your site. I suspect what you've done is assign all incoming requests to the only IP address on the system, which is why the xx.cloudapp.net is showing your app and the cert is failing.
This would cause xx.cloudapp.net to fail to show any site at all but I think that might be what you want to do anyway.
I'm running a ASP.NET on my pc and I would like to access to that app from another pc on the same network. I've tried to reach the app writing the URI of my pc on the network followed by the port number as below:
"192.168.X.X:49223/"
But it shows me an 400 error saying that it's an invalid hostname...
Is there something to do with my windows firewall or in IIS to allow access from another PC ?
Thanks for your help.
You may need to an exception in Windows Firewall.
Control Panel > Windows Firewall > Advanced Settings > Inbound/Outbound rules.
Add a new rule to both, specifying your port number and a generic name to identify its purpose.
Install IIS server on your machine, then deploy your application on that IIS server.
Refer this for Deployment assistance
To run the application on IIS instead of ASP.Net dev server you need to
Right click on solution in VS
Click on Start Options..
In Server section, Select "Use Custom Server" and then provide the URL of the application you have added earlier on IIS
Then you can easily access your website from any other machine on the same network.
Is it hosted in iis, or are you running it through Visual Studio. The funny port number (49223) tells me it's the latter.
When you run a VS project, the dev server is designd to only allow local conconnections. If you connect from a network it gets blocked by design. Their is no config around it.
What I do as a hack is run a reverse proxy like Nginx. It's a free download. Run it on your dev machine. You can tell it to listen on a port (eg 88) and then redirect tge traffic to port 49223. Give your mate the same url as before but replace the port with 88
Nb make sure your port 88 is open as per codemans answer
An example of the nginx config would be https://gist.github.com/ekinertac/5524389
This then tricks VS into thinking it came from your local machine.
A local website is set up on a server.
The website test.skien.kommune.no is mapped to 127.0.0.1
The site is configured in IIS and I have added a binding.
Everything worked for a week, but today I suddenly got this error message:
The following error was encountered while trying to retrieve the URL: http://test.skien.kommune.no/
Unable to determine IP address from host name "test.skien.kommune.no"
The DNS server returned:
Name Error: The domain name does not exist.
This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct.
Your cache administrator is webmaster.
The hosts-file is configured '127.0.0.1 test.skien.kommune.no'
Why doesn't it use the local dns-mapping in the host-file?
I found that the proxy settings were my problem.
In Windows "Control Panel" open "Internet Options" and go to the "Connections" tab. Click the "LAN settings" button.
If "Use a proxy server" is ticked, this may be your problem too. If there are periods in the local host domain, the proxy kicks in and treats the URL as a fully qualified domain name (which it won't be able to find).
To exclude it, click on "Advanced" and add it to the "Do not use proxy..." list.
Check for any VPN. if you have enabled any VPN in chrome then disable it.
Quoting #leo est omnia's answer, it might be possible that your browser would be treating your virtual host as a fully qualified domain when proxy server is ticked.
Adding to the answer,you also have these settings for the browser you are using, like for "Chrome":
settings => advanced settings => network => change proxy settings => connections => lan settings => uncheck use proxy server.
Also, if you have done some changes in your "httpd.conf" file, if you have given "\" backslash for directory path for the default path for your local apache files, use "/" forward slash instead, apache reads it the linux type.
This is the whole story
You should not use a proxy
Your proxy may have occurred through a browser extension, or you may have saved something in the system settings
I have an IIS7 site that works fine while on the server, however refuses to work from anywhere on the network.
When logged onto the IIS Server itself (with remote desktop) then the website shows fine, as per this link (I used port 801 for this site):
http://localhost:801/
However when attempting to access this site from the network, it refuses to work, giving the generic 'cannot display the webpage' message, while using the following link:
http://<<my IIS server>>:801/
Another thing I have noticed however is that on the network the default page (port 80) of the IIS server DOES work. I.E this following link shows the standard IIS7 page:
http://<<my IIS server>>:80/
Most of the help topics I've read point to it being a firewall issue, however as a test I disabled all firewall settings on the IIS Server, yet it still refused to show.
Does anyone have any other suggestions?
Many thanks
Did you tried with computer name and / or IP Address
e.g: http://192.168.1.105:80/
http://DELL_PC:80/
Run the following tests:
Check connectivity from both computers.
Firewall settings, temporary disable the firewall from all profiles (private, domain, public) if this works, try adding a Port Rule to your firewall allowing incoming connections to port 80.
Also, it'd be important to check the bindings configuration of your website, bindings specify the address the server should listen to for incoming connections, make sure you have 'All Unassigned'.
Reference : Click Here !!