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.

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

Web client doesn't load in Firefox ESR 45.8.x #6428

Closed
tumbl3w33d opened this Issue May 17, 2017 · 15 comments

Comments

Projects
None yet
5 participants
@tumbl3w33d

tumbl3w33d commented May 17, 2017

Summary

Web client fails to load in Firefox ESR (45.8.x) when connecting to self-hosted mattermost server 3.9.0

Steps to reproduce

Open the web client in a Firefox ESR (45.8.x)

Expected behavior

Web client loads.

Observed behavior

  • stare at 3 dots that indicate a loading process
  • open firebug and check the console
  • find a stacktrace that informs you about jQuery.Deferred exception: window.mm_config is null

Possible fixes

N/A

Notes:

  • I reproduced that on a colleague's machine to make sure it's not an issue caused by my workstation.
  • Deleting the browser cache didn't help
  • Doing the same thing in my chromium works
  • Connecting via standalone client works
@lindy65

This comment has been minimized.

Show comment
Hide comment
@lindy65

lindy65 May 18, 2017

Member

Hi @tumbl3w33d,

As I understand it, Firefox ESR is a desktop app version of Firefox for large corporations?

Could you explain a little more about your set-up as I'm wondering whether some settings within the Firefox ESR set-up are blocking Mattermost from loading.

Member

lindy65 commented May 18, 2017

Hi @tumbl3w33d,

As I understand it, Firefox ESR is a desktop app version of Firefox for large corporations?

Could you explain a little more about your set-up as I'm wondering whether some settings within the Firefox ESR set-up are blocking Mattermost from loading.

@tumbl3w33d

This comment has been minimized.

Show comment
Hide comment
@tumbl3w33d

tumbl3w33d May 18, 2017

Hi @lindy65,
yes Firefox ESR is a desktop app. It's the LTS version of the browser and not necessarily limited to corporations (although it's attractive for these, of course). When you're not after having the latest features, you gain more stability which is, for obvious reasons, attractive for a homogeneous network of workstations. For developers it can be interesting when they use Selenium and want to have less issues with web driver compatibility.

Debian 8 (current stable) comes with Iceweasel (rebranded for trademark reasons) which is a Firefox ESR and with a newer package called firefox-esr. The reason for the co-existence is that they are transitioning away from the rebranded thing, but that's not relevant for this issue.

I'm running Debian Stretch (that's the upcoming stable, release is soon to come). I don't have any plugins active. Our company (where my workstation is running) has no filtering forward proxy whatsoever. The TLS certificate that our self-hosted Mattermost uses is issued by Let's Encrypt.

If you need more information feel free to ask.

tumbl3w33d commented May 18, 2017

Hi @lindy65,
yes Firefox ESR is a desktop app. It's the LTS version of the browser and not necessarily limited to corporations (although it's attractive for these, of course). When you're not after having the latest features, you gain more stability which is, for obvious reasons, attractive for a homogeneous network of workstations. For developers it can be interesting when they use Selenium and want to have less issues with web driver compatibility.

Debian 8 (current stable) comes with Iceweasel (rebranded for trademark reasons) which is a Firefox ESR and with a newer package called firefox-esr. The reason for the co-existence is that they are transitioning away from the rebranded thing, but that's not relevant for this issue.

I'm running Debian Stretch (that's the upcoming stable, release is soon to come). I don't have any plugins active. Our company (where my workstation is running) has no filtering forward proxy whatsoever. The TLS certificate that our self-hosted Mattermost uses is issued by Let's Encrypt.

If you need more information feel free to ask.

@lindy65

This comment has been minimized.

Show comment
Hide comment
@lindy65

lindy65 May 19, 2017

Member

Hi @tumbl3w33d,

Thanks for your feedback!

I'll ask our devs whether they have any help/suggestions for you and post back here once I hear from them :)

Member

lindy65 commented May 19, 2017

Hi @tumbl3w33d,

Thanks for your feedback!

I'll ask our devs whether they have any help/suggestions for you and post back here once I hear from them :)

@paepke

This comment has been minimized.

Show comment
Hide comment
@paepke

paepke May 19, 2017

Can confirm that this happens on debian jessie
as a possible workaround you can install the current Firefox ESR 52 from the debian mozilla team which solves the issue for me. Nevertheless this should be fixed in mattermost.

paepke commented May 19, 2017

Can confirm that this happens on debian jessie
as a possible workaround you can install the current Firefox ESR 52 from the debian mozilla team which solves the issue for me. Nevertheless this should be fixed in mattermost.

@jasonblais

This comment has been minimized.

Show comment
Hide comment
@jasonblais

jasonblais May 19, 2017

Member

Thanks @tumbl3w33d and @paepke - were there any issues on an older version of Mattermost (if you upgraded to 3.9)?

Member

jasonblais commented May 19, 2017

Thanks @tumbl3w33d and @paepke - were there any issues on an older version of Mattermost (if you upgraded to 3.9)?

@tumbl3w33d

This comment has been minimized.

Show comment
Hide comment
@tumbl3w33d

tumbl3w33d May 19, 2017

@jasonblais no issues back at 3.8 and before. It started exactly with the 3.9 update.

tumbl3w33d commented May 19, 2017

@jasonblais no issues back at 3.8 and before. It started exactly with the 3.9 update.

@paepke

This comment has been minimized.

Show comment
Hide comment
@paepke

paepke May 20, 2017

Same here - migrated to 3.9 and it breaks on the ESR 45

paepke commented May 20, 2017

Same here - migrated to 3.9 and it breaks on the ESR 45

@jasonblais

This comment has been minimized.

Show comment
Hide comment
@jasonblais

jasonblais May 20, 2017

Member

Thanks! I've created a Jira ticket for us to investigate: https://mattermost.atlassian.net/browse/PLT-6650

Member

jasonblais commented May 20, 2017

Thanks! I've created a Jira ticket for us to investigate: https://mattermost.atlassian.net/browse/PLT-6650

@jasonblais

This comment has been minimized.

Show comment
Hide comment
@jasonblais

jasonblais May 23, 2017

Member

@paepke @tumbl3w33d Just to confirm: This works fine on Firefox ESR 52?

There have been some updates recently that have broken compatibility with older browser versions, and recommend upgrading to Firefox ESR 52.

Member

jasonblais commented May 23, 2017

@paepke @tumbl3w33d Just to confirm: This works fine on Firefox ESR 52?

There have been some updates recently that have broken compatibility with older browser versions, and recommend upgrading to Firefox ESR 52.

@tumbl3w33d

This comment has been minimized.

Show comment
Hide comment
@tumbl3w33d

tumbl3w33d May 23, 2017

@jasonblais yeah it works as usual on Firefox ESR 52. It's unfortunate that Debian's ESR package didn't get an upgrade to 52 yet even on Sid (unstable) which I run on my private machine, however, I guess you can just sit this out until 13th of June, when ESR 45 will hit EOL.

tumbl3w33d commented May 23, 2017

@jasonblais yeah it works as usual on Firefox ESR 52. It's unfortunate that Debian's ESR package didn't get an upgrade to 52 yet even on Sid (unstable) which I run on my private machine, however, I guess you can just sit this out until 13th of June, when ESR 45 will hit EOL.

@jasonblais

This comment has been minimized.

Show comment
Hide comment
@jasonblais

jasonblais May 25, 2017

Member

Thanks again @tumbl3w33d and @paepke

Given ESR 45 is reaching its end of life in three weeks, we recommend you to switch to ESR 52.

We'll also update our docs for updating the minimum Firefox version requirement: mattermost/docs#1209

Member

jasonblais commented May 25, 2017

Thanks again @tumbl3w33d and @paepke

Given ESR 45 is reaching its end of life in three weeks, we recommend you to switch to ESR 52.

We'll also update our docs for updating the minimum Firefox version requirement: mattermost/docs#1209

@jasonblais jasonblais closed this May 25, 2017

@jasonblais jasonblais reopened this May 25, 2017

@jasonblais jasonblais closed this May 29, 2017

@tpo

This comment has been minimized.

Show comment
Hide comment
@tpo

tpo Jun 1, 2017

(Same here - migrated to 3.9 and it breaks on my FF on Debian stable)

To recap:

  • Mattermost 3.8 works
  • your sysadmin upgrades it to 3.9
    (in my case idirectly via a gitlab upgrade)
  • Mattermost is now broken on all stable Debian clients
  • the Mattermost project closes the issue with "upgrade your Debian installation"

That's pretty lame IMHO. Why not fix the thing that introduced problem in the first place instead? Mattermost is now apparently broken on all systems running ESR 45. How do you know when/if those platforms will (be able to) upgrade?

tpo commented Jun 1, 2017

(Same here - migrated to 3.9 and it breaks on my FF on Debian stable)

To recap:

  • Mattermost 3.8 works
  • your sysadmin upgrades it to 3.9
    (in my case idirectly via a gitlab upgrade)
  • Mattermost is now broken on all stable Debian clients
  • the Mattermost project closes the issue with "upgrade your Debian installation"

That's pretty lame IMHO. Why not fix the thing that introduced problem in the first place instead? Mattermost is now apparently broken on all systems running ESR 45. How do you know when/if those platforms will (be able to) upgrade?

@tumbl3w33d

This comment has been minimized.

Show comment
Hide comment
@tumbl3w33d

tumbl3w33d Jun 1, 2017

At some point you need to limit the platforms/versions you support and I find it legitimate to not waste effort on supporting versions that are officially (EOL) not maintained anymore. In addition, if your company decides its chat solution is Mattermost, why not install the (well tested) standalone client then?

tumbl3w33d commented Jun 1, 2017

At some point you need to limit the platforms/versions you support and I find it legitimate to not waste effort on supporting versions that are officially (EOL) not maintained anymore. In addition, if your company decides its chat solution is Mattermost, why not install the (well tested) standalone client then?

@tpo

This comment has been minimized.

Show comment
Hide comment
@tpo

tpo Jun 1, 2017

In addition, if your company decides its chat solution is Mattermost, why not install the (well tested) standalone client then?

Because: if you want to use github, why not use their standalone client too (that is in fact a complete webbrowser + pixie dust)? And if you want to access nyt.com as well, then why not use their standalone client also? And slashdot. And gitlab. And stackoverflow. And redmine. And ... People's machines have only so much RAM. Maybe they'd like it to run applications that in fact really are different applications (say a compiler) or use their RAM for data (editing an image maybe?), instead of running N instances of the same application. I can see you point, but I think the path you're suggesting is a path of ressource and energy waste, which I'd rather not perpetuate.

tpo commented Jun 1, 2017

In addition, if your company decides its chat solution is Mattermost, why not install the (well tested) standalone client then?

Because: if you want to use github, why not use their standalone client too (that is in fact a complete webbrowser + pixie dust)? And if you want to access nyt.com as well, then why not use their standalone client also? And slashdot. And gitlab. And stackoverflow. And redmine. And ... People's machines have only so much RAM. Maybe they'd like it to run applications that in fact really are different applications (say a compiler) or use their RAM for data (editing an image maybe?), instead of running N instances of the same application. I can see you point, but I think the path you're suggesting is a path of ressource and energy waste, which I'd rather not perpetuate.

@tpo

This comment has been minimized.

Show comment
Hide comment
@tpo

tpo Jun 14, 2017

Debian stable has updated Firefox to 52.2.0. I can confirm that Mattermost now works in Debian stable with Firefox. That takes some steam out of my argument.

tpo commented Jun 14, 2017

Debian stable has updated Firefox to 52.2.0. I can confirm that Mattermost now works in Debian stable with Firefox. That takes some steam out of my argument.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment