Update item configuration

Typically you will see only one item for vhost-man, but some additional components (ie. ext) may provided them as well. They each have their own sections, but provide for a plethora of server options. Changes to the server are done in real time, and may not be permanent.


You will be presented with a list of domains that Tigase is currently hosting, you will be able to change settings for one domain at a time using this function. Once a domain is selected, you will be able to set or change the following settings:

  • Domain name: the full domain name of the new vhost. Tigase will not add anything to this domain, so if it is ti be a subdomain of example.com, you will need to enter sub.domain.com.
  • Enabled: Whether the domain is turned on or off.
  • Anonymous enabled: Allow anonymous logins.
  • In-band registration: Whether or not to allow users to register accounts upon login.
  • TLS required: Require logins to the vhost to conduct a TLS handshake before opening streams.
  • S2S secret: a server-generated code to differentiate traffic between servers, typically there is no need to enter your own, but you may if you need to get into low level code.
  • Domain filter policy: Sets the filter policy for this domain, see This section for a description of the rules.
  • Domain filter domains: a specific setting to restrict or control cross domain traffic.
  • Max users: maximum users allowed to be registered to the server.
  • Allowed C2S, BOSH, Websocket ports: Comma separated list of ports that this vhost will check for all of these services.
  • Presence forward address: specific address where presence information is forwarded too. This may be handy if you are looking to use a single domain for presence processing and handling.
  • Message forward address: Specific address where all messages will be sent too. This may be useful to you if you have a single server handling AMP or message storage and want to keep the load there.
  • Other Parameters: Other settings you may wish to pass to the server, consider this a section for options after a command.
  • Owner: The owner of the vhost who will also be considered an administrator.
  • Administrators: comma separated list of JIDs who will be considered admins for the vhost.
  • XEP-0136 Message Archiving Enabled: Whether to turn on or off this feature.
  • XEP-0136 Required store method: If XEP-0136 is turned on, you may restrict the portion of message that is saved. This is required for any archiving, if null, any portion of the message may be stored.
  • Client certificate required: Whether the client should submit a certificate to login.
  • Client certificate CA: Client Certificate Authority.
  • XEP-0136 retention period: Integer of number of days message archives will be set.
  • Trusted JIDs: Comma separated list of JIDs who will be added to the trusted list, these are JIDS that may conduct commands, edit settings, or other secure work without needed secure logins.
  • XEP-0136 retention type: Sets the type of data that retention period will use. May be User defined (custom number type), Unlimited, or Number of Days.
  • XEP-0136 - store MUC messages: Whether or not to store MUC messages for archiving. Default is user, which allows users to individually set this setting, otherwise true/false will override.
  • see-other-host redirection enabled: in servers that have multiple clusters, this feature will help to automatically repopulate the cluster list if one goes down, however if this is unchecked, that list will not change and may attempt to send traffic to a down server.
  • XEP-0136 Default store method: The default section of messages that will be stored in the archive.