Cloudron Forum

@nebulon I restored the server from a backup, as it must be working at this time.
I don't have Vaultwarden installed. Only redmine and a couple of other applications.
I sent the ticket to support.

@Grienauer I think Services -> Mail -> Restart. This updates the mail server certs. Can you check if it works after that?

@subven thx for your input!

@Grienauer said in app does not respond. statping-ng replacement possible?:

As the cloudron was updated to statping-ng… what steps should be done to do this for my old version?

This has not been done yet, I am yet to find the time to switch it.

Can we revisit this? Allowing some code in the (html) header of all apps would be enough, I think (and awesome)

Screenshot: Bye bye DeckDeckGo ... is now deprecated

The MySQL+SSH tunnel info is here - https://forum.cloudron.io/topic/3237/remote-sql-support-on-a-per-app-basis . If you are feeling brave (I don't recommend this at all), there are some socat tricks I posted a while ago - https://forum.cloudron.io/topic/3237/remote-sql-support-on-a-per-app-basis

So, all our mautic instances updated fine. Some of the themes might have to be removed manually since it seems the config.json changed from mautic 3 to mautic 4.

If some pages error, check the logs in System info i.e the Logs view in https://mautic.domain.com/s/sysinfo. You might see an error in the logs like so:

[2022-01-25 15:07:18] mautic.CRITICAL: Uncaught PHP Exception Mautic\CoreBundle\Exception\BadConfigurationException: "Theme Blank not configured properly: builder property in the config.json" at /app/code/app/bundles/CoreBundle/Helper/ThemeHelper.php line 673 {"exception":"[object] (Mautic\\CoreBundle\\Exception\\BadConfigurationException(code: 0): Theme Blank not configured properly: builder property in the config.json at /app/code/app/bundles/CoreBundle/Helper/ThemeHelper.php:673)"} []

To fix the above, open the file manager:

Go to themes directory Delete the blank-grapejs and confimme (sic) theme directories. You might have to delete more directories depending on the error messages you see. The above error gives a hint as to what theme is causing a problem ("Theme Blank not configured properly")

Thanks @luckow for helping us debug.

@grienauer
When I did my testing for the Valheim Server App I wrote this script to make testing easier.

Note tho, this only works when not using any addons, but localstorage works with the local mount.

#!/bin/bash # Function to get the user to input the needed vars get_vars () { read -p "Cloudron E-Mail: " EMAIL read -p "Cloudron Username: " USERNAME read -s -p "Cloudron Password: " PASSWORD read -p "Cloudron URL: " CLOUDRON_URL read -p "DOCKER REPOSITORY URL: " DOCKER_REPOSITORY_URL read -p "DOCKER USERNAME: " DOCKER_REPOSITORY_USERNAME read -p -s "DOCKER PASSWORD: " DOCKER_REPOSITORY_PASSWORD printf "EMAIL=$EMAIL\n USERNAME=$USERNAME\n PASSWORD=$PASSWORD\n CLOUDRON_URL=$CLOUDRON_URL\n DOCKER_REPOSITORY_URL=$DOCKER_REPOSITORY_URL\n DOCKER_REPOSITORY_USERNAME=$DOCKER_REPOSITORY_USERNAME\n DOCKER_REPOSITORY_PASSWORD=$DOCKER_REPOSITORY_PASSWORD\n " > .env } # check if .env file exists and read it or check if vars exsist if [ -f ".env" ]; then export $(egrep -v '^#' .env | xargs) &> /dev/null else echo ".env File missing - asking for required vars" get_vars fi if [ -z "$EMAIL" ] || [ -z "$USERNAME" ] || [ -z "$PASSWORD" ] || [ -z "$CLOUDRON_URL" ] || [ -z "$DOCKER_REPOSITORY_URL" ] || [ -z "$DOCKER_REPOSITORY_USERNAME" ] || [ -z "$DOCKER_REPOSITORY_PASSWORD" ]; then echo "some vars are empty - asking for required vars" get_vars fi echo "=> Login Docker" docker login --username $DOCKER_REPOSITORY_USERNAME --password $DOCKER_REPOSITORY_PASSWORD $DOCKER_REPOSITORY_URL echo "=> Login Cloudron" cloudron login --username $USERNAME --password $PASSWORD my.$CLOUDRON_URL set -x # Get the ID and VERSION from the CloudronManifest.json ID=$(jq -r ".id" CloudronManifest.json) VERSION=$(jq -r ".version" CloudronManifest.json) echo "=> Create Test Data dir" mkdir -p ./cloudron_test/data ./cloudron_test/tmp ./cloudron_test/run echo "=> Cleanup Test Data" rm -rf ./cloudron_test/data/* ./cloudron_test/tmp/* ./cloudron_test/run/* echo "=> Build test image" cloudron build --set-repository $DOCKER_REPOSITORY_URL/$ID # docker build -t $DOCKER_REPOSITORY_URL/$ID:$VERSION . if [[ RUN_IMG = "" ]]; then read -p "Do you want to run the image created image?: (y/N)" RUN_IMG fi if [[ "$RUN_IMG" = "y" || "$RUN_IMG" = "Y" ]]; then echo "=> Run `test` tag of build image" docker run -ti --read-only \ --volume $(pwd)/cloudron_test/data:/app/data:rw \ --volume $(pwd)/cloudron_test/tmp:/tmp:rw \ --volume $(pwd)/cloudron_test/run:/run:rw \ $DOCKER_REPOSITORY_URL/$ID:$VERSION \ bash fi echo "=> Running tests" cd test echo "=> Running ncu - updating deps" ncu -u npm -i echo "=> Installing package.json" npm install if [[ -f ./node_modules/.bin/mocha ]]; then ./node_modules/.bin/mocha ./test.js -b fi if [[ -f ../node_modules/.bin/mocha ]]; then ../node_modules/.bin/mocha ./test.js -b fi # remove installed test instance echo "Cancel now if you wish to keep the app installed" sleep 10 cloudron uninstall --app test.$CLOUDRON_URL

@grienauer nice. See also https://docs.growthbook.io/self-host

There is still a great area, right after My Apps to show the total state of your Cloudron.

For ex:
My Apps %(#00ff00)[33]/%(#c5d500)[1]/%(#ff0000)[0]

Meaning 33 running, 1 stopped, 0 not responding

We are using minIO for it. s3 compatible. the Service on our side was down… and then we also have a problem with backup size. but now it works! thx!

@grienauer You can set this thread to "solved" yourself.

@grienauer ah well spotted! I've set the correct icon now. Thanks

@thetomester13 yes. it is about the privatebin templates, but I think it is also tricky to update these because hash-check-values for js files etc… I tested it and they will now be picked up.

I checked it now. after a new update, it is already broken. a custom theme should also have the js hash numbers to verify and after an update these (or something else changes and the new template does not work any more. so custom themes are not a good idea in the actual state of the module, how it works now. someone has to dig deeper into it to find maybe a proper solution. for now I would say, it is not a good idea to do so, like nebulon suggested already and I have now the proof for that 😜

@thetomester13 thx for the help!
I tested your plugin and it worked and is visible under preferences… thx for the hint/proof… now I know that at least the plugin folder/mapping works!

Check. sorry for that. It seems I had here a big knot in my brain.
Works as designed!