Re bonjour
Aptrés avoir discuté sur le tchat de jappix, j’ai finalement décidé de laisser tomber openfire pour installer prosody en me servant du tuto suivant: jeyg.info/un-serveur-xmpp-pe … 5-minutes/
Mais la j’ai des problemes de disponibilité de mon serveur
voila ma configuration actuelle
/etc/prosody/prosody.cfg.lua
-- Prosody Example Configuration File
--
-- Information on configuring Prosody can be found on our
-- website at http://prosody.im/doc/configure
--
-- Tip: You can check that the syntax of this file is correct
-- when you have finished by running: luac -p prosody.cfg.lua
-- If there are any errors, it will let you know what and where
-- they are, otherwise it will keep quiet.
--
-- The only thing left to do is rename this file to remove the .dist ending, and fill in the
-- blanks. Good luck, and happy Jabbering!
---------- Server-wide settings ----------
-- Settings in this section apply to the whole server and are the default settings
-- for any virtual hosts
-- This is a (by default, empty) list of accounts that are admins
-- for the server. Note that you must create the accounts separately
-- (see http://prosody.im/doc/creating_accounts for info)
-- Example: admins = { "user1@example.com", "user2@example.net" }
admins = { }
-- Enable use of libevent for better performance under high load
-- For more information see: http://prosody.im/doc/libevent
--use_libevent = true;
-- This is the list of modules Prosody will load on startup.
-- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
-- Documentation on modules can be found at: http://prosody.im/doc/modules
modules_enabled = {
-- Generally required
"roster"; -- Allow users to have a roster. Recommended ;)
"saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.
"tls"; -- Add support for secure TLS on c2s/s2s connections
"dialback"; -- s2s dialback support
"disco"; -- Service discovery
-- Not essential, but recommended
"private"; -- Private XML storage (for room bookmarks, etc.)
"vcard"; -- Allow users to set vCards
--"privacy"; -- Support privacy lists
--"compression"; -- Stream compression
-- Nice to have
"legacyauth"; -- Legacy authentication. Only used by some old clients and bots.
"version"; -- Replies to server version requests
"uptime"; -- Report how long server has been running
"time"; -- Let others know the time here on this server
"ping"; -- Replies to XMPP pings with pongs
"pep"; -- Enables users to publish their mood, activity, playing music and more
"register"; -- Allow users to register on this server using a client and change passwords
-- Other specific functionality
--"console"; -- Opens admin telnet interface on localhost port 5582
"bosh"; -- Enable BOSH clients, aka "Jabber over HTTP"
"httpserver"; -- Serve static files from a directory over HTTP
"groups"; -- Shared roster support
"announce"; -- Send announcement to all online users
"welcome"; -- Welcome users who register accounts
--"watchregistrations"; -- Alert admins of registrations
-- Debian: do not remove this module, or you lose syslog
-- support
"posix"; -- POSIX functionality, sends server to background, enables syslog, etc.
};
-- These modules are auto-loaded, should you
-- for (for some mad reason) want to disable
-- them then uncomment them below
modules_disabled = {
-- "presence";
-- "message";
-- "iq";
};
-- Disable account creation by default, for security
-- For more information see http://prosody.im/doc/creating_accounts
allow_registration = true;
-- Debian:
-- send the server to background.
--
daemonize = true;
-- Debian:
-- Please, don't change this option since /var/run/prosody/
-- is one of the few directories Prosody is allowed to write to
--
pidfile = "/var/run/prosody/prosody.pid";
-- These are the SSL/TLS-related settings. If you don't want
-- to use SSL/TLS, you may comment or remove this
ssl = {
key = "/etc/prosody/certs/localhost.key";
certificate = "/etc/prosody/certs/localhost.cert";
}
-- Require encryption on client/server connections?
--c2s_require_encryption = false
--s2s_require_encryption = false
-- Logging configuration
-- For advanced logging see http://prosody.im/doc/logging
log = "prosody.log";
debug = false; -- Log debug messages?
-- Debian:
-- all to var/log
-- errors to syslog also
log = {
{ levels = { "error" }; to = "syslog"; };
{ levels = { "error" }; to = "file"; filename = "/var/log/prosody/prosody.err"; };
-- Change "info" to "debug" for more verbose logging
{ levels = { min = "info" }; to = "file"; filename = "/var/log/prosody/prosody.log"; };
}
-- Loads all configuration files in /etc/prosody/conf.d/ --
local ztact = require "util.ztact"
local cfgdir = "/etc/prosody/conf.d/"
for f in ztact.dir(cfgdir) do Include(cfgdir..f); end
-----------------------------------------------------------
/etc/prosody/conf.avail/blabla.dlinkddns.com.cfg.lua
[code]-- Section for example.com
VirtualHost "blabla.dlinkddns.com"
enabled = true
-- Assign this host a certificate for TLS, otherwise it would use the one
-- set in the global section (if any).
-- Note that old-style SSL on port 5223 only supports one certificate, and will always
-- use the global one.
ssl = {
key = "/etc/prosody/certs/example.com.key";
certificate = "/etc/prosody/certs/example.com.crt";
}
------ Components ------
– You can specify components to add hosts that provide special services,
– like multi-user conferences, and transports.
– For more information on components, see http://prosody.im/doc/components
– Set up a MUC (multi-user chat) room server on conference.example.com:
Component “conference.example.com” “muc”
– Set up a SOCKS5 bytestream proxy for server-proxied file transfers:
–Component “proxy.example.com” “proxy65”
—Set up an external component (default component port is 5347)
–Component “gateway.example.com”
– component_secret = “password”
[/code]
/etc/prosody/conf.d/:
blabla.dlinkddns.com.cfg.lua -> …/conf.avail/blabla.dlinkddns.com.cfg.lua
localhost.cfg.lua -> …/conf.avail/localhost.cfg.lua
j’ai bien créé un user via: prosodyctl adduser myuser@blabla.dlinkddns.com
j’ai ajouté a /etc/bind/
_xmpp-client._tcp.blabla.dlinkddns.com 86400 IN SRV 20 0 5222 blabla.dlinkddns.com
_xmpp-server._tcp.blabla.dlinkddns.com 86400 IN SRV 20 0 5269 blabla.dlinkddns.com
Sur le routeur j’ai ouvert les ports 5269, 5222, 5280.
ensuite je me connecte a mon serveur via jappix sur l’adresse: blabla.dlinkddns.com/jappix/
j’ai bien accés au panneau d’accueil mais une fois le user et mdp entrée en choississant comme serveur @blabla.dlinkddns.com
Jappix me dit service indisponible 
ma configuration jappix
Hôte principal: blabla.dlinkddns.com
Hôte de salons: muc.blabla.dlinkddns.com
Hôte Pubsub: pubsub.blabla.dlinkddns.com
Hôte anonyme: anonymous.blabla.dlinkddns.com
Hôte d’annuaire: vjud.blabla.dlinkddns.com
hote bosh: localhost:5280/http-bind
La je ne vois pas du tout ou est le soucis
merci pour votre aide et désolé d’être un boulet
