Hi Daniele,
Starting Nmap 6.47 ( http://nmap.org ) at 2017-05-03 16:58 UTC
Nmap scan report for localhost (127.0.0.1)
Host is up (0.0000050s latency).
Other addresses for localhost (not scanned): 127.0.0.1
Not shown: 995 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
111/tcp open rpcbind
3306/tcp open mysql
5269/tcp open xmpp-server
haven’t 5222 xmpp-client
I’m sorry @DeepChao what exactly are you talking about? Also please open a new topic to request support, thank you.
Dear daniele_athome,
05-04 09:15:02.105 18343-19399/? E/NumberValidation: validation error.
org.jivesoftware.smack.SmackException$ConnectionException: The following addresses failed: ‘192.168.10.104:5222’ failed because java.net.ConnectException: failed to connect to /192.168.10.104 (port 5222) after 30000ms: isConnected failed: ECONNREFUSED (Connection refused)
at org.kontalk.client.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:612)
at org.kontalk.client.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:850)
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:364)
at org.kontalk.service.XMPPConnectionHelper.connectOnce(XMPPConnectionHelper.java:195)
at org.kontalk.service.XMPPConnectionHelper.connectOnce(XMPPConnectionHelper.java:144)
at org.kontalk.client.NumberValidator.initConnection(NumberValidator.java:545)
at org.kontalk.client.NumberValidator.run(NumberValidator.java:256)
at java.lang.Thread.run(Thread.java:833)
Could you please help me know where i am doing wrong as per the above info.
thank you.
Dear daniele_athome
i Start up
root@debian:~/tigase-kontalk# scripts/tigase.sh start etc/tigase.conf
Starting Tigase:
Tigase running pid=7461
this is my init.properties,and i change
–s2s-ports=5269,5222,5999,8443
# Default Kontalk configuration, fine for most configurations
# XMPP host where you're serving your Kontalk instance
# Kontalk extensions support one virtual host only for now
sess-man/plugins-conf/urn\:ietf\:params\:xml\:ns\:xmpp-sasl/host=prime.kontalk.net
# Virtual hosts served by this instance (must match the above)
--virt-hosts=prime.kontalk.net
# Administrator JID (must be in the above domain)
--admins=admin@prime.kontalk.net
# Fingerprint of the GPG server key
sess-man/plugins-conf/fingerprint=FC863FD915B73C928281415BE93F81069436D92B
# The global network domain (do not change this if you want to participate in the Kontalk global network)
sess-man/plugins-conf/network-domain=kontalk.net
# Database configuration (the two db-uri parameters must be identical)
--user-db=mysql
--user-db-uri=jdbc:mysql://127.0.0.1:3306/tigase?user=root&password=toor&useUnicode=true&characterEncoding=UTF-8&useSSL=false&serverTimezone=UTC
sess-man/plugins-conf/db-uri=jdbc:mysql://127.0.0.1:3306/tigase?user=root&password=toor&useUnicode=true&characterEncoding=UTF-8&useSSL=false&serverTimezone=UTC
# Registration provider configuration
# Android emulator registration provider: it will emulate an SMS with the verification code
#sess-man/plugins-conf/kontalk\:jabber\:iq\:register/providers[s]=android=org.kontalk.xmppserver.registration.AndroidEmulatorProvider
# how many seconds to wait before a user can retry registration
#sess-man/plugins-conf/kontalk\:jabber\:iq\:register/android-expire[I]=900
# the sender number of the emulated SMS
#sess-man/plugins-conf/kontalk\:jabber\:iq\:register/android-sender=12345
# the device ID of the emulator to send the SMS to
#sess-man/plugins-conf/kontalk\:jabber\:iq\:register/android-device=emulator-5554
# Dummy provider configuration
# It will always accept 123456 as a valid verification code
# Good for a remote test server
sess-man/plugins-conf/kontalk\:jabber\:iq\:register/providers[s]=dummy=org.kontalk.xmppserver.registration.DummyProvider
sess-man/plugins-conf/kontalk\:jabber\:iq\:register/dummy-sender=123456
# Endpoints configuration
# All endpoints must declare a clientCertCA pointing to a valid certificate chain file
# (any CA chain will do, it won't actually be used but Tigase won't work without it)
# Client endpoint configuration
--c2s-ports=5999,5222,5223,8443
c2s/connections/5223/socket=ssl
c2s/connections/8443/socket=ssl
c2s/clientCertCA=trusted.pem
# Websocket endpoint configuration
message-router/components/msg-receivers/ws2s.active[B]=false
ws2s/connections/5290/socket=ssl
ws2s/clientCertCA=trusted.pem
# BOSH endpoint configuration
message-router/components/msg-receivers/bosh.active[B]=false
bosh/connections/5280/socket=ssl
bosh/clientCertCA=trusted.pem
# S2S endpoint configuration (comment to disable XMPP federation)
--s2s-ports=5269,5222,5999,8443
# Enabled plugins, comma-separated
# prefixed with a minus (-) means not loaded, prefixed with nothing or with a plus (+) means loaded.
# add "+kontalk:push:legacy" to enable Kontalk push notifications (external component must also be configured below)
--sm-plugins=-amp,-message-carbons,-jabber:iq:auth,-jabber:iq:register,-jabber:iq:privacy,-jabber:iq:last,-msgoffline,-urn:xmpp:blocking,-urn:xmpp:csi:0,+message,+msgoffline2,+presence:urn:xmpp:pubkey:2,+kontalk:jabber:iq:register,+kontalk:jabber:iq:roster,+urn:xmpp:pubkey:2,+kontalk:urn:xmpp:blocking,+kontalk:urn:xmpp:csi:0,+kontalk:jabber:iq:last
# Comment these to revert to default logging
--debug=server,xmpp.impl
--debug-packages=org.kontalk
# External components. Do not change the default names!
# --comp-xxx parameter pairs follow a numbering order
# whenever you delete/comment or insert a component, remember to fix the numbering!!
# Network component
# enables server list commands. Particularly needed if participating in a global network
--comp-name-1=network
--comp-class-1=org.kontalk.xmppserver.NetworkComponent
# Phone number lookup component
# enables discovery of contacts in the local/global network by their phone numbers
--comp-name-2=probe
--comp-class-2=org.kontalk.xmppserver.probe.ProbeComponent
# External XMPP component protocol
# needed for HttpFileUploadComponent
--comp-name-3=ext
--comp-class-3=tigase.server.ext.ComponentProtocol
# these must match HttpFileUploadComponent configuration
--external=media.prime.kontalk.net:secret:listen:5270
--comp-name-4=multicast
--comp-class-4=org.kontalk.xmppserver.ExtendedAddressing
# GCM push notifications
# remember to fix --sm-plugins too (see above)
#--comp-name-5=push
#--comp-class-5=org.kontalk.xmppserver.KontalkLegacyPushComponent
#push/gcm-projectid=PROJECT-ID
#push/gcm-apikey=API-KEY
# Internal parameters
# the following properties must not be changed unless you really know what you're doing
basic-conf/auth-repo-params/sasl-mechs=EXTERNAL
sess-man/plugins-conf/urn\:ietf\:params\:xml\:ns\:xmpp-sasl/factory=org.kontalk.xmppserver.auth.KontalkSaslServerFactory
sess-man/plugins-conf/urn\:ietf\:params\:xml\:ns\:xmpp-sasl/mechanism-selector=org.kontalk.xmppserver.auth.KontalkMechanismSelector
sess-man/plugins-conf/urn\:ietf\:params\:xml\:ns\:xmpp-sasl/callbackhandler-EXTERNAL=org.kontalk.xmppserver.auth.KontalkCertificateCallbackHandler
sess-man/plugins-conf/presence-state/extended-presence-processors=org.kontalk.xmppserver.presence.PublicKeyPresence
c2s/processors[s]=urn:xmpp:sm:3=org.kontalk.xmppserver.KontalkIOProcessor
message-router/components/msg-receivers/amp.active[B]=false
--vhost-anonymous-enabled=false
--vhost-tls-required=false
--hardened-mode=true
config-type=--gen-config-def
this is android studio
05-04 17:56:43.160 24557-25784/org.kontalk.debug E/NumberValidation: validation error.
org.jivesoftware.smack.SmackException$NoResponseException: No response received within reply timeout. Timeout was 15000ms (~15s). Used filter: No filter used or filter was 'null'.
at org.jivesoftware.smack.SynchronizationPoint.checkForResponse(SynchronizationPoint.java:253)
at org.jivesoftware.smack.SynchronizationPoint.checkIfSuccessOrWait(SynchronizationPoint.java:146)
at org.jivesoftware.smack.SynchronizationPoint.checkIfSuccessOrWaitOrThrow(SynchronizationPoint.java:125)
at org.kontalk.client.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:857)
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:364)
at org.kontalk.service.XMPPConnectionHelper.connectOnce(XMPPConnectionHelper.java:195)
at org.kontalk.service.XMPPConnectionHelper.connectOnce(XMPPConnectionHelper.java:144)
at org.kontalk.client.NumberValidator.initConnection(NumberValidator.java:545)
at org.kontalk.client.NumberValidator.run(NumberValidator.java:256)
at java.lang.Thread.run(Thread.java:833)
05-04 17:56:43.210 24557-24557/org.kontalk.debug W/NumberValidator: shutting down
05-04 17:56:43.210 24557-24557/org.kontalk.debug W/NumberValidator: exiting
Thanks very much
Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.
2017-05-04 17:40:08.592 [main] VHostManager.setProperties() WARNING: {prime.kontalk.net=Domain: prime.kontalk.net, enabled: true, anonym: false, register: true, maxusers: 0, tls: false, s2sSecret: b04bfc63-9b84-45f1-8108-3aad0dc7b37a, domainFilter: ALL, domainFilterDomains: null, c2sPortsAllowed: null, saslAllowedMechanisms: null}
2017-05-04 17:40:08.636 [main] ClientTrustManagerFactory.loadTrustedCert() WARNING: Can't create TrustManager with certificate from file.
java.io.FileNotFoundException: trusted.pem (没有那个文件或目录)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at java.io.FileReader.<init>(FileReader.java:72)
at tigase.cert.CertificateUtil.loadCertificate(CertificateUtil.java:402)
at tigase.cert.CertificateUtil.loadCertificate(CertificateUtil.java:426)
at tigase.server.xmppclient.ClientTrustManagerFactory.loadTrustedCert(ClientTrustManagerFactory.java:109)
at tigase.server.xmppclient.ClientTrustManagerFactory.setProperties(ClientTrustManagerFactory.java:145)
at tigase.server.xmppclient.ClientConnectionManager.setProperties(ClientConnectionManager.java:889)
at tigase.conf.ConfiguratorAbstract.itemUpdated(ConfiguratorAbstract.java:291)
at tigase.conf.ConfiguratorAbstract.itemUpdated(ConfiguratorAbstract.java:59)
at tigase.conf.ConfigurationCache.addItem(ConfigurationCache.java:119)
at tigase.conf.ConfigurationCache.putProperties(ConfigurationCache.java:349)
at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:509)
at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152)
at tigase.conf.Configurator.componentAdded(Configurator.java:50)
at tigase.conf.Configurator.componentAdded(Configurator.java:33)
at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116)
at tigase.server.MessageRouter.addComponent(MessageRouter.java:115)
at tigase.server.MessageRouter.addRouter(MessageRouter.java:152)
at tigase.server.MessageRouter.setProperties(MessageRouter.java:745)
at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519)
at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152)
at tigase.conf.Configurator.componentAdded(Configurator.java:50)
at tigase.conf.Configurator.componentAdded(Configurator.java:33)
at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116)
at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138)
at tigase.server.MessageRouter.setConfig(MessageRouter.java:644)
at tigase.server.XMPPServer.start(XMPPServer.java:142)
at tigase.server.XMPPServer.main(XMPPServer.java:112)
java.lang.RuntimeException: java.io.FileNotFoundException: trusted.pem (没有那个文件或目录)
at tigase.server.xmppclient.ClientTrustManagerFactory.loadTrustedCert(ClientTrustManagerFactory.java:136)
at tigase.server.xmppclient.ClientTrustManagerFactory.setProperties(ClientTrustManagerFactory.java:145)
at tigase.server.xmppclient.ClientConnectionManager.setProperties(ClientConnectionManager.java:889)
at tigase.conf.ConfiguratorAbstract.itemUpdated(ConfiguratorAbstract.java:291)
at tigase.conf.ConfiguratorAbstract.itemUpdated(ConfiguratorAbstract.java:59)
at tigase.conf.ConfigurationCache.addItem(ConfigurationCache.java:119)
at tigase.conf.ConfigurationCache.putProperties(ConfigurationCache.java:349)
at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:509)
at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152)
at tigase.conf.Configurator.componentAdded(Configurator.java:50)
at tigase.conf.Configurator.componentAdded(Configurator.java:33)
at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116)
at tigase.server.MessageRouter.addComponent(MessageRouter.java:115)
at tigase.server.MessageRouter.addRouter(MessageRouter.java:152)
at tigase.server.MessageRouter.setProperties(MessageRouter.java:745)
at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519)
at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152)
at tigase.conf.Configurator.componentAdded(Configurator.java:50)
at tigase.conf.Configurator.componentAdded(Configurator.java:33)
at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116)
at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138)
at tigase.server.MessageRouter.setConfig(MessageRouter.java:644)
at tigase.server.XMPPServer.start(XMPPServer.java:142)
at tigase.server.XMPPServer.main(XMPPServer.java:112)
Caused by: java.io.FileNotFoundException: trusted.pem (没有那个文件或目录)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at java.io.FileReader.<init>(FileReader.java:72)
at tigase.cert.CertificateUtil.loadCertificate(CertificateUtil.java:402)
at tigase.cert.CertificateUtil.loadCertificate(CertificateUtil.java:426)
at tigase.server.xmppclient.ClientTrustManagerFactory.loadTrustedCert(ClientTrustManagerFactory.java:109)
... 23 more
Loading component: eventbus :: componentInfo{Title=Tigase XMPP Server, Version=7.1.0-b59/48c47302 (2017-05-04/10:07:03), Class=tigase.disteventbus.component.EventBusComponent}
2017-05-04 17:40:08.667 [main] ConnectionManager.setProperties() WARNING: ext last_minute_packets_limit = 26214400
2017-05-04 17:40:08.667 [main] ConnectionManager.setProperties() WARNING: ext total_packets_limit = 0
2017-05-04 17:40:08.668 [main] ConnectionManager.setProperties() WARNING: ext last_minute_bin_limit = 20971520000
2017-05-04 17:40:08.668 [main] ConnectionManager.setProperties() WARNING: ext total_bin_limit = 0
Loading component: ext :: componentInfo{Title=Tigase XMPP Server, Version=7.1.0-b59/48c47302 (2017-05-04/10:07:03), Class=tigase.server.ext.ComponentProtocol}
2017-05-04 17:40:08.796 [main] ConfigRepository.setProperties() WARNING: Items list is not set in the configuration file!!
2017-05-04 17:40:08.856 [main] MonitorComponent.setProperties() WARNING: Monitoring Tasks: {} with items: {}
Loading component: monitor :: componentInfo{Title=Tigase XMPP Server, Version=7.1.0-b59/48c47302 (2017-05-04/10:07:03), Class=tigase.monitor.MonitorComponent}
Loading component: multicast :: componentInfo{Class=org.kontalk.xmppserver.ExtendedAddressing}
Loading component: network :: componentInfo{Class=org.kontalk.xmppserver.NetworkComponent}
Loading component: probe :: componentInfo{Class=org.kontalk.xmppserver.probe.ProbeComponent}
2017-05-04 17:40:09.081 [main] ConnectionManager.setProperties() WARNING: s2s last_minute_packets_limit = 15360
2017-05-04 17:40:09.081 [main] ConnectionManager.setProperties() WARNING: s2s total_packets_limit = 0
2017-05-04 17:40:09.081 [main] ConnectionManager.setProperties() WARNING: s2s last_minute_bin_limit = 125829120
2017-05-04 17:40:09.081 [main] ConnectionManager.setProperties() WARNING: s2s total_bin_limit = 0
Loading component: s2s :: componentInfo{Title=Tigase XMPP Server, Version=7.1.0-b59/48c47302 (2017-05-04/10:07:03), Class=tigase.server.xmppserver.S2SConnectionManager}
2017-05-04 17:40:09.265 [main] DNSResolver.<clinit>() WARNING: Resolving default host name: debian took: 1
Loading plugin: session-close=16:291 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: session-open=8:582 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: default-handler=16:291 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: urn:ietf:params:xml:ns:xmpp-sasl=16:291 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: urn:ietf:params:xml:ns:xmpp-bind=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: urn:ietf:params:xml:ns:xmpp-session=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: jabber:iq:roster=16:291 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: jabber:iq:version=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: http://jabber.org/protocol/stats=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: starttls=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: vcard-temp=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: http://jabber.org/protocol/commands=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: jabber:iq:private=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: urn:xmpp:ping=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: presence-state=16:291 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: presence-subscription=16:291 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: disco=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: zlib=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: vcard-xep-0292=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: urn:xmpp:time=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: message=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: msgoffline2=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: kontalk:jabber:iq:register=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: kontalk:jabber:iq:roster=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: urn:xmpp:pubkey:2=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: kontalk:urn:xmpp:blocking=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: kontalk:urn:xmpp:csi:0=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading plugin: kontalk:jabber:iq:last=4:1165 ... , version: 7.1.0-b59/48c47302 (2017-05-04/10:07:03)
Loading component: sess-man :: componentInfo{Title=Tigase XMPP Server, Version=7.1.0-b59/48c47302 (2017-05-04/10:07:03), Class=tigase.server.xmppsession.SessionManager}
2017-05-04 17:40:10.147 [main] ConfigurationCache.store() WARNING: Dumping server configuration to: etc/config-dump.properties
== Thu May 04 17:40:10 UTC 2017 Server finished starting up and (if there wasn't any error) is ready to use
2017-05-04 17:55:58.366 [ConnectionOpenThread] SocketThread.<clinit>() WARNING: 17 socketReadThreads started.
2017-05-04 17:55:58.370 [ConnectionOpenThread] SocketThread.<clinit>() WARNING: 17 socketWriteThreads started.These are the ports for server-to-server connections. You’re using the same ports in client-to-server too, this can’t work. Decide which ports to use for one and what ports to use for the other. Usually the default values are fine.
The log also notifies you of a missing trusted.pem file in tigase-kontalk. Please copy a certification authority you have (use your CA if you have one) into a PEM file named trusted.pem. It isn’t really used, it’s just to make Tigase work (WIP on that with the Tigase team).
A post was merged into an existing topic: Running Kontalk Server on Ubuntu - Warning connection is not validated
Hi @DeepChao Are you solving your problem ?
Not shown: 995 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
111/tcp open rpcbind
3306/tcp open mysql
5269/tcp open xmpp-server
haven’t 5222 xmpp-client
I have the same one , can any help
@daniele_athome Hi, I followed all instructions to build kontalk server , so how can i verify the server is running well?
thanks in advance.
Hello @jedo,
things have changed a bit in the last couple of months. We switched to Docker.
I don’t know if you followed that or you did a manual installation.
@daniele_athome Thanks for replay , I have followed a manual instalation in github
what i must do in this case?
Manual installation is no longer supported. It depends on too many variables and it’s hard to figure out problems because it’s very dependant on your system configuration. Please switch to the Docker environment where we can help you out. It is very easy, if you didn’t register any user accounts there isn’t even need to migrate the database. It takes a few seconds to configure and a few minutes to build and start.
Let me know how it goes, we’ll improve our documentation on the Docker environment based on your feedback, if needed.
@daniele_athome Hi , How can i verify kontalk server is running correctly and is ready to connect with the client.
Building the image can take some time. You can watch details about the build by activating the debug mode (so we can inspect any issue easily):
DEBUG=1 ./launcher bootstrap
@daniele_athome Hi , How can i verify kontalk server is running correctly and is ready to connect with the client.
I guess you passed that previous issue about building the image.
You can launch:
./launcher logs
to view logs for all 3 containers. If everything is fine you should be able to try a registration via the Kontalk app by make it connect to your server (Kontalk settings > Manual server address). Alternatively (but it’s not a comprehensive test) you may connect to port 5222 of your server and talk to the server by using XMPP directly.