Search results

MongoDB 7.x is not yet supported by Rocket.Chat. Version 6 is the way to go. Basically the following steps would give you a Rocket.Chat instance based on two containers: a) Setup a MongoDB container, e.g. Image: bitnami/mongodb:6.0.13 Settings: Also connect to the newly created MongoDB and...

Do you have any active firewall? If so please check the rules if they are preventing the access. The default Plesk firewall would do so in your scenario on port 3000. System policy for incoming traffic => Deny all other incoming traffic

@whu I would wait at least for the first or second patch release. As there is no way for downgrading a buggy new release can be a lot of headache. In the past we had to learn that the hard way. When 18.0.60 #1 is released we will start the deployment on our dev servers. I would never install a...

@David Borrink Is 3000 your external docker mapped port of the container? If the port is e.g. 3001 try the following config for "Additional nginx directives" (Proxy mode needs to be switched off too): # see...

As there seems to be no progress at all by Plesk for the bugs EXTSSLIT-1879 and PPS-15436 we decided to implement our own work-around. To share wildcard certificates among subdomains is buggy with heavy impact on our client's satisfaction. To avoid this shameful bug of a so called "server...

It is also possible to install Rocket.Chat without using docker-compose. We are using a setup of two single standard containers. One container is the needed MongoDB instance, e.g. Image: bitnami/mongodb:6.0.13. The other one is the Rocket.Chat server itself, e.g. Image: rocketchat/rocket.chat:6.6.6.

@Bitpalast I also like the idea that we could set the link to an own target to advertise our own WordPress developers of the company as some of our clients do not know, that we also have this service. This would also help the intended purpose of Plesk, that the:

PPPM-13562 was fixed with the release of Plesk Obsidian 18.0.60.

Fixed with the release of Plesk Obsidian 18.0.60.

Solved with the release of Plesk Obsidian 18.0.60.

We did not install 6.3.0 yet. We are still on 6.2.15. So this feature was deployed by accident to older versions? At least the setting does also work for 6.2.15.

Hello, as the title says: how can we disable that advertisement in the WordPress toolkit? We are actually not amused, that Plesk wants to catch out clients.

The built-in backup solution is not really useful for large Plesk servers with several TB of user data. On top typical backup recovery tasks of our clients like... a) Can I have a database copy from 3 days ago? b) Can you give me a mailbox copy from 5 days ago? c) Can I get a copy of my webroot...

After digging deeper into our problem we did find the reason. "/etc/default/named" did not have the correct content (still default Debian 12). After updating the file to the Plesk specific default settings the DNS is working like a charm again: Maybe the Plesk team could add this info to a...

Hello, after upgrading one of our older servers from Debian 10 to 12 the BIND domain name server does not answer to requests anymore. For domains where the server is the primary name server requests end up like this: Dig: Log: AppArmor looks good so far same as the bind configuration. But...

The anomaly is quite interesting and hard to catch. Changes to printk of the kernel have also no effect even with the lowest values. cat /proc/sys/kernel/printk 1 1 1 1 Everything with values of 0 (KERN_EMERG), 1 (KERN_ALERT) and 2 (KERN_CRIT) is printed in the terminal...

We can confirm the same problem on our Debian 12 Plesk servers after a fresh install. The minimal base system of Debian 12 is not affected. The same error messages are logged but not shown inside the terminal. After Plesk is installed the warnings are printed in the console.

@Peter Debik At the moment we only have reseller licenses. So we cannot open support tickets as mentioned before. And our reseller does also not accept support requests. Maybe we will switch one affected server to a license directly from Plesk so we can open support tickets directly. But as the...

Here is a bit of the madness we are facing every day, and this is just one server.

As feedback for anyone who did also wait with the rollout of this version. We did reach phase 3 by deploying 18.0.59 #2 to our live servers with hundreds of clients. So far all looks good. No negative feedback of clients in our ticket system.