Currently if you want to automatically import bank transactions into Cloudron hosted Firefly III you need to run and manage an instance of Spectre importer.
There is a docker image for this application maintained by the application's developers which will hopefully make integrating this easier.
Having the ability to host Spectre importer and Firefly III self hosted on Cloudron would allow it to work as a replacement to services like Mint.
This may be something that I just need to learn better but I tried to manually update apps over the last few days by clicking the update button for the individual app tiles and each time it would start and then look like it finished but no update took place.
I eventually figured out today that this was due to the mount point where backups are sent not being available and after fixing that updates complete as expected but before this point they were failing silently when manually triggered.
I am not sure where I would look to see the reasons the update failed as the app's logs don't show anything and the Cloudron event log shows the update being triggered but doesn't show anything indicating that the update failed and subsequently why it failed.
I just watched the BayLISA presentation on Cloudron and saw it mentioned that they do Selenium tests of the applications on each release so I have updated my original post to include a link to Camunda's own maintained selenium based web application tests.
I have opened up a request to get Spectre importer added as an app, please up vote if your still interested in that feature.
Relevant links:
I have saved and then followed these steps for installing a certificate once it has been sent to a iOS 13.7 iPhone (in my case I used iCloud storage and the Files app to get the certificate onto the device.
After these steps have been completed you should be able enable trust for this certificate like this.
I have also used the iMazing profile editor to create a profile with the auto generated self signed wildcard certificate in case that made a difference.
In all cases the certificate doesn't show up under the "Enable full trust for root certificates" heading on the Settings > General > About > Certificate Trust Settings screen.
Apple published new requirements for certificates that can be trusted in iOS 13 and above.
All of the first set of requirements appear to be met but the last section's bullets appear to be where the problems are:
Additionally, all TLS server certificates issued after July 1, 2019 (as indicated in the NotBefore field of the certificate) must follow these guidelines:
At present it appears that it is not possible for an updated iOS device to trust the automatically generated self signed certificate created by Cloudron.
This blog article provides steps that work, part of the issue being the requirement to have a separate CA cert that is then used to generate the TLS Web Server Authentication cert that ultimately is used for the tls connections.
Beyond that it also appears that the 10 year life time on the certificate would have to be reduced to 825 days or less (~2.26 years).
@girish Sorry for the late reply, I the default forum settings were to send me email notifications once a week, I have changed that to daily.
I was trying to use the self-signed certificate for all apps.
I have gone ahead and followed the steps in the blog article I linked to and was able to upload the full CA and web server cert chain to Cloudron and after getting the root certificate authority into all the devices accessing Cloudron everything is working well from Windows and iOS based devices.
It looks like Apple is going to be decreasing the certificate lifetime further down to 398 days so you may want to lower the lifetime down to a year to get ahead of that change.
I would like to create some Kanban based dashboards, like cumulative flow diagrams, cycle time reporting, etc. using the data in the Mongo DB instance used by Wekan.
I believe I can create the dashboard I would like using Metabase and/or Grafana with the Wekan Mongo DB instance as the datasource.
What would be the right way to go about exposing the Mongo DB instance used by Wekan to inbound connections from Metabse and/or Grafana?
@nebulon Nice, your absolutely right.
Both are crashing over and over but by the looks of it for different reasons.
I will start a separate threads about those issues but you solved the last mystery here, first issue was terminal not loading after update due to browser cache, 2nd issue is the apps are actually crashing over and over and that is why the terminal keeps resetting.
Thanks for your help!
@girish Good thinking, yes that appears to be the behavior, if the smtp server rejects the connection the app refuses to start.
This may be something that I just need to learn better but I tried to manually update apps over the last few days by clicking the update button for the individual app tiles and each time it would start and then look like it finished but no update took place.
I eventually figured out today that this was due to the mount point where backups are sent not being available and after fixing that updates complete as expected but before this point they were failing silently when manually triggered.
I am not sure where I would look to see the reasons the update failed as the app's logs don't show anything and the Cloudron event log shows the update being triggered but doesn't show anything indicating that the update failed and subsequently why it failed.
@girish Good thinking, yes that appears to be the behavior, if the smtp server rejects the connection the app refuses to start.
@nebulon based on the current design I think the cleanest way to handle this is to change the behavior of Cloudron to be that when Outbound Email Relay configuration for a domain is set to disabled the smtp daemon referenced in the app containers via the environment variable CLOUDRON_MAIL_SMTP_SERVER continues to accept mail from applications and then deletes/routes all mail it receives to /dev/null (how to accomplish this would be dependent on the smtp daemon used).
This would allow individual apps not to have to have configuration changes based on whether email is enabled or not.
The other maybe more correct but difficult option is to change the state visible to the app container if Email Relay is set to disabled. This could be by no longer setting the various SMTP related environment variables so that the start.sh scripts can check for the presence of the variables before trying to use their values in configuration files.
The app state change option requires that each app's start.sh has to account for this configuration possibility and then change the app's configuration based on that whereas the first option allows all apps configuration to remain consistent independent of whether Email Relay is disabled or not.
The cloudron user and group are not set as the owner of the /app/data directory and subdirectories which results in the following error being logged and the app to keep restarting:
Dec 10 09:08:05 => Creating config file on first run
Dec 10 09:08:05 cp: cannot create regular file '/app/data/config/prometheus.yml': Permission denied
Changing the ownership manually resolved the issue and allowed the app to start.
After copying /app/pkg/start.sh to /app/data/start.sh I commented out the lines that set the smtp server configuration and saved start.sh.
I then commented out the smtp section of the /app/data/production.yaml file.
From /app/code/server I was then able to run /app/data/start.sh and the server started up properly:
root@d2fb1510-462d-45d0-84b8-8143184152fc:/app/code/server# /app/data/start.sh
==> Updating Ldap credentials
UPDATE 0
==> Updating configs
==> Starting PeerTube
> peertube@2.4.0 start /app/code/server
> node dist/server
[peertube.cloudron.magnusonfinancial.com:443] 2020-12-10 14:02:20.940 warn: Emailer is disabled so the contact form will not work.
[peertube.cloudron.magnusonfinancial.com:443] 2020-12-10 14:02:21.319 info: Database dbd2fb1510462d45d084b88143184152fc is ready.
[peertube.cloudron.magnusonfinancial.com:443] 2020-12-10 14:02:21.455 error: Cannot use SMTP server because of lack of configuration. PeerTube will not be able to send mails!
[peertube.cloudron.magnusonfinancial.com:443] 2020-12-10 14:02:21.464 info: Cleaning HTML cache.
[peertube.cloudron.magnusonfinancial.com:443] 2020-12-10 14:02:21.507 info: Server listening on 0.0.0.0:9000
Based on this it seems like this app breaks if cloudron's outbound SMTP configuration is set to disabled.
@nebulon What do I do to report this as an issue and request the package be updated, is this message here enough or should I start a thread in the Support section of the forum, or something else?
@christophermag I have tried to comment out the section of start.sh for this app that writes the smtp server configuration into the production.yaml so I can confirm that the smtp server not responding is the cause of this issue but start.sh is in a read only file system.
Running start.sh from /app/pkg/ results in an error message as it is looking for a package.json file.
Changing to /app/code/server and then executing /app/pkg/start.sh results in the server trying to start and getting the smtp error messages from the first post.
Will now try to copy start.sh somewhere and see if a modified version that doesn't set smtp server config in the production.yaml along with commenting that config out of production.yaml allows me to start peertube.
@christophermag I had to delete an appended section of smtp configuration from the end of the file and uncomment out the original smtp section and now the app tries to start and gets the error messages from the first post.
@christophermag It looks like the 2nd output is due to me corrupting the production.yaml as the start.sh script overwrites parts of it so my manual modifications conflicted.
Currently trying to get back to a properly formatted production.yaml but the first set of logs in the thread are the ones related to the real problem and not the one I caused by modifying production.yaml while not in recovery mode.
After commenting out the smtp and email sections of the production.yaml I now get the following:
Dec 10 08:18:09 ==> Updating Ldap credentials
Dec 10 08:18:09 UPDATE 0
Dec 10 08:18:09 ==> Updating configs
Dec 10 08:18:09 ==> Starting PeerTube
Dec 10 08:18:09
Dec 10 08:18:09 > peertube@2.4.0 start /app/code/server
Dec 10 08:18:09 > node dist/server
Dec 10 08:18:09
Dec 10 08:18:09 internal/fs/utils.js:230
Dec 10 08:18:09 throw err;
Dec 10 08:18:09 ^
Dec 10 08:18:09
Dec 10 08:18:09 Error: ENOENT: no such file or directory, mkdir '/app/code/server/storage/logs'
Dec 10 08:18:09 at Object.mkdirSync (fs.js:841:3)
Dec 10 08:18:09 at Object.module.exports.makeDirSync (/app/code/server/node_modules/fs-extra/lib/mkdirs/make-dir.js:101:15)
Dec 10 08:18:09 at Object.<anonymous> (/app/code/server/dist/server/helpers/logger.js:11:12)
Dec 10 08:18:09 at Module._compile (internal/modules/cjs/loader.js:1156:30)
Dec 10 08:18:09 at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10)
Dec 10 08:18:09 at Module.load (internal/modules/cjs/loader.js:1000:32)
Dec 10 08:18:09 at Function.Module._load (internal/modules/cjs/loader.js:899:14)
Dec 10 08:18:09 at Module.require (internal/modules/cjs/loader.js:1042:19)
Dec 10 08:18:09 at require (internal/modules/cjs/helpers.js:77:18)
Dec 10 08:18:09 at Object.<anonymous> (/app/code/server/dist/server/initializers/checker-before-init.js:7:18) {
Dec 10 08:18:09 errno: -2,
Dec 10 08:18:09 syscall: 'mkdir',
Dec 10 08:18:09 code: 'ENOENT',
Dec 10 08:18:09 path: '/app/code/server/storage/logs'
Dec 10 08:18:09 }
Dec 10 08:18:09 npm ERR! code ELIFECYCLE
Dec 10 08:18:09 npm ERR! errno 1
Dec 10 08:18:09 npm ERR! peertube@2.4.0 start: `node dist/server`
Dec 10 08:18:09 npm ERR! Exit status 1
Dec 10 08:18:09 npm ERR!
Dec 10 08:18:09 npm ERR! Failed at the peertube@2.4.0 start script.
Dec 10 08:18:09 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Dec 10 08:18:09