无法与ejabberd和XMPP客户端Psi +进行一对一聊天

时间:2019-06-10 03:10:16

标签: ejabberd psi+

Mac OSX 10.13.6
ejabberd 19.05

我使用安装程序安装ejabberd,并在出现提示时输入以下信息:

ejabberd server domain: localhost
administrator username: 7stud
administrator password: blahblah

我正在学习本教程:How to Build One to One Chat App Using Ejabberd & Erlang from Scratch?

如果我通过单击start目录中的ejabberd-19.05/bin可执行文件来启动ejabberd,则ejabberd将启动,并在浏览器中打开一个网页。然后,我可以登录到管理Web界面。

但是,本教程指导我将以下内容添加到ejabberd.yml:

auth_method: sql
sql_type: mysql
sql_server: "localhost" 
sql_database: "chat" 
sql_username: "root" 
sql_password: "" 

(对于我的mysql设置,root用户没有密码-我只是在提示输入密码时按回车键)

这样做之后,如果我停止ejabberd,然后再次启动ejabberd,我将无法再登录到管理页面。

我有两个问题:

  1. 为什么将数据库配置添加到ejabberd.yml会阻止我登录到管理Web界面?

  2. 为什么还要配置mysql db?根据{{​​3}}:ejabberd default backend is Mnesia internal database。我非常乐于使用健忘症(不必触摸ejabberd.yml)。

我用ejabberd.yml中的mysql db config东西完成了本教程的其余部分,但没有,但是User1和User2都没有收到其他用户发送的消息,因此由于某种原因,我的ejabberd设置无法正常工作。我还尝试通过遵循ejabberd docs来配置另一个mysql数据库:

auth_method: sql
sql_type: mysql
sql_server: "localhost"
sql_database: "ejabberd"
sql_username: "ejabberd"
sql_password: "12345"

仍然没有运气。

如果有人可以推荐,我愿意尝试使用ejabberd中继消息的其他任何简单教程。

管理Web界面

ejabberd database docs


enter image description here


enter image description here


enter image description here


enter image description here

psi +张图片:

enter image description here

enter image description here

enter image description here ejabberd.yml:

###
###'           ejabberd configuration file
###
### The parameters used in this configuration file are explained at
###
###       https://docs.ejabberd.im/admin/configuration
###
### The configuration file is written in YAML.
### *******************************************************
### *******           !!! WARNING !!!               *******
### *******     YAML IS INDENTATION SENSITIVE       *******
### ******* MAKE SURE YOU INDENT SECTIONS CORRECTLY *******
### *******************************************************
### Refer to http://en.wikipedia.org/wiki/YAML for the brief description.
### However, ejabberd treats different literals as different types:
###
### - unquoted or single-quoted strings. They are called "atoms".
###   Example: dog, 'Jupiter', '3.14159', YELLOW
###
### - numeric literals. Example: 3, -45.0, .0
###
### - quoted or folded strings.
###   Examples of quoted string: "Lizzard", "orange".
###   Example of folded string:
###   > Art thou not Romeo,
###     and a Montague?
###


language: "en"
hosts:
  - "localhost"

loglevel: 4
log_rotate_size: 10485760
log_rotate_date: ""
log_rotate_count: 1
log_rate_limit: 100

certfiles:
  - "/Applications/ejabberd-19.05/conf/server.pem"
##  - "/etc/letsencrypt/live/localhost/fullchain.pem"
##  - "/etc/letsencrypt/live/localhost/privkey.pem"

ca_file: "/Applications/ejabberd-19.05/conf/cacert.pem"

listen:
  -
    port: 5222
    ip: "::"
    module: ejabberd_c2s
    max_stanza_size: 262144
    shaper: c2s_shaper
    access: c2s
    starttls_required: true
  -
    port: 5269
    ip: "::"
    module: ejabberd_s2s_in
    max_stanza_size: 524288
  -
    port: 5443
    ip: "::"
    module: ejabberd_http
    tls: true
    request_handlers:
      "/admin": ejabberd_web_admin
      "/api": mod_http_api
      "/bosh": mod_bosh
      "/captcha": ejabberd_captcha
      "/upload": mod_http_upload
      "/ws": ejabberd_http_ws
      "/oauth": ejabberd_oauth
  -
    port: 5280
    ip: "::"
    module: ejabberd_http
    request_handlers:
      "/admin": ejabberd_web_admin
  -
    port: 1883
    ip: "::"
    module: mod_mqtt
    backlog: 1000

s2s_use_starttls: optional

acl:
  local:
    user_regexp: ""
  loopback:
    ip:
      - "127.0.0.0/8"
      - "::1/128"
      - "::FFFF:127.0.0.1/128"
  admin:
    user:
      - "7stud@localhost"

access_rules:
  local:
    - allow: local
  c2s:
    - deny: blocked
    - allow
  announce:
    - allow: admin
  configure:
    - allow: admin
  muc_create:
    - allow: local
  pubsub_createnode:
    - allow: local
  trusted_network:
    - allow: loopback

api_permissions:
  "console commands":
    from:
      - ejabberd_ctl
    who: all
    what: "*"
  "admin access":
    who:
      - access:
          - allow:
            - acl: loopback
            - acl: admin
      - oauth:
        - scope: "ejabberd:admin"
        - access:
          - allow:
            - acl: loopback
            - acl: admin
    what:
      - "*"
      - "!stop"
      - "!start"
  "public commands":
    who:
      - ip: "127.0.0.1/8"
    what:
      - "status"
      - "connected_users_number"

shaper:
  normal: 1000
  fast: 50000

shaper_rules:
  max_user_sessions: 10
  max_user_offline_messages:
    - 5000: admin
    - 100
  c2s_shaper:
    - none: admin
    - normal
  s2s_shaper: fast

max_fsm_queue: 10000

acme:
   contact: "mailto:7stud@localhost"
   ca_url: "https://acme-v01.api.letsencrypt.org"

modules:
  mod_adhoc: {}
  mod_admin_extra: {}
  mod_announce:
    access: announce
  mod_avatar: {}
  mod_blocking: {}
  mod_bosh: {}
  mod_caps: {}
  mod_carboncopy: {}
  mod_client_state: {}
  mod_configure: {}
  mod_disco: {}
  mod_fail2ban: {}
  mod_http_api: {}
  mod_http_upload:
    put_url: "https://@HOST@:5443/upload"
  mod_last: {}
  ## mod_mam:
    ## Mnesia is limited to 2GB, better to use an SQL backend
    ## For small servers SQLite is a good fit and is very easy
    ## to configure. Uncomment this when you have SQL configured:
    ## db_type: sql
    ## assume_mam_usage: true
    ## default: always
  mod_mqtt: {}
  mod_muc:
    access:
      - allow
    access_admin:
      - allow: admin
    access_create: muc_create
    access_persistent: muc_create
    default_room_options:
      allow_subscription: true  # enable MucSub
      ## mam: true
  mod_muc_admin: {}
  mod_offline:
    access_max_user_messages: max_user_offline_messages
  mod_ping: {}
  mod_privacy: {}
  mod_private: {}
  mod_proxy65:
    access: local
    max_connections: 5
  mod_pubsub:
    access_createnode: pubsub_createnode
    plugins:
      - "flat"
      - "pep"
    force_node_config:
      ## Avoid buggy clients to make their bookmarks public
      "storage:bookmarks":
        access_model: whitelist
  mod_push: {}
  mod_push_keepalive: {}
  mod_register:
    ## Only accept registration requests from the "trusted"
    ## network (see access_rules section above).
    ## Think twice before enabling registration from any
    ## address. See the Jabber SPAM Manifesto for details:
    ## https://github.com/ge0rg/jabber-spam-fighting-manifesto
    ip_access: trusted_network
  mod_roster:
    versioning: true
  mod_s2s_dialback: {}
  mod_shared_roster: {}
  mod_stream_mgmt:
    resend_on_timeout: if_offline
  mod_vcard: {}
  mod_vcard_xupdate: {}
  mod_version:
    show_os: false

### Local Variables:
### mode: yaml
### End:

  [1]: https://www.apptha.com/blog/steps-to-build-a-private-one-to-one-chat-app/
  [2]: https://docs.ejabberd.im/admin/databases/mysql/

2 个答案:

答案 0 :(得分:3)

  

为什么将数据库配置添加到ejabberd.yml会阻止我登录到管理Web界面?

正如Pouriya所说,您首先在Mnesia数据库中创建了一个帐户。然后,您切换到该帐户不存在的MySQL数据库...因此,再次创建它,或使用 export2sql 将Mnesia内容导出到SQL文件并将其导入SQL数据库中。 / p>

  

为什么还要配置mysql db?根据ejabberd的文档:ejabberd的默认后端是Mnesia内部数据库。我非常乐于使用健忘症(不必触摸ejabberd.yml)。

内部Mnesia数据库足以容纳小型服务器(数百个并发用户)。如果您有一台小型服务器,那可能就足够了。但是,如果您计划使用大型服务器(成千上万的并发用户),则最好使用SQL数据库。现在有可能开始使用Mnesia几个月,一旦有很多用户,就可以将内容和配置切换到SQL。

答案 1 :(得分:1)

  

我需要在ebjabberd.yml中配置默认​​的Mnesia数据库吗?我该怎么办?

安装ejabberd,在配置文件中进行任何更改,然后使用Mnesia。

  

我实际上是否需要能够登录到管理Web界面才能使本教程正常工作?

“上班”是一个模棱两可的句子,所以我无法回答。

  

我在哪里创建帐户?在Mysql中?在埃贾伯德?

在ejabberd中,就像您存储在Mnesia中的第一个帐户一样。

  

我有两个用户想要在他们之间传递一条消息,即“ hi”。

对于两个用户...。只需安装ejabberd,在ejabberd中注册两个帐户即可。