Hi @Tony,
Are you able to ask QNAP Systems, Inc. for an update (if you would like to try on 5.10)?
↧
Android app is not working
↧
Open mattermost desktop app via url
Hi @s.azdoufal,
I’m not sure if this is possible, but you could use the Ctrl + K shortcut to quickly switch to a specific channel. More information about shortcuts here: https://docs.mattermost.com/help/messaging/keyboard-shortcuts.html.
↧
↧
Tuning mattermost for client performance
Hi @gubbins,
I haven’t heard feedback from community on this yet, would you like me to help open a support ticket and our support team could take a closer look at this?
↧
Android app is not working
I will ask them.
Where could I find the 5.10 package ? Thank you
↧
Community version, user privileges
to say what Amy said a bit differently, the ability to set user privileges is not part of the freely usable “team edition” builds of Mattermost. This has previously been discussed for example in Adjust member's authority on channel
For technical reasons the code to handle set permissions that have already been set are part of the open source code (since these restrictions are stored in the database). In previous version you could patch the server code to show the ui to change these permissions (it was a simple “has license” check somewhere, will not share the patch here out of respect for the Mattermost developers), but you could also temporarily run the enterprise edition with an evaluation key, set permissions and then go back to the free team edition.
↧
↧
SSL certificate for dockerized Mattermost installation
Hi all - I was renewing the certificate from docker installation of Mattermost, following those instructions: https://github.com/mattermost/mattermost-docker#install-with-ssl-certificate
I renewed the certificate using certbot, then copied the cert.pem file to ./volumes/web/cert/cert.pem, and privkey.pem to ./volumes/web/cert/key-no-password.pem
but when I run docker-compose up, the app container fails. The error being:
Error: failed to load: invalid config: Config.IsValid: model.config.is_valid.tls_cert_file.app_error,
I think it’s because of the file permissions on the cert files, but I’m not sure.
$ sudo ls -al volumes/web/cert/
total 12
drwxrwxr-- 2 majdal docker 70 May 2 11:26 .
drwxr-xr-x 3 root root 18 Sep 17 2018 ..
-rwxrwxr-- 1 majdal docker 1919 May 2 10:19 cert.pem
-rwxrwxr-- 1 majdal docker 3566 May 2 11:26 fullchain.pem
-rwxrwxr-- 1 majdal docker 1704 May 2 10:19 key-no-password.pem
Many thanks!
↧
SSL certificate for dockerized Mattermost installation
Hi @majdal,
Would you be open to creating an issue on the docker project and the project creators will be able to assist you: https://github.com/mattermost/mattermost-docker/issues?
↧
SSL certificate for dockerized Mattermost installation
Hey @amy.blais - I definitely can, but should we first make sure that it’s not an obvious problem that could be resolved here first?
↧
SSL certificate for dockerized Mattermost installation
@pichouk Can you help take a look at this one?
↧
↧
Colored emojis between different browsers
Okay, I solved the problem. As expected, it wasn’t an error from Mattermost but a Linux font misconfiguration. Arch Linux and Ubuntu required similar but different solutions. In any case, the Noto Color Emoji font needs to be installed.
For Arch Linux it was sufficient to follow this guide, while Ubuntu needed another one.
In case of the latter one, I changed my personal solution to put the config file not in my home dir config but in the system config folder /etc/fonts/conf.avail resp. /etc/fonts/conf.d. First, I tried naming the config 01-emoji.conf but obviously it got loaded to early. After renaming it to 65-emoji.conf it worked. I guess, the solutions with the config in the home dir work because they get loaded after the system config.
↧
Colored emojis between different browsers
In the answer I linked there is a reference to an older answer to an older question that I actually used. I mention that because those two answers differ in exactly the naming of the config file.
↧
Select element default value not displayed
Hi,
I have a problem that I don’t know how to solve.
When I’m using the api to create a dialog, all the select default values are not displayed:
'dialog': {
'callback_id': 'callback',
'title': 'title',
'icon_url': 'http://www.mattermost.org/wp-content/uploads/2016/04/icon.png',
'elements': [
{
'display_name': 'Task',
'name': 'task',
'default': 'opt1',
'type': 'select',
'options': [{'text': 'Option 1', 'value': 'opt1'}, {'text': 'Option 2', 'value': 'opt2'}],
'optional': False
}
],
'submit_label': 'Submit Test',
'notify_on_cancel': True,
'state': 'state'
}
But on submit, the value default value is correctly in the payload as intended.
Do you have any idea ?
↧
Select element default value not displayed
@Hanzei / @jasonblais ^
↧
↧
Team Edition vs Enterprise
To clarify the answer to the original question - using Enterprise Edition without a license is fine, and will cause no issues. The Enterprise features just will not be unlocked until you upload a license.
(The only difference between the Team Edition download and the Enterprise Edition download is that you have the ability to upload a license to Enterprise Edition if you choose to, while Team Edition needs to be upgraded to Enterprise Edition before a license can be added).
↧
Select element default value not displayed
@gloupmer Do you have a trigger_id and url part of the form submission? https://docs.mattermost.com/developer/interactive-dialogs.html#parameters
↧
SSL certificate for dockerized Mattermost installation
In theory the certificate is only mounted on the web container so I don’t think that a permission issue will trigger an error message in Mattermost application.
This Mattermost application log message is on this part of the Mattermost code, but I don’t know what it means. If a Mattermost developper could help to explain what conditions triggers this message, maybe we would find the issue.
↧
Select element default value not displayed
yes, everything works perfectly, the dialog is correctly displayed but not the default values on select elements
↧
↧
Install on ispconfig Debian9 with docker =connection reset
I just saw that your web container bind your 8065 port to the port 8065 of the container. Same with port 4433.
The web container listen requests on port 80 only (port 443 too if you configure it) so I think what you want to do is the bind port 8065 of your host to port 80 of your web container.
Normally you should bin port 80 of your host to port 80 of your container. I guess that you already have another process listening on port 80 of your host. If this process is a reverse proxy, I encourage you to use it in front of app container instead of the web container. or at least use it in front of the web container, and terminate HTTPS on your reverse proxy.
↧
SSL certificate for dockerized Mattermost installation
Is there someone we could mention here to follow up?
↧
Stocks Alerts to Channel (over Webhooks?)
HI, i am searching something, which can tracks stocks and if they drop X% then an Alert will be posted into Mattermost Channel.
Does anyone has an Idea how i can archive this?
↧
