I Create a New Website in Windows IIS , It has been working for several months
but i get this error today.
“The connection has timed out.”
the server 192.168.1.7 at is taking too long to respond
i set binding
and get this error
you can also be set in the web.config (example is for 2 minutes, 120 seconds):
<limits connectionTimeout="00:02:00" />
Try to clear the host name, and then use localhost to access your website in server.If you do not access your website locally, you need to use the IP address to access. If you have registered a domain name and completed the binding, you can also use the domain name to access.
Related
I'm working on a Rails app that is hosted on Heroku and has a custom domain configured to point to the Heroku DNS target. In other words, it can be accessed at both appname.herokuapp.com and appname.com.
The owner of the app experienced an issue recently where the domain name registrar mistakenly deactivated the domain due to an error in recording the subscription payment. The issue has since been resolved, but the owner wants to know if we can set up a custom error page to show in this situation, instead of the browser error page that would normally show in this case.
I am a novice developer, but my suspicion is that this is not possible. If the registrar believed at the time that the domain did not belong to the person, why would they allow that person to decide the error page or redirect to an alternate version of the site?
Am I correct on this or is there an alternative solution?
Since DNS resolves appname.com to an IP Address. then if DNS is unavailable the machine trying to resolve the address won't have an address to connect to to get the website from.
If the DNS records have a long TTL (time to live - basically the time that it takes to flush the name from the cache of nameservers) then it will stay online even if the DNS server is offline. However this would only work for nameservers that have previously resolved those records.
My JSF website(http://discountbox.in) is returning 404 Not Found error since night most of the times. But my friends are able to see my website. When I access via my mobile I am able to access the site.
What can be the cause for this, of this. I have deployed the application in tomcat and not using apache at all. It was working for year, only since a day I am having this issue.
This could be caused by the DNS registered on your own router.
Your client (PC) in the same network as your server and aforementionned router needs to access your website via local IP (something like 192.168.X.X).
i am trying to use swift mailer to send emails with mandrill API. I was working on a server and it worked great. Then when i changed to another server and it shows this: Fatal error: Uncaught exception 'Swift_TransportException' with message 'Connection could not be established with host smtp.mandrillapp.com [Connection refused #111]'
can anyone help?
This is typically a result of your hosting provider blocking the port being used or blocking external SMTP connections. You'll likely want to get in touch with the host for the new server you're working with since many shared hosting providers limit or prohibit the use of certain ports or external services.
In my case, I had not mentioned port number 587. mandrillapp changed from default 25 to 587 now.
Here is my situation. I have an application (Mirth Connect) running on the same server as SQL Anywhere 11. There is also another server on the same network running SQL Anywhere 11. I need to connect to both of them. They are both using the same SQL Anywhere "Server Name".
I need to use a JDBC connection to connect to either of them at any given moment. I can connect to the local instance just fine.
I tried to set up an ODBC connection to the remote server. When I test the connection it says it is all good. Then when I try to run a query I notice I am connected to the local server. It must be because both SQL Anywhere servers are using the same "Server Name".
How do I force the ODBC connection to connect to the Remote server?
Thank you!
You need to specify the IP address (and port, if not using the default) in the connection string. Your connection string must contain the LINKS parameter, with (at least) the following options:
LINKS=tcpip(HOST=<remote IP address>;PORT=<remote port>;DoBroadcast=None)
If the remote server is using the default port number, 2638, you don't need to specify the port number in the connection string. DoBroadcast=None tells the client library that it should make a direct connection to that host. The default (for version 11 and older) is to broadcast on the network looking for that server name, and whichever server responds first wins. Since there is a server on the local machine, it is very likely to respond first.
For version 12 and up, you can replace the entire LINKS parameter with the new HOST parameter:
HOST=<remote IP address>:<remote port>
which will have the same behaviour as the LINKS parameter above.
P.S. It is recommended that you give each server a unique server name, thus avoiding the need to hard-code the IP address of the host. Not to mention that you must be using some trickery to fool the second server into either (a) thinking its name is unique, or (b) not checking to see if it's unique, which it does by default. If you use unique server names, you don't need this extra stuff.
Disclaimer: I work for Sybase in SQL Anywhere engineering.
For the past several days I've been working tirelessly to setup a test environment for development with WIF & ADFS 2.0. One of the problems that I am up against is my home environment only has one IP address and I wasn't about to stick ADFS on my main server. Therefore, I've created a dedicated virtual machine for FS (idp.yyy.local).
For the sake of not having direct links back to my site, 'yyy' refers to 'dgdev'. (image below)
The strange thing is, it's partially working. Here is an image detailing my infrastructure.
What's odd is that I can browse 'idp.yyy.net' in both normal HTTP and HTTPS just fine. I can also view the WS-Federation Metadata perfectly. Now, I'm quite new to ADFS, but I expect that when going to http://idp.yyy.net/adfs/services/trust it would redirect me to a Windows SSL login. Instead all I'm receiving is:
Service Unavailable
HTTP Error 503. The service is unavailable.
I am using the same SSL certificate on the FS Proxy and FS. Its subject is my main domain name yyy.net. It has several Subject Alternative Names so that I can host multiple IIS web sites with SSL with my single IP:Port.
CN = yyy.net
DNS Name=www.yyy.net
DNS Name=idp.yyy.net
DNS Name=idp.yyy.local
...
IP Address=192.168.1.2
IP Address=192.168.1.3
IP Address=192.168.1.4
...
Does anyone have any idea of why I'm seeing 503 Service Unavailable errors. Nothing is showing up in Event Viewer as an error. (except annoying things with AppFabric, but that's another issue I've yet to touch)
Thanks in advance! Actually many many thanks. I've exhausted every avenue and idea I could come up with, why this might be "broken"?
If anyone has an idea how I can debug this issue I'd certainly except that as a solution. I've tried IIS Failed Request Logging but nothing is being generated. Where/What is hosting the ADFS Services?
Things I've already looked at:
All AppPools are running.
The old ADFS 1.0 web service (asmx) is accessible just fine.
I can access issuer endpoints directly ... or at least 'windowstransport'
Well turns out everything has been working all along!
I spent a couple hours ensuring the certificate was created properly. Then after still seeing 503 & 403 errors, I realized that my proxy server AppPool for the \Default Web Site was running under "ApplicationPoolIdentity" - which is really the user:
IIS AppPool\DefaultAppPool.
I never gave that user read privileges to the ADFS certificate private key. Hence the reason I saw a 403 Forbidden instead of 503. After switching the AppPool over to Network Service ... voila!, 503 Service Unavailable.
So now I was sure my proxy server and ADFS server were talking just fine. Now why was I still seeing 503 Service Unavailable?!?
I told myself to create a test application anyway. In visual studio, I setup a new MVC 3 Web App. Added my existing STS-Reference. Setup a dummy claim and updated the application's FederationMetadata. Added the new Relying Party to ADFS.
Opened my browser to the web app and instant success!
> GET) https://mywebapp/
> Response-Redirect) Location header kicks me to my IdP (ADFS)
https://idp.yyy.net/adfs/ls/?wa=wsignin1.0&wtrealm.........
> I sign-in with proper credentials
> POST) https://mywebapp/login << AWESOME!