element-web: Could not connect to the integration server Error
Description
In a newly created room, under the settings for said room, the Manage Integrations button is grayed out. After waiting ~60 seconds, I get a warning message that states Could not connect to the integration server.
Steps to reproduce
- Create new room
- Click the settings for that room
Manage Integrationsbutton is grayed out- Wait ~60 seconds for the
Could not connect to the integration servererror message
I expected to be able to click the Manage Integrations Button to configure Integration items.
Version information
- Platform: web (in-browser) AND desktop
For the web app:
- Browser: Chrome, latest
- OS: OS X 10.12.4 Beta
- URL: riot.im/app
For the desktop app:
- OS: OS X 10.12.4 Beta
- Version:
matrix-react-sdk version: 0.8.6
vector-web version: 0.9.7
olm version: 2.2.1
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 4
- Comments: 43 (11 by maintainers)
Is your homeserver behind a reverse proxy? If so, one other thing to check is that your proxy itself is using HTTPS (port 8448) with the homeserver. In other words, if your firewall/proxy is serving HTTPS on your WAN but using HTTP internally for local/network services, try changing this to HTTPS for synapse. My integrations did not work until I did so, even though the server worked otherwise.
I had the same issue. It turned out that I have to set the port number to 8448. Can not customize the port number if you want to use the integration or invite external users. It seems someone hard-coded the port number.
I have the same issue. I’m running Synapse from the docker appliance (https://hub.docker.com/r/silviof/docker-matrix/) on an Ubuntu box. When setting up an account, I use that as the home server and the default (vector.im) as the ‘identity server’. I’m using http://riot.im/app as the client.
I’m calling riot.im from Chrome on said Ubuntu box and from Safari on a Mac. When I try it from Chrome on the mac, I also get a ‘CORS request rejected’ message.
I was getting the same issue as @jcrabapple, what fixed it for me was going over these directions again. I was getting thrown off by the DNS SRV record part since my homeserver is on a subdomain. Once that was in place with my DNS provider the federation tester showed all good and the error was gone.
@jogleasonjr At least for me this worked.
Homeserver is Synapse (https://github.com/matrix-org/synapse). No privacy related plugins installed with Chrome.