17 / 17
Jun 2021

Hello Ralf,
thanks for your reply, yes it seems that the /rocketchat prefix is missing:


Can I just go back to stable? I see that the database is on Version

Database Migration
215 (February 3, 2021 8:26 AM

Thanks again
Alex

You can try it (after a full backup). The last version we released is 213(!):

See also:

Stefan

Hello Stephan,
I just tried, it is not working… the image sees 215 and does not know how to handle this. I will have to wait…
BR
Alex

Hi Alex.

I once looked in


and had a look. But I can’t find anything there that fits.

Did you install via egroupware-rocketchat.packet?:


What happens when you upload new images?

Stefan

Ich muss nur den file-upload in der Proxy Konfiguration des Nginx mit eintragen, dann gehen die auch wieder, nach dem Paketupdate.

Ich hoffe das ich die nächsten Tage dazu komme.

Ralf

Hello Ralf,
I added the following in the nginx.conf:

location ~ ^/file-upload/(.)$ {
rewrite ^/file-upload/(.
) /rocketchat/file-upload/$1 permanent;
}

and it works… :grinning:
BR
Alex

2 months later

Hi ALexS, I have the same ploblem,I running egroupware in to a docker container , this is my nginx.conf
user nginx;
worker_processes auto;

error_log /var/log/nginx/error.log warn;
pid /var/run/nginx.pid;

events {
worker_connections 1024;
}

http {
include /etc/nginx/mime.types;
default_type application/octet-stream;

log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                  '$status $body_bytes_sent "$http_referer" '
                  '"$http_user_agent" "$http_x_forwarded_for"';

access_log  /var/log/nginx/access.log  main;

sendfile        on;
#tcp_nopush     on;

keepalive_timeout  65;

#gzip  on;

include /etc/nginx/conf.d/*.conf;

where I insert the code you wrote ?
Tks
Pep

I do NOT recommend applying these fixes manually, as it will create a problem, once we rollout a fix via a new rocketchat package.

Specially as the full fix is a different one from what we currently have and which is similar to what @AlexS did.

The full fix will pass everything not matching /egroupware or other explicit paths into the rocketchat container, no longer running Rocket.Chat under /rocketchat, which the Rocket.Chat project stopped supporting some versions back, but run it under /.

Ralf

2 months later

Hello everyone,
I’m sorry to return to this issue but I need to know if anyone has any news related to the preview problem and file down load. Even with version 3.15.0 the problem appears the same.
image.
File downloading does not work either. The downloaded file appears to be corrupted.


No idea about how to solve the problem?
Thanks
Gabriele

Hi Gabriele,

the problem is caused by Rocket.Chat no longer supporting a prefix/subpath in the URL.

We worked around it, but that workaround is not in the RC container, but in our proxy files for Nginx or Apache2, which come with the updated egroupware-rocketchat DEB/RPM package.

Are you sure you’re up-to-date in that regard and NOT having told you’re package manager to keep the old files, instead our updated ones with the fixes? The files are in /etc/egroupware-rocketchat/{nginx,apache}.conf.

Ralf

Hi , Ralf this is the content of my /etc/egroupware-rocketchat/nginx.conf

# Rocket.Chat sniplet meant to be included in server block of EGroupware vhost

        # proxy into rocketchat container
        location /rocketchat {
                proxy_pass http://127.0.0.1:3000;
                include proxy_params;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
        }

and

RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule ^/rocketchat/(.*) ws://127.0.0.1:3000/rocketchat/$1 [P,L]
RewriteCond %{HTTP:Upgrade} !=websocket [NC]
RewriteRule ^/rocketchat/(.*) http://127.0.0.1:3000/rocketchat/$1 [P,L]

is the content of my /etc/egroupware-rocketchat/apache.conf, the server and the container are updated at the stable version.
Can you help me to resolve the same “retry” error?
Tks

These are the old versions of the file and you’re package manager created either an .rpmnew or .dpkg-new file with the current content, you should use.

The latest version of the files can also be downloaded from Github:

Ralf