Access Rocket chat within Egroupware

RalfBecker 2019-09-05 09:02:54 UTC #22

What type of installation do you have?

package installation: apt, yum, zypper
direct docker-compose
developer install: git, composer, …

Ralf

adnanbutt050 2019-09-05 09:17:53 UTC #23

Hey @RalfBecker,

direct docker compose

RalfBecker 2019-09-05 09:29:19 UTC #24

Our docker-compose.yml does NOT yet install Rocket.Chat or Collabora, only the packages do!

The Rocket.Chat EGroupware app, is NOT the Rocket.Chat container/server, it’s just an EGroupware app to display Rocket.Chat inside EGroupware, it needs the container.

You can use the docker-compose file from Rocket.Chat itself:
https://rocket.chat/docs/installation/docker-containers/docker-compose/

You need to change the ROOT_URL to something matching your installation eg. https://domain.com/rocketchat and you need to set up a reverse proxy for /rocketchat into the container, like we do in your packages:
https://github.com/EGroupware/build.opensuse.org/blob/master/server:eGroupWare/egroupware-rocketchat/egroupware-rocketchat/apache.conf

This are only pointers, I don’t have time to support you setting up your individual system, please use our packages, if you want Rocket.Chat and Collabora integration!

Ralf

prodesk 2019-09-05 14:37:55 UTC #25

Hi All!

Same problem as adnan. I’ve installed all from egroupware-docker upgrading from 17.1
Rocket is accessible out from egroupware.
All configuration like your suggestion but i’m not able to see rocketchat from administration -> rocket.chat -> configuration. (Status:Error contacting Api server: /api/info)
No question mark in user icon (top right) but the error is always the same
In docker installation where is the file “egroupware-rocketchat.conf” ? Pheraps is there a misconfiguration ?
Why is not possible change the url in administration -> rocket.chat -> configuration.?

Thanks

prodesk 2019-09-05 15:03:56 UTC #26

I can’t understand why it doesn’t update the url. I think the problem depends on it.
In fact, only “/ api / info” appears in the error message and not the entire path.
Wouldn’t it be possible to force the parameter somewhere?
Is it in a configuration file or in a database field?

prodesk 2019-09-09 06:20:40 UTC #27

Problem partially solved or better … circumvented
Since it was not possible to change the server path setting from egroupware/administration I forced the value into the appropriate field in the database. The error “cannot contact the server … / api / info” remains in the server setting and the access.
In the settings of Rocketchat (OAuth setup) I had to replace the path of my “Egroupware” installation with the IP address and in Egroupware in the OpenID client setup leave the path (NO IP).
I had to replace the recommended “Login Style” setting with Popup instead of Redirect. When I select “Rocket.Chat” from Egroupware a login window of Egroupware opens again a sub-window with default user = “anonymous” I have to re-enter username and password and at this point Rocketchat works by logging in with the Egroupware user. In this case it seems that the user / password data is not passed but with double login it works.
I hope it can be useful to identify the problem.

RalfBecker 2019-09-09 07:20:48 UTC #28

We made some progress in that regard: if the Rocket.Chat URL ends with a slash, it is not stored, so the url should be something like https://example.org/rocketchat (no trailing slash). Then you can save it.

About the other stuff with the IP address: this will not work, if you use https and it is probably caused by the container is not able to contact the full domain name. It can be a name-resolution problem or eg. NAT reflection in your router. Most easy workaround is to put the IP address of your machine or your docker0 bridge:

github.com

EGroupware/build.opensuse.org/blob/master/server:eGroupWare/egroupware-rocketchat/egroupware-rocketchat/docker-compose.yml#L33


    - ROOT_URL=http://localhost/rocketchat
    - MONGO_URL=mongodb://mongo:27017/rocketchat
    - MONGO_OPLOG_URL=mongodb://mongo:27017/local
#     - HTTP_PROXY=http://proxy.domain.com
#     - HTTPS_PROXY=http://proxy.domain.com
  depends_on:
    - mongo
  ports:
    - 127.0.0.1:3000:3000
  container_name: rocketchat
  # set the ip-address of your docker host AND your official DNS name so Rocket.Chat
  # can access EGroupware without the need to go over your firewall
  #extra_hosts:
  #- "my.host.name:ip-address"


mongo:
  image: mongo:4.0
  restart: unless-stopped
  volumes:
   - mongo:/data/db
   - /var/lib/egroupware/default/rocketchat/dump:/dump

Ralf

prodesk 2019-09-09 10:38:43 UTC #29

Thanks Raf.

For the fact that we have to put the again and the redirect doesn’t work, can you tell me something?
I thought Egroupware would pass the credentials directly. If you set the “login style” as suggested = “redirect” you cannot log in.

bye

RalfBecker 2019-09-09 10:44:09 UTC #30

The only difference between login style redirect and popup, is that one works in a popup and the other in the main window. Server-side code is absolute identical. If one does not work, the other will fail too.

Maybe you had a temporary problem …

Ralf