I am trying Wso2 API Manager in EC2 Ubuntu instance. When i run the ./wso2server.sh, the host name is set to the Private IP of the EC2 machine. To change that Private IP to my elastic IP i changed
<ServerURL>https://${carbon.local.ip}:${carbon.management.port}${carbon.context}/services/</ServerURL>
to
https:// <-- elastic_IP --
:${carbon.management.port}${carbon.context}/services/
inside PRODUCT_HOME/repository/conf/carbox.xml.
This didn't solve my issue. So i replaced all ${carbon.local.ip} present inside PRODUCT_HOME/repository/conf/ to my elastic IP, but still when i started the server i am getting 'CarbonUIServiceComponent Mgt Console URL with my private IP'
can someone help me solve this issue of changing the Private_IP to elastic_IP ?
Thanks
Thanks for trying out API Manager on EC2.
This seems to be a bug in API Manager 1.0.0. Created an issue (https://wso2.org/jira/browse/APIMANAGER-703) to track the progress. Fix will be available on API Manager 1.0.1 release (scheduled to happen by mid of September 2012).
Related
I am using an Aws EC2 with Ubuntu, I installed Xampp and it is working fine, the problem that I have it's that if I put this url:
xellin.com
It will open the Xampp dashboard... if you check this url too:
http://xellin.com/akivoy/
You will see that there is a website, I wonder how can I do if I put xellin.com it diplays what it's in xellin.com/akivoy?
Is it possible? Thanks!
If xellin.com is your domain, you need to associate it with the elastic IP address of your EC2 instance. It is the only way in which DNS systems will know how route/propagate traffic to your instance.
I want to deploy the api manager on a server of the company, but I never did't and I need some help, I already installed the wso2 esb and it's ok, but the new release (3.0) is giving me a localhost link to acess the store and the publisher, so I can't access this from another computer what I'm doing wrong?
Any help will be much apreciated
Extract a new APIM 3.0 zip and configure hostname in deployment.toml to be a hostname or a public IP of the server. Then you can use that public IP to access the server.
[server]
hostname = "192.168.0.1"
I have installed Ionic in my AWS Linux instance. The 'ionic address' option gives 3 addresses - (1)Eth0(2)docker ip (3)localhost.
I have tried selecting each of these options and have tried connecting from my windows browser. But none of it works and ofcourse ping of all these IPs fail.
I have enabled the port 8100 in AWS instance and have tried connecting through the AWS public ip as well.
What am I doing wrongly - can someone pls help me here.
I'm trying to install a WSO2 EMM server on Amazon EC2 Instance, but have a problem with it. EC2 instance have 2 IP addresses - one of them is internal Amazon address like 172.32.x.x, another is external real IP.
If I try to setup carbon.xml file with real IP (or domain), I have a problem with thrift server, which can't open port 10500 at a real IP. If I use internal IP running of server is fine, but in application I can't reach identity server (because it's a gray IP, of course).
I tried some tricks with using /etc/hosts file, for example, setup 0.0.0.0 as my domain. In this case server is running without errors, and a can see that port 10500 is open using netstat, but web application is not redirect to identity server.
May be there are any solutions of this problem?
I have to update EMM server to version 1.1.0 and all is working now.
Thanks all!
In the carbon.xml, change the HostName and MgtHostName to the real IP and start the server.
For example if the real IP is 172.32.x.x then HostName and MgtHostName in the carbon.xml should change to:
<HostName>172.32.x.x</HostName>
<MgtHostName>172.32.x.x</MgtHostName>
I have an single EC2 CentOS instance with ElasticSearch installed.
I am unable to connect externally using the public ip or hostname.
ElasticSearch starts correctly and I can access locally on the machine using:
CURL <my_internal_ip>:9200
However running the same remotely using the public ip fails.
I have the the cloud-aws plugin is installed
I have setup an AWS security group with all tcp ports open for testing
I am guessing I need to bind the address within the elasticsearch.yml file, however do not understand which setting to use, and with what address. Setting the network.host to an external address stops ES from starting - unable to bind.
Appreciate any comments.
Amazon Ec2 Instance is use remotely according with the Elastic Search Installed that provide the aws cloud plugins
After many hours....
IP Tables was enabled on the OS as default blocking my elasticsearch ports.
I've the same issue and followed below steps and get resolved:
Elasticsearch process memory locking failed
MAX_LOCKED_MEMORY=unlimited
LimitMEMLOCK=infinity
Do these two steps also.