Cloudron Forum

Thank you @girish and @marcelfolaron, I updated my test system with the fix and it worked fine, so I have updated production ones too.
That was resolved remarkably quickly and saved me a lot of strife, amazing, thanks again

@nebulon Would you mind checking this?
I see you are working on PHP 8.2 for Leantime

@marcelfolaron can you add your wisdom please
Could our issues be permissions or ports?

Leantime have posted:
Docker configuration updates
Due to the user/group updates on the docker image there is a small chance you run into file permission issues on existing volumes check https://github.com/Leantime/docker-leantime?tab=readme-ov-file#common-issues--solutions for setting the permissions correctly.

Additionally we updated the internal port to be 8080. Please make sure your docker compose files reflect the recent changes

Highlights
For a full list of 3.4 updates see: https://github.com/Leantime/leantime/releases/tag/v3.4.0
==> Fixed date issue in milestone, timesheet, sprint generation <==
Fixed cron handler for long running schedule:work job to be able to run cron jobs in docker
Misc other fixes

I believe the update broke the app, probably when going from 3.4.2 to 3.4.3. (but it could have been earlier and not spotted)
Looking into the upgrade process I see there are three issues:

1. Changes in permissions - related to changes in Docker configuration updates - probably responsible for the bland 'Server error' issue
2. Internal port changed to 8080, probably responsible for the ECONNREFUSED 172.18.16.53:8080 issue
3. PHP 8.2 required, Laravel no longer supports 8.1 - no idea if this is an issue, are we on 8.2 already?

Hi all,
Leantime is only partially functional after upgrade to 3.4. For example you get 'Server Error' when trying to add a milestone.
The logs show various errors after restarting the app.
E.g. Healtheck error: Error: connect ECONNREFUSED 172.18.16.53:8080
This is consistent across 2 installations on different boxes, clients and domains.
The normal restart, reboot etc do not fix the errors.
Restoring a backup to a fresh install on a different VM did not either.

Hi, sorry, I missed your question, yes @jdaviescoates is correct Marcel is.

If you need a license to integrate this I'm sure Marcel will oblige.
As it is an additional cost option, would you approach this in the same way as Cloudron did for FreeScout, where by default it installs with the app managing its own users, unless the license is purchased?

Hi @nebulon I think the app does support OIDC, at least according to this article https://marketplace.leantime.io/product/installation-auth-provider/
Choice of LDAP (OL or AD), OIDC or Google SSO. Works with the open source installation: https://marketplace.leantime.io/product/leantime-open-source-installation/

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