error image feign-client error test enviroment
The code work correctly in localhost connection.
In test enviroment don't work.
I have microservices that run in the cloud.
I tried to add in the application.properties of NewsService:
feign.client.config.default.connectTimeout=160000000
feign.client.config.default.readTimeout=160000000
But not work.
It is as if it did not reach notification-service from the feign-client call.
Locally on other calls I received this error and I changed the type of connection: from ethernet cable to router with the phone. Since the environment is in the cloud, I cannot solve it like this.
I solved it by knocking down and retiring on the pods: service-registry, gatway-service, news-service and notification-service.
The environment is now cleaner
Related
I have successful setup Concourse (5.7.1) on Ubuntu (16.04). Everything was find but after adding a script in deploy job to call an restful service running on same machine where concourse is installed, I got
error:Failed to connect to xxx.xxx.xx.xx port 9090: No route to host
I have been able to call the restful service from other sources.
I intercept the Job and i was not able to make make a call to the service but I was able to ping external calls
Sorry for taking this long to response. If someone else has the same problem. I succeeded to solve this problem by restarting my servers.
I don't know what exactly may had been the problem but restarting the servers works and it solved my problem.
I am new to JMeter. I have created one script for our application. Now our complete system architecture is deployed on AWS. So, we have created one EC2 instance as "Load Generator" to run my script with 100 user load. Script is working fine on my local system but it is not working on that instance.
Every time I am getting below error. I have also tried to run from non-GUI mode as well but result is same.
Error: Response code: Non HTTP response code: java.net.ConnectException Response message: Non HTTP response message:
Connection timed out (Connection timed out)
Please help me out here. How to resolve this issue on EC2 instance.
I had a similar problem (my tests were executed on Microsoft's Azure).
The issue was that the system being tested had a IP white list.
When I ran it on my local machine, it was already within our VPN
(whitelisted).
When it was executed on Azure, the VM had a
dynamic IP which was not whitelisted.
For the purposes of testing. I have three computers running 9 containers locally on top of a ruby Sinatra server, testing an Android app. I'm using calabash server with cucumber steps.
All was running fine until about a month ago and I started seeing Calabash server errors. The first few containers run fine. Then it gets to around the 5th container and I start seeing a connection error as follow: "
Error in Remote Calabash Server: 'Connection refused - Connection
refused - connect for "127.0.0.1" port 37265 (127.0.0.1:37265)'"
Followed by a long runtime error.
And that container craps out. The other containers will then usually run successfully after that.
I understand it's a very broad sounding issue and there's a lot of variables at play. But any suggestions at all of where to look would be most helpful. Could the servers just be struggling with too many requests? It's not getting hit by many at once, but who knows at this stage.
Any help as always much appreciated.
I am testing with the v2 C# payment example.
https://github.com/petespatio/connect-api-examples/tree/master/connect-examples/v2/csharp_payment/PaymentExample
When i run locally everything works properly and i can actually create a payment.
When i try to run on my website (1and1 hosted), i get
error calling charge: unable to connect to the remote server
Does anyone know what has to be done to allow this connection?
Regards
Have you tried pining the server you are connecting to? That's a good place to start. Try:
ping connect.squareup.com
To see if you can connect at all. If you can't ping the server, it might be a firewall issue on your server.
1&1 has information about setting firewall rules on their hardware firewalls for their dedicated linux servers here:
https://help.1and1.com/servers-c37684/dedicated-server-linux-c37687/system-security-c37699
and information on setting firewall rules for their cloud servers here:
https://www.1and1.com/cloud-community/learn/networking/firewall/
Hope this helps!
I am using the same setup as on the server. I have an EC2 instance running Ubuntu, then I am using Docker to host an Ubuntu image with runs my Laravel project on nginx and php7. My local is setup up the exact same, I use the same Docker image and everything.
When I test my emails on my local they work seamlessly, no errors or problems but as soon as I test it on my EC2 I get the following error in Laravel:
Swift_TransportException: Connection to tcp://smtp.mailgun.org:587 Timed Out in /app/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php:404
I have tried using ports 25, 2525 and 465 butt he exact same result. Here are my env variables:
MAIL_DRIVER=smtp
MAIL_HOST=smtp.mailgun.org
MAIL_PORT=587
MAIL_USERNAME=postmaster#placeholder.com
MAIL_PASSWORD=5uup3rL0nGPa55w0RdY0uPr0bablykn0
MAIL_ENCRYPTION=tls
MAIL_FROM_ADDRESS=no-reply#placeholder.com
MAIL_FROM_NAME="placeholder Team"
MAILGUN_DOMAIN=placeholder.com
MAILGUN_SECRET=key-MyK3y1s0ac001y0uw15hy0uhadi7h3h3
The secret and password is fake data
On Mailgun's dashboard I have verified my domain (locally I use localhost.MYDOMAIN.com pointing to 127.0.0.1) and all checks are green except for mxa.mailgun.org and mxb.mailgun.org because we are using gmail for our emails. Not sure if this is the source but I cannot risk disabling the emails just for a test.
If I telnet to Mailgun using telnet smtp.mailgun.org 25 (or any other port) I get a connection, so I do get access.
I also applied to relieve the email sending throttling on my server that Amazon puts onto EC2 servers. Not sure when this will actually be in effect so not sure if it will help or not (It might)
I am not sure why I only get a timeout on my server and it works on my local but any advice would be appreciated!
I did try searching around for answers but did not succeed.
WORKAROUND If anyone is struggling with this same issue, it is not worth the effort, rather just implement the Mailgun API, this way you do not have to put up with these issues, it is what I have now done which, had I known about the issues I would have faced, would have done from the start. So still no solution from my side, just avoided it and also why I am not updating with an answer and instead just updating with an edit. Not sure if this is the correct way.