实现 pyejabberd 消息系统时的配置相关问题

Posted 2023-03-15

【中文标题】实现 pyejabberd 消息系统时的配置相关问题

【英文标题】：Configuration related issue while implementing pyejabberd message system

【发布时间】：2022-01-22 01:52:23

【问题描述】：

我正在我的 python 应用程序中实现一个消息系统，为了实现这一点，我使用了 ejabberd 的客户端库 pyejabberd。我已经检查了这个的官方文档来配置 ejabberd.yml 文件，但得到了一些错误。这是 BadStatusLine("") 错误。 IDK 为什么这会获取我的 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.
###

hosts:
  - localhost

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

certfiles:
  - /home/ejabberd/conf/server.pem

ca_file: "/home/ejabberd/conf/cacert.pem"

## When using let's encrypt to generate certificates
##certfiles:
##  - /etc/letsencrypt/live/localhost/fullchain.pem
##  - /etc/letsencrypt/live/localhost/privkey.pem
##
##ca_file: "/etc/letsencrypt/live/localhost/fullchain.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:
      # /: ejabberd_web_admin
      /: mod_http_api
      "/bosh": mod_bosh
      "/captcha": ejabberd_captcha
      "/upload": mod_http_upload
      "/ws": ejabberd_http_ws
      "/oauth": ejabberd_oauth
    web_admin: true
    http_bind: true
    captcha: false
  -
    port: 5180
    ip: "::"
    module: ejabberd_http
    request_handlers:
      /: ejabberd_web_admin
  -
    port: 1883
    ip: "::"
    module: mod_mqtt
    backlog: 1000
  ##
  ## https://docs.ejabberd.im/admin/configuration/#stun-and-turn
  ## ejabberd_stun: Handles STUN Binding requests
  ##
  ##-
  ##  port: 3478
  ##  ip: "0.0.0.0"
  ##  transport: udp
  ##  module: ejabberd_stun
  ##  use_turn: true
  ##  turn_ip: " IP "
  ##  auth_type: user
  ##  auth_realm: "example.com"
  ##-
  ##  port: 3478
  ##  ip: "0.0.0.0"
  ##  module: ejabberd_stun
  ##  use_turn: true
  ##  turn_ip: " IP "
  ##  auth_type: user
  ##  auth_realm: "example.com"
  ##- 
  ##  port: 5349
  ##  ip: "0.0.0.0"
  ##  module: ejabberd_stun
  ##  certfile: "/home/ejabberd/conf/server.pem"
  ##  tls: true
  ##  use_turn: true
  ##  turn_ip: " IP "
  ##  auth_type: user
  ##  auth_realm: "example.com"
  ##
  ## https://docs.ejabberd.im/admin/configuration/#sip
  ## To handle SIP (VOIP) requests:
  ##
  ##-
  ##  port: 5060
  ##  ip: "0.0.0.0"
  ##  transport: udp
  ##  module: ejabberd_sip
  ##-
  ##  port: 5060
  ##  ip: "0.0.0.0"
  ##  module: ejabberd_sip
  ##-
  ##  port: 5061
  ##  ip: "0.0.0.0"
  ##  module: ejabberd_sip
  ##  tls: true

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:
      - "admin@localhost"

access_rules:
  local:
    allow: local
  c2s:
    deny: blocked
    allow: all
  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: all
  c2s_shaper:
    none: admin
    normal: all
  s2s_shaper: fast

max_fsm_queue: 10000

acme:
   contact: "mailto:[e-mail]"
   ca_url: "https://acme-staging-v02.api.letsencrypt.org/directory"

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: never
  mod_mqtt: 
  mod_muc:
    access:
      - allow
    access_admin:
      - allow: admin
    access_create: muc_create
    access_persistent: muc_create
    access_mam:
      - allow
    default_room_options:
      allow_subscription: true  # enable MucSub
      mam: false
  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_sip: 
  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:
### vim: set filetype=yaml tabstop=8

我在这里做错了还是我的配置有误？你能建议我解决这个问题的方法吗？

我的python脚本代码：

from pyejabberd import EjabberdAPIClient
import http
import logging
import json

# Create a client and authenticate with elevated user '[e-mail]'
client = EjabberdAPIClient(host='127.0.0.1', port=5443, username='admin@localhost', password='yatish@1234', user_domain='example.com',
                           protocol='http')
try:
    client.echo(json.dumps("test":"sentence"))
except http.client.BadStatusLine as e:
    # import pdb
    # pdb.set_trace()
    print(">>>>>>>>",e)

当我调用 client.echo 方法时，它会遇到异常并引发错误。

【参考方案1】：

免责声明：我从未使用过 pyejabberd，所以我只是给你一些想法来调查。

我看到您的客户端尝试使用 HTTP 协议连接到端口 5443。查看您的 ejabberd 配置，它启用了 TLS ......所以也许它应该是 HTTPS？或者您可以尝试在 ejabberd 中设置“tls: false”。

另外，pyejabberd是用什么样的连接方式连接ejabberd的呢？ XMPP（端口 5222），或 XMPP over BOSH（端口 5443），或 XMPP over WebSocket（端口 5443，但 URL 路径不同）。

也许你应该在 pyejabberd 中设置端口 5222 和协议 xmpp，或者类似的东西。

如果收到连接尝试，请检查 ejabberd 日志文件。尝试使用著名的 XMPP 客户端登录，以便了解它在 ejabberd 日志文件中的外观（登录成功时显示的消息），并将其与您的客户端进行比较。