I have been connecting to KAFKA using CONDUKTOR Application. But somehow Conduktor connection is disabled (yellow highlighted in the screenshot), and I am unable to connect to kafka, even after rebooting system twice.
Attaching the screenshot. Any help is appreciated.
Thanks,
To use Conduktor, login is mandatory
As mentioned in Conduktor changelog, from version 1.4.0 onwards it's required to be logged into Conduktor in order to be able to connect to Kafka.
From Conduktor changelog:
Conduktor 1.4.0 (Jan 24, 2020):
We must have to login into Conduktor now. We are integrated with auth0, using a Native app with PKCE oauth flow.
Kafka is running in a docker container
Your host cannot resolve docker containers by name. You need to connect to localhost:9092, or whatever the advertised listener you've set up to your host machine
Related
i’ve created an instance that runs on a linux virtual matchine
i’ve also installed cockroachdb and nakama on that vm and started the node and nakama server there
i’m using oracle cloud infrastructure, i added security list to it to be able to access it through internet and now when try access it through the internet it shos me my server like this :
and now i dont know to to connect to this ???
i have the client in using and it doesn’t connect to it
and when i run it, it shows me this error
i also added the nakama port 7350, and the dashboard 7351 to the security list to have access to them through oci cloud and now the dashboard looks like this
where is the issue and how should i fix it ??
If you are using platform images, both Linux and Windows come with the OS firewall activated and allow very few services.
Open the ports on the OS firewall and try again.
We are upgrading the ZK Server and would like to know the version clients are using to connect so we have a better overview which clients need to be upgraded.
Is there a way of doing this? I tried 'cons' but no luck.
Thx for any advice .
Client versions are added to zookeeper log files when connecting. Considering you have set INFO level on log4j zookeeper configuration, you should observe entries like the following:
2020-10-13 16:38:01,275 [myid:] - INFO [main:Environment#98] - Client environment:zookeeper.version=3.6.2--803c7f1a12f85978cb049af5e4ef23bd8b688715, built on 09/04/2020 12:44 GMT
I'm a new comer to using the overseas server. Recently I bought a vps from virmach in order to see foreign websites like google and wiki.
I've been trying for a long time configuring my shadowsocks on my server.
However, when I was using shadowsocks-qt5 to connect my server, it was timeout.
And of course I can't access google correctly.
What I want to ask is the reason why I failed.
Here are things that I do remember to do:
stop the firewall on both computers;
build the .json file which I referred to blogs in China.
Here are the outline of my shadowsocks.json on my server:
{
"server":"0.0.0.0",
"server_port":8388,
"local_address":"127.0.0.1",
"local_port":1080,
"password":"XXXX",
"timeout":600,
"method":"aes-256-cfb"
}
Other useful(maybe) information:
my client OS version: Ubuntu 18.04.3 LTS
my server OS version: Ubuntu 16.04.6 LTS
the client I choose is from: https://github.com/shadowsocks/shadowsocks-qt5
I could not help but wandered, are there any other possible reasons I've forgot? Can anyone inform me some helpful details to solve this puzzling problems? Thanks a lot!
I have not set up my own VPS but I have instead subscribed to the server provided by caonima.io, so I can't speak for any server related issues. Additionally, I have no affiliation with caonima.io. I did however successfully set up my client on Ubuntu 16.04 after having some issues connecting to GFW-blocked (China's Great FireWall) websites.
From what I understand from my solution, the client configuration is NOT the only step of setup. There are two layers of proxy access that need to be completed:
Client Configuration. Configure your client with the server and connection information. A successful connection looked like this for me with my command line interface
shadowsocks-libev command line client successful connection
System or Browser Proxy Configuration. You will need to configure either your browser or web access tool to use a proxy, or set system-wide proxy settings. To set system wide proxy settings, go to system settings > network > network proxy and enter the proxy information. Setting Socks host to localhost:1080 resulted in successful GFW-blocked website access (as shown below)!
Ubuntu network settings proxy manual configuration
I have configured the Kaa Server on Ubuntu 14.04. I have chosen MongoDB as log appender. When i execute my SDK on the same ubuntu machine the data gets inserted into the Mongo Database. But when i try to execute the SDk on Intel Edison board it gives me Can't get CONNACK+KAASYNC message. I have followed all the rules for installing the Kaa Server.
the logs links are
https://drive.google.com/open?id=0Bx5TGFxgyDWbSkZUVVUzbkhqSTA
https://drive.google.com/open?id=0Bx5TGFxgyDWbalNBZkZBMmRtajQ
Have you opened up the ports used by Kaa. If not Check "Firewall rules configuration" in this installation guide "http://docs.kaaproject.org/display/KAA/Installation+guide"
I think earlier, your app sdk and the kaa server must be on the same machine and hence you faced no issue. Now since intel edison needs to communicate with your kaa host as an external device, you need to configure your kaa host admin and also your log appenders with the external IP address of your kaa host. Pls refer to a similar issue mentioned in this question
It looks like you need to re-configure the Kaa instance for the correct 'Kaa host' setting, then regenerate the Kaa SDK and rebuild your application for Intel Edison board with that new SDK.
The 'Kaa host' should match the IP address of the host the kaa-node
instance is running on and be accessible from the application side by that
IP address. This configuration must be done before the SDK for the
application is generated as the bootstrap IP addresses are embedded into
the SDK.
Please check your node network configuration and re-generate the SDK for
the application.
Is it possible to run the Mosquitto Broker on any shared server? The closest solution I got to is this here, it only tells how to configure it, but I can't figure out how to install it on my server without ssh.
Another possible solution for my problem will be to use hosted brokers like CloudMQTT. I don't like it's plans and pricing, are there any other alternatives to this?
If you don't have console (SSH) access to the machine to install and run software it is going to be very difficult to add a broker without help from the administrator.
If you do mean a virtual host on a shared web server, then this is unlikely to happen as there is no concept of virtual hosts for MQTT so each user would have to be given their own port number (may be 2 if you want MQTT over websockets)