Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Integrations not working #5896

Closed
NQNetwork opened this issue Feb 3, 2017 · 9 comments
Closed

Integrations not working #5896

NQNetwork opened this issue Feb 3, 2017 · 9 comments
Assignees
@rodrigok
Labels
feat: integration / plugin type: support
Milestone
0.51.0

Comments

@NQNetwork
Copy link

Hello,

After this issue #5841 we have sold our problem by updating the docker-composer.yml with your new file.
But after that, our integrations like Giphy not working.
When we try to use it, we have this error log:

Exception in callback of async function: TypeError: Cannot read property 'statusCode' of null at /app/bundle/programs/server/packages/rocketchat_integrations.js:1316:30 at runWithEnvironment (packages/meteor.js:1176:24)

Thanks.

Rocket.Chat Version: 0.50.1
Running Instances: 1
DB Replicaset OpLog: Active
Node Version: 4.7.1
Running with docker-compose
@manuelbachl
Copy link

Hi there, could anyone determine if this is a RC related issue or if we have to adjust our giphy integration? If so, please open an issue here: https://github.com/FinndropStudios/GifRocket
Thanks in advance for figuring out - unfortunately we're limited in time at the moment

@thiesschneider
Copy link

We are running the same version and it is working...

@NQNetwork
Copy link
Author

@manuelbachl , the problem is not just for the Giphy integration. We have an integration for Redmine, and this is the same issue.

graywolf336 added a commit that referenced this issue Feb 3, 2017
@graywolf336
Don't check for property on result if it isn't there.
d44ba0a 
Closes #4175, #5762, and #5896.
@graywolf336
Copy link
Contributor

This happens when the result from going out to the urls doesn't work and errors out.

@engelgabriel engelgabriel added this to the 0.51.0 milestone Feb 4, 2017
@NQNetwork
Copy link
Author

Hello,

When we try a curl on an url with the container, it's appear that Rocket.Chat try to connect by proxy.domain.com. How to disable that?

docker exec -it b47060af2214 curl -l "https://api.giphy.com/v1/"
curl: (7) Failed to connect to proxy.domain.com port 1080: Connection timed out

@graywolf336
Copy link
Contributor

Have you setup a proxy for it to use? As Rocket.Chat by default won't try to proxy (that I'm aware of) unless it has been told to.

@rodrigok
Copy link
Member

rodrigok commented Feb 6, 2017

@NQNetwork You should remove the HTTP_PROXY and HTTPS_PROXY environment variables from your docker-compose.yml or change to your proxy settings.

@rodrigok rodrigok closed this as completed Feb 6, 2017
@rodrigok
Copy link
Member

rodrigok commented Feb 6, 2017

Please reopen this issue if the problem persists

@anthok
Copy link

anthok commented Feb 10, 2017 •
edited
Loading

I'm having the same issue except I'm running through snap. Is there a specific way to set Rocket's proxy. I've tried setting the EnvironmentFile=/etc/environment in the service files of caddy and mongo for systemd.

rodrigok pushed a commit that referenced this issue Feb 16, 2017
@graywolf336 @rodrigok
Enhance outgoing webhooks and add history (#5823)
e888808 
* Convert the majority of the integrations package to JavaScript

* Move the trigger handler to it's own class

* Start trying to generalize integration items

* Yay, additional events trigger outgoing webhooks

* Silence codacy and fix eslint problems.

* Started work on user created event for outgoing integrations

* Finish the outgoing integration work on the user created event.

* Add user join and leave room events for outgoing webhooks

* Add fields to the rest api integration creation and clean up the processWebhookMessage

* Add the HTTP to the incoming webhook context

* Don't check for property on result if it isn't there.
Closes #4175, #5762, and #5896.

* Add archive room and file upload events for the webhooks

* Disable integrations when the user to run/post as gets deleted.

* Try to fix the tests failing due to the requird events property

* Add history of integration which get fired

* Add the missing file for the IntegrationHistory

* Fix deleting users being broke due to my code

* Add the outgoing webhook integration history viewing page along with v1 rest api to retrieve it

* Integration history replays are now enabled along with advanced settings

* Work on the advanced settings and enable paging on the integration history

* Enable i18n for the history and advanced settings

* Update the wording on the word placement

* Move migration to be 88 now.

* Add missing translations for the webhooks

* Fix en.i18n.json identation

* Fix integrations.html indentation

* Fix more identations

* Fix identation of integrationsOutgoing.html
@holgerdell holgerdell mentioned this issue Dec 3, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rodrigok rodrigok

Labels
feat: integration / plugin type: support
Projects
None yet
Milestone
0.51.0
Development

No branches or pull requests
8 participants
@rodrigok @graywolf336 @engelgabriel @anthok @NQNetwork @thiesschneider @manuelbachl @MartinSchoeler