Cloudron Forum

Thank you

Hi @nebulon I think there's a fix for this on Github, revert the changes in app/Core/Console/ConsoleKernel.php and apparently the error will disappear. See https://github.com/Leantime/leantime/issues/2710

Meanwhile I have chased @marcelfolaron for support.

@nebulon, version 3.2.0 has an issue that breaks Leantime if upgrade from an earlier version without first disabling all the plugins and deleting some files/folders. All very well, however the first you know about this is when the automatic upgrade has run and broken Leantime, by which time it is too late.
@marcelfolaron has kindly released a fix in version 3.2.1 which will allow us to get back up and running, however we cannot manually install it as we don't want to break the Cloudron updates system.
Can you give an idea on when you might be able to pull this new version?
Thank you for your help

Hi @sponch
Did you get this error resolved?
We had this problem with version 3.2.0.
Marcel from Leantime emailed back last night and said he has just released 3.2.1 with a fix.
@nebulon, can you give an idea on when you might be able to pull this new version?

Hi @girish
I would think this is an issue for Taiga to resolve - what is the upgrade path from 6.6 to 6.7.
I will chase this up with them as we currently run two instances of Taiga on different servers and have many many projects that we would have to export.

Hi @girish, yami from Taiga said they have released the PG 14 update in stable branch 6.7.0 and deployed it to their SAAS last week.
She says they are releasing a new image with the latest tag now, so worth checking again

@ei8fdb did you install geo locations for geo tagging your photos?

I recently installed geo, and I have been using memories for a long Time without issues, its a great plugin! So either the recent update killed it or it is the geo locations doing it.

@girish thanks Girish, that's amazing!

I had disabled Memories and NC still wouldn't start.

I did recently install geolocations so Memories coukd worked with locations. I was suspicious that this was the app requiring polygons on Postgres, but I couldn't find anything else about it. It was running for 5 or 6 weeks after that, until the update of NC.

Thanks @girish
I have disabled the apps I think might be linked but I still get not responding - there seem to be lots of things not responding, see list, so I'll open a support ticket

Hi All,

I hope someone can help me, I'm running Cloudron 7.4.2 with Nextcloud 26.01 (4.17.0) and Nextcloud fails to start. In the Event log it shows 'App Down'.

The problem started when I did the reboot in the message - Cloudron requires a reboot - to complete the install of 7.4.2. NC didn't restart. I tried to restart it, but that failed, I increased the memory and that made no difference. Event log showed App ran out of memory. In Cloudron Services Redis showed red, and out of memory so I increased it and restarted the whole server. Nothing helped.

In the logs I could see a db error: "Unknown database type polygon requested, Doctrine\DBAL\Platforms\PostgreSQL"

2023-06-02T07:51:17.000Z files_sharing recognize workflowengine
2023-06-02T07:51:18.000Z
2023-06-02T07:51:18.000Z
2023-06-02T07:51:18.000Z
2023-06-02T07:51:18.000Z Nextcloud is already latest version
2023-06-02T07:51:18.000Z db:convert-filecache-bigint
2023-06-02T07:51:18.000Z In AbstractPlatform.php line 396:
2023-06-02T07:51:18.000Z  
2023-06-02T07:51:18.000Z  
2023-06-02T07:51:18.000Z  100Platform may not support it. 
2023-06-02T07:51:18.000Z  Unknown database type polygon requested, Doctrine\DBAL\Platforms\PostgreSQL 
2023-06-02T07:51:25.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.4:80
2023-06-02T07:51:33.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.4:80

I saw that there was an update to 26.02 (4.17.1) so I applied the update - this has fixed errors in the past. Unfortunately that didn't fix the db issue, and I now see in the logs:

Jun 02 15:19:50 ==> run migration
Jun 02 15:19:50 Nextcloud is in maintenance mode, no apps are loaded.

Any idea how I can recover NC?

Thanks!!!

@girish thanks, I'll chase them next week if they haven't by then

Hi Everyone,
We saw this as we had the same issue and we posted a request with Taiga to get this resolved.
Taiga show the status as Ready to Release...
https://tree.taiga.io/project/taiga/issue/5196
Perhaps this can be put into Cloudron now as we are big users of Taiga and need to keep it up to date, thanks!
Hope this helps.

@robi Hi, I was wondering if you had looked at this since your post back in October?

We have successfully started using XWiki for 2 corporate clients and had very good feedback. We hosted these on non-Cloudron boxes using the official XWiki images.

For one of the clients we ran the Confluence migration process which worked very well for most of the spaces (pages). We had formatting issues with a few pages which we had to fix by copying and pasting the content over. It appears there are ways to avoid this, or get support for the migration, but for us it was easier to fix the pages manually.

So we would really love to have XWiki in Cloudron and enjoy all the benefits that Cloudron brings!

@timconsidine yes, agreed, everyone will always want their own favorite one added.

For us we don't have a favorite yet, but we have a clear requirement for something that is open source, self hosting and is fully featured enough to make it a comprehensive replacement for Confluence.

I may be mistaken, but Wikiss is aimed at a different use case and is does not compete in this space. As @nebulon says it is a lightweight PHP system

@robi Thanks, that would be fantastic!

In the meantime we are using an official docker image of XWiki to see how well it performs and possibly try a migration from one of our Confluence KBs.

@marcusquinn yep, thanks, we tried BS, simple to use and great for smaller projects. Not really suited to our needs in this case

@ruihildt

Although they have many similarities in the things they do they are very different beasts to use. We found Confluence to be much smoother for end users to edit content, users could simply type what they liked, paste content from other documents and retain the formatting. More than one person could edit a document at the same time. What you saw was what would be visible instantly when saved.

I am not a Wiki.js advanced user, but my impressions were very different. Editing documents was much more like creating web content than using. You have to click the edit button, wait for it to display the edit page and then find where you were when you decided to update the content.

When you are done and then there was a long pause to render the page after you publish it, stopping you from working in the meantime - this was on a 16 processor 48GB RAM SSD-NVMe server, so hardware wasn't the issue.

All this is OK for users who consume content or those who statically create content with occasional edits, but not ideal when you want your non-Wiki savvy users to see content that needs correcting and simply want to click in the page where they see the error, change it then save it.

The big challenge for us is persuading our users to contribute and update content. It has to be a slick and pleasant experience.

I run 5 or so live Cloudrons across the businesses I'm responsible for and we've been looking for a replacement Wiki to switch to as we know Confluence on-premise is going away.

When selecting candidates for a project like this I always start by looking at the products on Cloudron,

• firstly because it is quick and easy to install and try them (thanks guys, Cloudron is awesome!)

• secondly because you guys have already gone through a process of vetting out the not so good products - if it has made it to Cloudron is must have merit!

I think where the case requires a larger/more complex use Confluence is a long way ahead of most of the other alternative Wikis already on Cloudron so I looked at a lot of other OS Wikis to find a better option.

XWiki does appear to be everything a larger Wiki needs there is also mention of a Confluence import - an essential tool if anyone is ever to migrate from Confluence with years of knowledge embedded in the platform.

There is also a Docker implementation of XWiki, the trend is now to deploy on Docker.

I was wondering if we are any closer to having XWiki on Cloudron...