Unable to communicate with server - I/O error on GET request for "https://api.ng.bluemix.net/info":Connect to 10.81.82.132:80 [/10.81.82.132] failed: Connection timed out: connect; nested exception is org.apache.http.conn.HttpHostConnectException: Connect to 10.81.82.132:80 [/10.81.82.132] failed: Connection timed out: connect
I am getting this error when trying to create a Bluemix server in Eclipse, specifically on click of Validate Account button. I have downloaded and installed the IBM Bluemix for Eclipse plug-in but still having connectivity issues. Any help is appreciated.
The connection error is depending from the wrong IP address your internet ISP/provider is returning for api.ng.bluemix.net
Check your DNS configuration, you could run the following command
nslookup api.ng.bluemix.net
to check which DNS server is returning the wrong IP address.
Related
I am unable to connect to a Mongo db which is hosted in IBM cloud. I have got the credentials and the db name. I am using direct authentication method but getting sometime timeout error or sometime "Client network socket disconnected before secure TLS connection was established" error. I am new to Mongo client. It seems ibm cloud team do not set any restrictions and on public internet. I can do a telnet with the server string.
1.Do I need to use any configuration in Mongo compass client like installing certificates?
2.Do I need to request for ip binding (though my ip is dynamic)
Any help will be appreciated on this
I am developing a MERN stack application. My Node web server used to work fine. Recently however, whenever I start my Node server, I get the following error:
[1] Error: queryTxt ESERVFAIL cluster0.b4oyxi0.mongodb.net
[0] [HPM] Error occurred while proxying request localhost:3000/api/users/login to http://localhost:5000/ [ECONNRESET] (https://nodejs.org/api/errors.html#errors_common_system_errors)
[1] [nodemon] app crashed - waiting for file changes before starting...
What does this error mean and how can I fix it?
Not exactly sure what the error means. I encountered a similar error and the non +srv connection string did it for me.
To get one,
head out to your Atlas Dashboard under Database Deployment,
click Connect,
then choose Connect your application.
On the Node.js driver version, lower that to 2.2.12 or later.
This should give the connection string.
It's a DNS server issue. Try changing your DNS server in your network settings to any of these, or any other trusted one you know:
208.67.222.222
1.1.1.1
8.8.8.8
9.9.9.9
I have three apps running in 3 containers on the same host.
CONTAINER ID IMAGE COMMAND PORTS
3f938111c1bf registration "java -jar registration.jar" 0.0.0.0:8030->8030/tcp
cb9c4782194e security "java -jar security.jar" 0.0.0.0:8020->8020/tcp
60005507a246 main "java -jar main.jar" 0.0.0.0:8000->8000/tcp
I am able to access an endpoint of the security app from main app using an Ajax request.
The registration app calls an endpoint of security app from a java method using a RestTemplate object. This call is refused by the security app as follows.
I/O error on POST request for "http://localhost:8020/security/register": Connect to localhost:8020 [localhost/127.0.0.1] failed: Connection refused (Connection refused); nested exception is org.apache.http.conn.HttpHostConnectException: Connect to localhost:8020 [localhost/127.0.0.1] failed: Connection refused (Connection refused)
I am not able to identify the issue. Note that this call is working perfectly fine when I run these apps locally through eclipse.
I am very new to the dockers. Is there a possibility that I am missing out something? Any leads would be helpful.
Thanks a lot!
When you work with docker containers/images so you need to set your configurations on them. So you must change localhost to your container name. For example:
http://localhost:8020/security/register
http://authentication:8020/security/register
I'm trying to connect a database in the Bluemix DB2 on Cloud (DashDB) to IBM BPM on Cloud. Is this possible? I tried setting up a datasource in BPMoC using the data provided by DB2 on Cloud, but it is not able to connect:
(Error Details)[jcc][t4][2043][11550][4.18.60] Exception
java.net.SocketException: Error opening socket to server ... with
message: Network is unreachable (connect failed). ERRORCODE=-4499,
SQLSTATE=08001 DSRA0010E: SQL State = 08001, Error Code = -4,499Test
Connection
IBM BPM on Cloud support was able to help me get this working. There was something that needed to be done on the network side of things to allow BPMoC to talk with DB2 on Cloud (Bluemix). They also had to install the SSL certs for me.
Getting this error in instance log. I could not seek out any errors in nova or neutron log.
Checked with all configuration and everything is fine.
url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: request error [(, 'Connection to 169.254.169.254 timed out. (connect timeout=50.0)')]
Anyone could help whats the actual error and how to solve it?
Probable Reason1:-
I guess you are running instances with GUI installed on them. When you install GUI on an instance(ubuntu/centos or whatever), they bring in a bunch of different services. Specially, in ubuntu, a service named "avahi" gets added and started which adds a route of 169.254/16 on the instance. This starts causing the issue as now the instance thinks that it can reach 169.254.169.254 directly rather than sending the packets to the gateway.
More details why this happens and how you can stop this can be found on this blog.
https://rahulait.wordpress.com/2016/04/02/metadata-failure-with-ubuntu-desktop-on-openstack/
Probable Reason2:-
If you have a private-network and it is not connected to any "router", the gateway interface for that private-network will be down. For communicating to metadata service, the packets needs to be sent to gateway of network, which would not be reachable in this case and hence you would see these logs.
I hope it helps.
In my case this error raised because the L3 agent was down due to some corruption in the ini file. Check if there is an agent down in neutron:
openstack network agent list
Fix the issue (check the log at /var/log/neutron and restart the service)
service neutron-l3-agent restart
This happened to me on a node that was still running nova-network from a previous configuration.
The effect on the faulty node was this (bad):
# curl -v http://169.254.169.254/openstack
* Hostname was NOT found in DNS cache
* Trying 169.254.169.254...
* connect to 169.254.169.254 port 80 failed: Connection refused
* Failed to connect to 169.254.169.254 port 80: Connection refused
* Closing connection 0
curl: (7) Failed to connect to 169.254.169.254 port 80: Connection refused
...instead of this (good):
# curl -v http://169.254.169.254/openstack
* Hostname was NOT found in DNS cache
* Trying 169.254.169.254...
* Immediate connect fail for 169.254.169.254: Network is unreachable
* Closing connection 0
curl: (7) Couldn't connect to server
If this is the case get rid of the legacy service on your node and enjoy.