New Install Issue - 404 error

scubadave112

Hello everyone, I did a clean install and got all my DNS records sorted out and am now sending/receiving emails.

I was playing with meet and sent an invite to an external email and when I click the link I am getting a 404 page (Viewable HERE)

I followed some of the other posts here and nothing seems to fix this. I am able to login to chat (Mattermost) and everything else seems to be working just fine.

antipiot

scubadave112

Hello, i juste encountered this while playing around in a new installation.
Can you have a look in console login screen and check nginx is not showing as not started?

BusinessTux

On one of my installations I have the same error. meet ist not installed and there are installation errors in grommunio-setup.log for this package.

What returns the following on your server?
zypper info grommunio-videobridge grommunio-jicofo grommunio-meet

makeitsimple

Hello

I had the same issue a few month ago and it was nginx that was no longer running.
And last week, nginx crashed due to an update that removed my own SSL/TLS certificates on the server.

Maybe something worth to check?

segro

hi,
I also have problems with /meet on some installations. are the meet packages removed from reposity or renamed?

mail:~ # zypper info grommunio-videobridge grommunio-jicofo grommunio-meet
Loading repository data...
Reading installed packages...
package 'grommunio-videobridge' not found.
package 'grommunio-jicofo' not found.
package 'grommunio-meet' not found.

GeneralProbe

Ja, wenn Du Dir das Repo ansiehst, dann ist dem so.
Ich denke Grommunio hat die Standard-Namen für die Pakete gesetzt.
Sie heißen jetzt "jitsi-*"

antipiot

GeneralProbe
It could be a cool thing to keep threads in english for other people looking for help and informations :-)

segro

hi,
aber wenn man die installiert startet nginx nicht mehr, da sind die pfade für die ssl certs auch komsich. Hast du das so am laufen?

GeneralProbe

Ich warte seit November auf eine funktionierende Debian-Installationsroutine.

Mich hat Dein Problem nur interessiert.
Am besten gehst Du auf die alten Pakete zurück (wenn das mit Zypper geht, ich verwende selbst nur Debian bzw. Fedora) und wartest bis die Entwickler von Grommunio das in der Community Edition beheben.

Ich verwende (noch) Kopano in der Debian Community Edition, möchte da eben von weg.

segro

tja, da warten wir wohl alle drauf ;-) aber auch unter centos hatte ich wegen der ganzen abhängikeiten noch keinen erfolg... aber es soll ja sehr bald was für debian kommen... was kopano angeht bist Du hier wohl nicht der einzige ,-)

mwilliams

https://github.com/jengelh/g-manual/blob/master/index.rst

(findet in erweiterter fassung bald für alle distros einzug bei https://docs.grommunio.com)

BusinessTux

Nur leider lassen sich die neuen Pakete nicht ohne Konflikte installieren :-(

grommunio:~ # zypper install jitsi-meet-branding-grommunio
Loading repository data...
Warning: Repository 'debug-update' appears to be outdated. Consider using a different mirror or server.
Warning: Repository 'repo-backports-debug-update' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...
Resolving package dependencies...

The following 3 NEW packages are going to be installed:
  jitsi-meet jitsi-meet-branding-grommunio jitsi-meet-prosody-plugins

3 new packages to install.
Overall download size: 0 B. Already cached: 12.7 MiB. After the operation, additional 40.0 MiB will be used.
Continue? [y/n/v/...? shows all options] (y):
In cache jitsi-meet-prosody-plugins-2.0.6726-lp153.4.4.noarch.rpm                                                                                                                                                                              (1/3), 206.3 KiB (254.9 KiB unpacked)
In cache jitsi-meet-2.0.6726-lp153.4.4.noarch.rpm                                                                                                                                                                                              (2/3),  12.5 MiB ( 39.6 MiB unpacked)
In cache jitsi-meet-branding-grommunio-2.0.6726-lp153.1.1.noarch.rpm                                                                                                                                                                           (3/3),  49.9 KiB (194.1 KiB unpacked)

Checking for file conflicts: ................................................................................................................................................................................................................................................[error]
Detected 5 file conflicts:

File /srv/jitsi-meet/base.html
  from install of
     jitsi-meet-2.0.6726-lp153.4.4.noarch (grommunio)
  conflicts with file from install of
     jitsi-meet-branding-grommunio-2.0.6726-lp153.1.1.noarch (grommunio)

File /srv/jitsi-meet/images/logo-deep-linking.png
  from install of
     jitsi-meet-2.0.6726-lp153.4.4.noarch (grommunio)
  conflicts with file from install of
     jitsi-meet-branding-grommunio-2.0.6726-lp153.1.1.noarch (grommunio)

File /srv/jitsi-meet/images/watermark.svg
  from install of
     jitsi-meet-2.0.6726-lp153.4.4.noarch (grommunio)
  conflicts with file from install of
     jitsi-meet-branding-grommunio-2.0.6726-lp153.1.1.noarch (grommunio)

File /srv/jitsi-meet/index.html
  from install of
     jitsi-meet-2.0.6726-lp153.4.4.noarch (grommunio)
  conflicts with file from install of
     jitsi-meet-branding-grommunio-2.0.6726-lp153.1.1.noarch (grommunio)

File /srv/jitsi-meet/title.html
  from install of
     jitsi-meet-2.0.6726-lp153.4.4.noarch (grommunio)
  conflicts with file from install of
     jitsi-meet-branding-grommunio-2.0.6726-lp153.1.1.noarch (grommunio)

File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.
Continue? [yes/no] (no):

mwilliams

die branding packages in der community überschreiben (momentan) das hauptpackage. nicht schön. update expected bis dienstag kommender woche

neu

More details on https://github.com/grommunio/grommunio-cui/issues/3

neu

Is this issue only on openSUSE_Leap_15.3, or across all community repo?

Manual installation from repos available at

https://github.com/jengelh/g-manual/blob/master/index.rst
Covering OpenSUSE, RHEL8, Debian 11, Ubuntu 20.04

https://download.grommunio.com/community

Is grommunio-meet sourcecode available on github? I'd test installing it all from source if possible. Anything that leads towards a closer solution.

Should there be community repo for tested updates, and separate repo for bleeding edge updates?

jengelh

Is grommunio-meet sourcecode available on github

neu

jengelh So what's the difference from the jitsi packages provided from Grommunio vs the original jitsi packages? I'm just trying to find a way to install grommunio-meet properly. I'm unable to do that.