Cloudron Forum

@nebulon It would be awesome if Cloudron could integrate the 'Suite Numérique' apps! In France, this suite is gaining a lot of traction and is being rolled out everywhere. Being able to deploy it easily thanks to Cloudron would be a massive advantage. I’m not sure how feasible it is or if all these apps are suitable for Cloudron packaging, but it would definitely be a game-changer.

Hi @nebulon , Thanks for investigation, but I'm sorry i don't think it's the explanation. On friday we were able to reproduce the behavior just by going to the "/.well-known/openid-configuration" from our browsers but also from the server itself with wget, excluding any external network issue. Your troubleshooting report tool also report same issue with some other path, the openid path is only the best one to see the issue. The explanation of occasional timeouts is probably because the server has not many users and many apps do not require re-login or other path that has issue. Finally, even if heavy load is the explanation, we do not change our habits, so were does it come from ? How to avoid that ? All the server load statistics are very good, and i made some test few minutes ago the url just always timeout even locally with wget. edit: # wget http://127.0.0.1/ is timeouting too

So I was trying to reproduce this issue and got the .ics file with all those about 600 birthday events. However those all have the same UID, so they do map to the very same event in the end. Not sure if this was because of sanitizing the list or if this was related to some other problem. All in all I am not able to reproduce the disappearance though

The app is using an ip database which is behind an auth endpoint. We have added a work item to add a way for users to update the database with custom maxmind credentials

@robi I’m already on the latest LTS Ubuntu version. Do you have some links of other issues, I didn’t find them with the search.

Hello @valexico @Valexico said: So, should we do something to restore our cloudron to nominal configuration ? Recreate this cloudron.conf file somehow ? That would be best I think. If this would reproduce the previous issue, that be interesting to get an understanding what is causing this. The default content from /etc/systemd/system/docker.service.d/cloudron.conf is: [Service] ExecStart= ExecStart=/usr/bin/dockerd -H fd:// --log-driver=journald --exec-opt native.cgroupdriver=cgroupfs --storage-driver=overlay2 --experimental --ip6tables --userland-proxy=false

Ok I did restore a previous state and then proceeded to update. This instance was not critical so no data loss

@james said: Hello @apesorguk That is a good idea. Nextcloud apps are a notorious offender in breaking Nextcloud setups. Totally agree, we have said to nextcloud that they should not release updates and apps until tested with all other apps. They need to get rid of untested apps as well.

@ekevu123 said: This is fixed in the next release coming up today! It is brilliant to have the developer on Cloudron! Thank you, @ekevu123

I am not against AI content, if the quality is good.