We are rolling out 7.0.4 slowly. Mostly fixes various regressions. Our DO/Vultr/AWS marketplace images are also updated to the latest version. The DO image is pending approval.

Add password reveal button to login pages appstore: fix crash if account already registered Do not nuke all the logrotate configs on update Remove unused httpPaths from manifest cloudron-support: add option to reset cloudron.io account Fix flicker in login page Fix LE account key re-use issue in DO 1-click image mail: add non-tls ports for recvmail addon backups: fix issue where mail backups where not cleaned up notifications: fix automatic app update notifications

@nebulon cheers !

Teamspeak 5 Beta is now available to download from the Windows11 store! 👍

You no longer require closed beta access 🚀 to voice chat on your favourite servers on the new client,
but will still require closed beta access to unlock the global chat features using the methods listed in this Thread.

How to get closed beta access is written in the first post of the same Thread

@jdaviescoates All the features listed on the top are part of 6.3.

@atridad fixed

@thetomester13 Reading about the function of the whitelist on their wiki suggests this is for filtering the bridges being displayed, not for access to the service.

So it's not a network security context as I initially thought.

6.3.5 will be rolled out slowly.

[6.3.5]

Fix permission issues with sshfs filemanager: reset selection if directory has changed branding: fix error highlight with empty cloudron name better text instead of "Cloudron in the wild" Make sso login hint translatable Give unread notifications a small left border Fix issue where clicking update indicator opened app in new tab Ensure notifications are only fetched and shown for at least admins setupaccount: Show input field errors below input field Set focus automatically for new alias or redirect eventlog: fix issue where old events are not periodically removed

I am open to other solutions.

Anyone know the devs for ps and top?

Can you contribute to their code to mark container IDs with something?

Or add a container aware view to the tools to use?

@jeau I started to explore OmekaS and created an instance for testing.
I just wanted to say THANK YOU for a really impressive piece of software. 👍 👏 👏 👏

In 6.3, we also have vultr dns integration.

I have staged 6.2.8 now, will roll out slowly as always.

Additional information: There is no API_Secret in the ENV file in the standard app package. Depending on your thousands of clients, it takes some time to migrate. For me, it was done in less than 5 minutes.

The only moment of confusion was: when installing IN v. 5. you have to fill in the name of the company in a modal frame. After the migration it took me a few seconds to realise that there is a multi-company option in IN v. 5 and I had to switch to the "other" (migrated) company (which has the same company name).

It looks like everything has migrated well.

@mdreira said in Changes to WordPress apps:

1-Is a security plugin necessary in wordpress managed?

I use the Developer package for WordPress so can't speak for the Managed version too much, but my general advice would be the following:

Generally speaking, it'd best to only install plugins when you know you have a need that isn't already addressed in the system. Thus, knowing your exact needs would come before choosing any particular plugin. My rule of thumb personally is not to install a plugin unless I understand why I need it and what I want to achieve with it.

Security is a huge umbrella with probably hundreds of different sub-categories / uses. So for example, it'd be good to know if you are wanting to be notified of any irregular file changes, block specific functionality in WordPress, lockdown user accounts with custom permissions, change the login page URL, rate limit logins, or a mix of those or a whole bunch of other ones.

It's good to copy an existing WordPress site (or a default one) to test new plugins on to see if they will interfere with your current setup, avoiding testing in any live production website.

Aside from the above, I'd honestly recommend just using the Developer package of WordPress. I know that goes against Girish's recommendation 👼 but there are at least several of us "power users" in Cloudron that feel there's no real upside to the Managed package other than a little bit more security by default. Eventually, whether it's sooner or later, you'll likely have the need to use a particular plugin that will need to modify files or access certain files, in which case you'll then have to do a bunch of work to migrate from the Managed package to the Developer package, so IMO you may as well just start on the Developer package to begin with unless you have very basic needs for WordPress and don't plan on growing it at all. And you won't want to be caught in a project that's time-sensitive to then find out you need to now also migrate an entire website to a new app instance type. I learned that lesson the hard way myself. 😉

By the way, every app has its own category in the forum. You may be better served to create a separate and dedicated post in the WordPress (managed or developer) categories. This thread in particular is pretty old and is generally on a different topic than "security plugins" for WordPress.