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.*.*.*"
Related
I've installed WSO2 Api Manager 4.0.0 on internal server and I have no idea how to tell it to use proxy server to connect to Choreo analytics.
I see following error in the log:
:Provided authentication endpoint https://analytics-event-auth.choreo.dev/auth/v1 is not reachable.
I've tried to set http_proxy, https_proxy, HTTP_PROXY and HTTPS_PROXY environment variables with flag java.net.useSystemProxies=true to api_manager.sh but they seem to not work and I don't see any traffic coming from this server through proxy.
Adding java flags http.proxyHost and http.proxyPort didn't helped too.
If I start it from server with internet access then it works just fine with Choreo.
Is there any way to set the proxy for APIM?
WSO2 API Manager's gateway component talks to an API in the Analytics cloud in order to fetch required credentials to publish events to the cloud. The failure that you have pointed out occurs at the point of talking to this API. It appears that proxy settings have not been configured for this particular HTTP client. Please see here.
Event publishing is the next step and uses AMQP protocol. Therefore I think it would not go through the HTTP/S proxy. However, if the gateway has no access to the internet, this step will fail again regardless of the API call is fixed to honour the proxy settings.
Currently, analytics does not have the support to publish events through a proxy. It seems that in order to honour proxy settings in event publishing, the protocol needs to be changed to Websocket.
New to AWS and AWS CLI, I have installed and configured the AWS CLI, and I am simply trying to list the buckets in S3, but I am behind a proxy.
How do I troubleshoot and resolve and the following error?
C:\Users\MyUserName\Desktop >aws s3 ls
HTTPSConnectionPool(host='s3.us-east-2.amazonaws.com', port=443): Max retries exceeded with url: / (Caused by ProxyError('Cannot connect to proxy.', error(10060, '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')))
The only troubleshooting step I have attempted is to Set the HTTP_PROXY and HTTPS_PROXY variables to my IP on port 80.
The key to using the AWS CLI behind a proxy is to configure two environment variables.
The IP address is the address of your proxy server, which is probably not your local IP. Consult with your network administrator to get the correct IP address and basic authentication parameters.
Chrome, IE, etc. support proxy servers, so you may already have these parameters setup in your browser. For Chrome go to settings and search for Open proxy settings. Similar technique for other browsers.
For Windows:
set HTTP_PROXY=http://a.b.c.d:n
set HTTPS_PROXY=http://w.x.y.z:m
Or for basic authentication:
set HTTP_PROXY=http://username:password#a.b.c.d:n
set HTTPS_PROXY=http://username:password#w.x.y.z:m
For Linux, macOS, or Unix:
export HTTP_PROXY=http://a.b.c.d:n
export HTTPS_PROXY=http://w.x.y.z:m
Or for basic authentication:
export HTTP_PROXY=http://username:password#a.b.c.d:n
export HTTPS_PROXY=http://username:password#w.x.y.z:m
Using an HTTP Proxy
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 want configuration files for WSO2 ELB 2.1.1 and WSO2 ESB 4.8.1, axis2.xml loadbalancer.config carbon.xml catalina-server.xml and any other if there.
I have configured with one ELB(offset 0, 8280), one manager(offset 1, 8281) and one worker(offset 2, 8282) ESB and when i try to send a request via ELB I'm getting
DynamicLoadbalanceEndpoint application member not available
but both are available and get the log that mgt and worker have joined when they turn on in ELB.
Initially when i send a request i have got
httpclient.HttpMethodDirector: I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
then I have set allowall in axis2.xml and got the error which I have mentioned.
What would be the problem? If someone who have already configured could share the configuration files it will be very helpful for me.
Thanks.
Please refer WSO2 Clustering and Deployment Guide. There are instructions to configure an ESB cluster.
If the ESB cluster is not connected to the ELB, you will see "application member not available" message in ELB logs when you try to send requests.
Maybe this will be useful to someone else in future:
The WSO2 Elastic Load Balancer has been discontinued as of July 1st 2015. You can download NGinx Plus [1] - the load balancer by NGinx - for which we provide support.
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