#1298 Cross domain not working on 0.9

Reporter Stone
Owner Nobody
Created
Updated
Stars ★★ (2)
Tags
  • Priority-Medium
  • Type-Defect
  • Status-Invalid
  1. Stone on

    What steps will reproduce the problem? 1. Install Prosody 0.9 2. Enable bosh and set `cross_domain_bosh = true` 3. Try to use TURN server with Nextcloud XMPP at https://example.com:5281/http-bind (note: no SSL errors, that is configured correctly) What is the expected output? Nextcloud and other services should accept and use TURN server What do you see instead? Actual output from Nextcloud XMPP app: ``` BOSH server NOT reachable or misconfigured. Cross domain request was not possible. Either your BOSH server does not send any Access-Control-Allow-Origin header or the content-security-policy (CSP) blocks your request. Starting from Owncloud 9.0 your CSP will be updated in any app which uses the appframework (e.g. files) after you save these settings and reload.The savest way is still to use Apache ProxyRequest or Nginx proxy_pass. ``` What version of the product are you using? On what operating system? 0.9 Ubuntu 16.04 Please provide any additional information below. If the problem is that I must upgrade to .10 the docs should say this on this page: https://prosody.im/doc/setting_up_bosh

  2. Zash on

    Thanks for the report. Please verify that the setting cross_domain_bosh is in the global section of the config, above any VirtualHost or Component lines.

    Changes
    • tags Status-NeedInfo
  3. Stone on

    > lease verify that the setting cross_domain_bosh is in the global section of the config, above any VirtualHost or Component lines. There is no heading that says "global" in the file so I can't know if I am in a global section. Please tell me exactly where I should put the declaration and I will move it there and re-test. (However I did fix this problem with apache2 reverse proxy settings)

  4. Zash on

    https://hg.prosody.im/0.9/file/tip/prosody.cfg.lua.dist#l15 > above any VirtualHost or Component lines.

  5. Stone on

    > above any VirtualHost or Component lines. I put it at the top of the file and now it works. I thought that where it was was global because it was after the individual server.

  6. Zash on

    Good that it got resolved :)

    Changes
    • tags Status-Invalid
  7. Soulfire on

    Hey, I know that cross_domain_bosh is now the default, but I've also been getting this error. Is there something I need to add into my Apache config?

  8. Zash on

    Please open a new issue with more details or ask in the chat https://prosody.im/discuss

New comment

Not published. Used for spam prevention and optional update notifications.