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.

I have opened up a request to get Spectre importer added as an app, please up vote if your still interested in that feature.

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:

• TLS server certificates must contain an ExtendedKeyUsage (EKU) extension containing the id-kp-serverAuth OID.
• TLS server certificates must have a validity period of 825 days or fewer (as expressed in the NotBefore and NotAfter fields of the certificate).

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).

Relevant links:

• Download page which includes docker image instructions
• Docker hub image maintained by Camunda
• Relevant documentation on configuring LDAP authentication for integrated user management
  • The LDAP Identity and Administrator Authorization plugins are already included in the Docker image
• Administrator Authorization plugin which would be used to make Cloudron Admin's Camunda admins
• Process engine configuration needed for the Comunda process engine to use the Cloudron email relay
  • Email configuration is also mentioned here but it is in the context of new user email notifications which wouldn't be relevant if identity management is handled by Cloudron
• No state information for Camunda is in containers
• Docker container has runtime parameters to configure either MySQL or PostgreSQL database connection information
  • Documentation on other database parameters that can be passed to the container and example configuration using PostgreSQL

@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?

Relevant links:

• Download page which includes docker image instructions
• Docker hub image maintained by Camunda
• Relevant documentation on configuring LDAP authentication for integrated user management
  • The LDAP Identity and Administrator Authorization plugins are already included in the Docker image
• Administrator Authorization plugin which would be used to make Cloudron Admin's Camunda admins
• Process engine configuration needed for the Comunda process engine to use the Cloudron email relay
  • Email configuration is also mentioned here but it is in the context of new user email notifications which wouldn't be relevant if identity management is handled by Cloudron
• No state information for Camunda is in containers
• Docker container has runtime parameters to configure either MySQL or PostgreSQL database connection information
  • Documentation on other database parameters that can be passed to the container and example configuration using PostgreSQL

I am trying to only do this from the Cloudron hosted versions of Metabase/Grafana.

I followed your instructions and this worked perfectly, took the username, password, port, host, and database name from the environment variables within the Wekan web console, entered them in Metabase, and was able to connect and see the data.

Thank you!

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?

@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 have opened up a request to get Spectre importer added as an app, please up vote if your still interested in that feature.

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:

• TLS server certificates must contain an ExtendedKeyUsage (EKU) extension containing the id-kp-serverAuth OID.
• TLS server certificates must have a validity period of 825 days or fewer (as expressed in the NotBefore and NotAfter fields of the certificate).

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).

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.