unable to connect to citris.com with Butt app. keep getting an "error resolving server address" message. Any guidance on resolving please? - connection

Butt app has an "error resolving server address" when attempting to connecting to a live citris.com server
been trying for the last few weeks and suddenly stopped connecting for a live broadcast . Has been ok for the last 5 years

Related

Error "Timed out waiting for the socket to be ready for a write" while connecting to server in Xcode

I am trying to connect to server for web socket connection. but I am getting the error:
"Websocket is disconnected: Optional(Starscream.WSError(type:
Starscream.ErrorType.writeTimeoutError, message: \"Timed out waiting
for the socket to be ready for a write\", code: 0))"
Starscream.WSError(type: Starscream.ErrorType.writeTimeoutError
How can I solve it? also
Here is my source code link:
https://www.dropbox.com/s/v348vxxjf74dsds/websocket.zip?dl=0
I tried to connect after some time again too, Once its failed but still it's giving me same error.
I tried your code, it's working fine. the only change I have made is your socket server URL
before it was ws://192.168.1.2:8080
and I have updated with "http://192.168.1.41:8080" //41 is my IP. you can use yours
just changed ws with http.

java.lang.Exception: The server rejected the connection: None of the protocols were accepted

I/we(the company) have a weird issue with Jenkins and the connection between Master and Slave.
After a while the connection is rejected/timed out for some reason.
We tried to start it as a Windows Service but that didn't go well(also error message). We try it again, maybe we didn't start it properly.
Below is the error Message(3) and the error from the Server(1) and slave(2)
How can we/I resolve this?
I read that this is still a bug in Jenkins but is there really no workaround?
1,2,3

web reference not working when deployed live

I used a webreference in my mvc project. It is working properly for my project locally but i am getting the following error when i deployed my project in live.
System.Net.Sockets.SocketException:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond 46.xxx.xxx.xxx:80
Please help me solve this.

Using RestKit with local server

I've got RestKit in my iPhone app interacting with a Rails app on Heroku, but RestKit won't seem to work with the Rails app running locally on my machine. Here's the output in my iPhone app:
Fail: Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." NSErrorFailingURLKey=http://0.0.0.0:3000/users/1.json, NSUnderlyingError=0x2a9690 "Could not connect to the server."}
I've done all the sanity checks. http://0.0.0.0:3000/users/1.json returns a JSON object in my browser and when I change the root URL to the app on Heroku, RestKit works fine.
Is there something I'm missing? How do I get RestKit to work with the local version of my app?
This was a dumb error on my part. An app running on a device obviously can't access a rails app running on localhost.
This works fine in the simulator or when pointed to a production server.

How do I push to Heroku or get info/status when it "hung up" or does not respond?

Got that error when trying to push updated app to Heroku (probably the same as this question):
> git push heroku master
ssh: connect to host heroku.com port 22: Bad file number
fatal: The remote end hung up unexpectedly
I cannot connect to the API URL
> heroku info
! Unable to connect to api.heroku.com
Nor can I get status
> heroku status
C:/Ruby192/lib/ruby/1.9.1/net/http.rb:644:in `initialize':
A connection attempt failed because the connected party did
not properly respond after a period of time, or established
connection failed because connected host has failed to resp
ond. - connect(2) Errno::ETIMEDOUT)
Had that error on two separate occasions today.
Once when on WIFI at a cafe. Presumably port 22 blocked, though unconfirmed.
Second occurrence was at home whilst had VPN connection in to office. Likely due to some sort of firewall rule. It now works fine having disconnected from the VPN.
Conclusion is that this is a network issue.

Resources