I am using Secure Gateway of ibm blue-mix.
However, I do not know how to do "500 Error: Failed to establish a backside connection" error.
The situation is as follows:
When accessing, the following message will be displayed on the Secure Gateway client.
[INFO] (Client ID keqdVTJMrJt_prF) Connection #1 is being estabrished to xxx.xxx.xxx.xxx:nnn
The display of the log is
"[INFO ] SRVE0242I: [ChisInq003] [/ChisInq003] [Servlet.ChisServlet003]: Initialization successful.".
However, if it takes about two minutes, "500 Error" will be displayed.
Does anyone know what to do?
If the connection fails after ~2 minutes, it sounds like the connection between the Secure Gateway Client and the host:port it is trying to connect to is timing out which implies a network issue.
Are there any additional Secure Gateway Client logs that can be shared that might contain an error? What is it that you're trying to connect to via Secure Gateway?
Related
I am failing to connect to this SQL Server 2019 using a fully qualified database server name,21433. This has been working for over 18 months. There is a new network changes. The rule for mapping 21433 is active.
The connection fails when I use Verizon's gateway network but when I tether my sprint phone it works.
The error below:
Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=43; handshake=29988; (.Net SqlClient Data Provider)
The problem was with Palo Alto VPN.
When it was enabled, it blocked any port other 3389.
When it was disabled, I could connect to the port 21433 worked perfectly. The downside
as I could not rdp because the Palo Alto VPN was disabled.
It will be fixed by properly configuring the Palo Alto VPN.
My bluemix securegateway client installed on linux , gives an error as :
[2017-10-03 04:08:05.791] [DEBUG] (Client ID 16583) The Secure Gateway client will fetch its configuration from https://sgmanager.ng.bluemix.net/sgconfig/[masked]
[2017-10-03 04:09:08.882] [ERROR] (Client ID 16583) The response is code: ETIMEDOUT, message: connect
This was working earlier , but suddenly stopped connecting.
Does the client use curl to get to the above configuration url ?
The SG Client doesn't use curl specifically, but it does make an HTTPS request to sgmanager.ng.bluemix.net as part of the initial connection process. Following this request, a second HTTPS request is made to cap-sg-prd-#.integration.ibmcloud.com:9000 where # is 1-5 depending on the details of your specific gateway.
ETIMEDOUT is typically caused by something like a firewall blocking your requests, so you could use something like telnet to confirm your connectivity. A successful connection should be similar to:
telnet sgmanager.ng.bluemix.net 443
Trying 169.54.245.68...
Connected to ng.bluemix.net.
Escape character is '^]'.
and
telnet cap-sg-prd-1.integration.ibmcloud.com 9000
Trying 169.55.54.176...
Connected to cap-sg-prd-1.integration.ibmcloud.com.
Escape character is '^]'.
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.
We have Tableau Desktop & Redshift as datasource. When we are publishing the report to Tableau server (hosted) we are getting following error :
An unexpected error occurred on the server. If you continue to receive this error please contact your Tableau Server Administrator.
TableauException: Could not connect to the server; 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. [58.89.281.166:5439] Unable to connect to the server "abc.redshift.amazonaws.com". Check that the server is running and that you have access privile...
2014-06-17 13:56:20.974 (U6BI2gq#AWoAAB0gowQAAAGi,0,1)
This is likely caused by the Tableau Server not being able to access the Redshift Server you listed. It looks like a time out occurred which indicates that a connection attempt failed.
Since it's hosted, you might not be able to verify the connection directly. If you can log onto the Tableau Server and access Windows, you can attempt to establish a connection to the RedShift server at the command line using a tool like Telnet. You need to make sure that the Tableau Server in question can access the Redshift server (verify firewall and security settings for both the Tableau Server and Redshift instance).
I have a FIX server and FIX client implementing FIX4.4 running on the same network. I use QuickFIX C++ engine. Altough they are on the same network, sometimes they disconnect. In the FIX server's event logs:
20140612-01:21:30.000 : Sent test request TEST
20140612-04:11:56.000 : Sent test request TEST
20140612-07:05:26.029 : Sent test request TEST
20140612-07:05:26.029 : Socket Error: An established connection was aborted by the software in your host machine.
Means HEARTBIT messages are failed to send/recv.
What can be wrong? I have a regular setup and nothing special..
Thanks
while the client connection was accepted by the server, it doesn't look like you then achieved "logon". First you connect, then you logon. You need to make a logon request after you connect. Look at the initial FIX messages sent between client and server.