I am using myeclipse to generate web service client. I change my network connection to Native (Use proxy address) but still am getting this error:
"unable to tunnel through proxy. proxy returns http/1.0 504"
Any solution for this?
Related
So I have been using the cloud_sql_proxy for a while now for a local development environment and never had any issues (over a year). I tried to connect today, and it authenticates fine. Yet, connecting to the local port gives a connectex error:
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.
I authenticate with a service account at a location specified in my environmental variables. I connect with the command cloud_sql_proxy -instances="XXXXX.XXXXX.XXXXX"=tcp:5432
Windows 10
The Cloud SQL instance works fine and communicates (over a similar proxy) with the production server.
I tried connecting with Django, get connectex error.
I tried to ping the local network, get connectex error.
I tried adding a firewall rule that allows all outbound traffic to port 3307
Any ideas what could've broken my proxy?
If the connection to the Cloud SQL proxy times out, it means the connection to the proxy itself didn't work. That means either the proxy is not listening, or that something it blocking the connection.
I would suggest looking in the proxy logs to see if it reports any start up errors.
I have a websocket server built with go running on AWS beanstalk. I'm running a load balancer with a SSL cert. I'm having issues connecting to it via the browser. If I try to connect to it through another go program running on my terminal everything works fine. I've updated my environment to accept TCP instead of HTTP connections on port 80.
When I try to connect from the webapp though I get this error.
WebSocket connection to 'wss://root.com/users/fcbd7f8d-2ef6-4fe2-b46c-22db9b107214/sockets/client'
failed: Error during WebSocket handshake: Unexpected response code: 400
When I check the AWS logs I find this error.
the client is not using the websocket protocol:
'websocket' token not found in 'Upgrade' header
UPDATE
if I run the webapp on my localhost and change the connection string from wss:// to ws:// it works. If I try the same url in the live webapp I get an ssl error.
Mixed Content: The page at 'https://root.com/captions' was loaded over HTTPS,
but attempted to connect to the insecure WebSocket endpoint
'ws://root.com/users/fcbd7f8d-2ef6-4fe2-b46c-22db9b107214/sockets/client'.
This request has been blocked; this endpoint must be available over WSS.
I have configured WSO2 Identity Server following this doc.
But when i log in to my webapp I get the following error :
Connection Refused.
I'm behind a corporate proxy. How should I configure IS server to make it work?
If you are having issues with connecting outside from your network without a proxy, you can use the following jvm parameters during the server startup to provide the proxy configurations.
ex:
sh wso2server.sh -Dhttp.proxyHost=10.0.0.100 -Dhttp.proxyPort=8000
-Dhttp.nonProxyHosts="localhost|127.0.0.1|10.*.*.*"
I am trying to integrate the Mule Amazon SNS connector behind the corporate proxy and having much trouble to bypass the proxy. It always give me this error:
[[snstest].HTTP_Listener_Configuration.worker.01]
com.amazonaws.http.AmazonHttpClient: Unable to execute HTTP request:
Connection to https://sns.us-east-1.amazonaws.com refused
Exception stack is:
Unable to execute HTTP request: Connection to https://sns.us-east-1.amazonaws.com refused
Failed to invoke createTopic. Message payload is of type: NullPayload
org.mule.modules.sns.processors.CreateTopicMessageProcessor:129
I believe the issue is the proxy trying to block the connection between the application and the amazon endpoint. When I try it at home with direct internet, it worked. Also, I have also tried http:connector and http:proxy to configure the proxy and it has not worked at all.
Check the secret key and access key. Issue is not with proxy its problem in credentials.
I have proxy service on WSO2 Enterprise Service Bus 4.8.1. It makes pass through proxy to Echo service on the same server. After restart ESB server this service disappears because of
ERROR - ProxyService Error reading from wsdl URI java.net.ConnectException: Connection refused: connect
WARN - Axis2SynapseController The proxy service echoProxy cannot be deployed - Continue in Proxy Service fail-safe mode.
I think that internal service Echo is not started when this service starting and it causes this error. When ESB server is completely started Echo servise is running and it is possible to deploy echoProxy service. But I don't know how.
For your proxy, i believe you used option. That is why you get that error. If you go to repository/deployment/server/synapse/default/proxy folder, you will see the proxy configuration which you created. You can make a copy from that, and after server starts fine, you can deploy that file in the same location. It will be deployed successfully