Hi @atridad,
I discovered I needed to make the following change in the start.sh file to get forgot password emails working.

export PUBLIC_URL="$CLOUDRON_APP_ORIGIN"

cheers
Mark

Great. Thanks @atridad!

Thanks @atridad. I've now got it running.

Hi @atridad, thanks for providing such a wonderful resource. I'm trying to use your directus instance but its hanging on the health check. (This is my first time trying to run a custom cloudron app so I may be doing something silly.)

I was hoping you could help me out in case there is something obviously wrong. App part of the logs are below -

Jul 29 13:15:43 Fresh installation, setting up data directory...
Jul 29 13:15:44 Cannot find module '@directus/shared/utils/node'
Jul 29 13:15:44 Require stack:
Jul 29 13:15:44 - /app/code/node_modules/directus/dist/extensions.js
Jul 29 13:15:44 - /app/code/node_modules/directus/dist/services/graphql.js
Jul 29 13:15:44 - /app/code/node_modules/directus/dist/services/index.js
Jul 29 13:15:44 - /app/code/node_modules/directus/dist/utils/get-schema.js
Jul 29 13:15:44 - /app/code/node_modules/directus/dist/cli/commands/bootstrap/index.js
Jul 29 13:15:44 - /app/code/node_modules/directus/dist/cli/index.js
Jul 29 13:15:44 - /app/code/node_modules/directus/cli.js
Jul 29 13:15:26 Generating SSL certificate
Jul 29 13:15:26 Generating a RSA private key
Jul 29 13:15:26 ....+++++
Jul 29 13:15:27 ...................................+++++
Jul 29 13:15:27 writing new private key to '/run/redis.cloudron.key'
Jul 29 13:15:27 -----
Jul 29 13:15:27 Starting supervisor
Jul 29 13:15:27 2021-07-29 03:15:27,375 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
Jul 29 13:15:27 2021-07-29 03:15:27,375 INFO Included extra file "/etc/supervisor/conf.d/redis-service.conf" during parsing
Jul 29 13:15:27 2021-07-29 03:15:27,375 INFO Included extra file "/etc/supervisor/conf.d/redis.conf" during parsing
Jul 29 13:15:27 2021-07-29 03:15:27,387 INFO RPC interface 'supervisor' initialized
Jul 29 13:15:27 2021-07-29 03:15:27,387 CRIT Server 'inet_http_server' running without any HTTP authentication checking
Jul 29 13:15:27 2021-07-29 03:15:27,387 INFO RPC interface 'supervisor' initialized
Jul 29 13:15:27 2021-07-29 03:15:27,387 CRIT Server 'unix_http_server' running without any HTTP authentication checking
Jul 29 13:15:27 2021-07-29 03:15:27,388 INFO supervisord started with pid 1
Jul 29 13:15:28 2021-07-29 03:15:28,390 INFO spawned: 'redis' with pid 16
Jul 29 13:15:28 2021-07-29 03:15:28,392 INFO spawned: 'redis-service' with pid 17
Jul 29 13:15:28 16:C 29 Jul 2021 03:15:28.407 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Jul 29 13:15:28 16:C 29 Jul 2021 03:15:28.407 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=16, just started
Jul 29 13:15:28 16:C 29 Jul 2021 03:15:28.407 # Configuration loaded
Jul 29 13:15:28 16:M 29 Jul 2021 03:15:28.413 * Running mode=standalone, port=6379.
Jul 29 13:15:28 16:M 29 Jul 2021 03:15:28.414 # Server initialized
Jul 29 13:15:28 16:M 29 Jul 2021 03:15:28.414 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Jul 29 13:15:28 16:M 29 Jul 2021 03:15:28.415 * Ready to accept connections
Jul 29 13:15:28 Redis service endpoint listening on https://:::3000
Jul 29 13:15:29 2021-07-29 03:15:29,747 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Jul 29 13:15:29 2021-07-29 03:15:29,747 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Jul 29 13:15:41 [GET] /healthcheck
Jul 29 13:15:42 Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.

thanks
Mark

Hi All,
Looking at the Redash forums the devs have indicated a number of times that the latest beta - 9.0.0-beta.b42121 is also the production version.

There doesn't seem much inclination at their end to create a new prod tag using the same beta baseline.

Is it possible to allow the use of this version in Cloudron?

It's apparently what they're using in the redash hosted offering. So it would seem to be production ready.

There are a number of features in 9.0 that would be very useful to me on my cloudron instances.

Thanks
Mark

Hi @atridad,
I discovered I needed to make the following change in the start.sh file to get forgot password emails working.

export PUBLIC_URL="$CLOUDRON_APP_ORIGIN"

cheers
Mark

Thanks @atridad. I've now got it running.

Great. Thanks @atridad!

Hi @atridad, thanks for providing such a wonderful resource. I'm trying to use your directus instance but its hanging on the health check. (This is my first time trying to run a custom cloudron app so I may be doing something silly.)

I was hoping you could help me out in case there is something obviously wrong. App part of the logs are below -

Jul 29 13:15:43 Fresh installation, setting up data directory...
Jul 29 13:15:44 Cannot find module '@directus/shared/utils/node'
Jul 29 13:15:44 Require stack:
Jul 29 13:15:44 - /app/code/node_modules/directus/dist/extensions.js
Jul 29 13:15:44 - /app/code/node_modules/directus/dist/services/graphql.js
Jul 29 13:15:44 - /app/code/node_modules/directus/dist/services/index.js
Jul 29 13:15:44 - /app/code/node_modules/directus/dist/utils/get-schema.js
Jul 29 13:15:44 - /app/code/node_modules/directus/dist/cli/commands/bootstrap/index.js
Jul 29 13:15:44 - /app/code/node_modules/directus/dist/cli/index.js
Jul 29 13:15:44 - /app/code/node_modules/directus/cli.js
Jul 29 13:15:26 Generating SSL certificate
Jul 29 13:15:26 Generating a RSA private key
Jul 29 13:15:26 ....+++++
Jul 29 13:15:27 ...................................+++++
Jul 29 13:15:27 writing new private key to '/run/redis.cloudron.key'
Jul 29 13:15:27 -----
Jul 29 13:15:27 Starting supervisor
Jul 29 13:15:27 2021-07-29 03:15:27,375 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
Jul 29 13:15:27 2021-07-29 03:15:27,375 INFO Included extra file "/etc/supervisor/conf.d/redis-service.conf" during parsing
Jul 29 13:15:27 2021-07-29 03:15:27,375 INFO Included extra file "/etc/supervisor/conf.d/redis.conf" during parsing
Jul 29 13:15:27 2021-07-29 03:15:27,387 INFO RPC interface 'supervisor' initialized
Jul 29 13:15:27 2021-07-29 03:15:27,387 CRIT Server 'inet_http_server' running without any HTTP authentication checking
Jul 29 13:15:27 2021-07-29 03:15:27,387 INFO RPC interface 'supervisor' initialized
Jul 29 13:15:27 2021-07-29 03:15:27,387 CRIT Server 'unix_http_server' running without any HTTP authentication checking
Jul 29 13:15:27 2021-07-29 03:15:27,388 INFO supervisord started with pid 1
Jul 29 13:15:28 2021-07-29 03:15:28,390 INFO spawned: 'redis' with pid 16
Jul 29 13:15:28 2021-07-29 03:15:28,392 INFO spawned: 'redis-service' with pid 17
Jul 29 13:15:28 16:C 29 Jul 2021 03:15:28.407 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Jul 29 13:15:28 16:C 29 Jul 2021 03:15:28.407 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=16, just started
Jul 29 13:15:28 16:C 29 Jul 2021 03:15:28.407 # Configuration loaded
Jul 29 13:15:28 16:M 29 Jul 2021 03:15:28.413 * Running mode=standalone, port=6379.
Jul 29 13:15:28 16:M 29 Jul 2021 03:15:28.414 # Server initialized
Jul 29 13:15:28 16:M 29 Jul 2021 03:15:28.414 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Jul 29 13:15:28 16:M 29 Jul 2021 03:15:28.415 * Ready to accept connections
Jul 29 13:15:28 Redis service endpoint listening on https://:::3000
Jul 29 13:15:29 2021-07-29 03:15:29,747 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Jul 29 13:15:29 2021-07-29 03:15:29,747 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Jul 29 13:15:41 [GET] /healthcheck
Jul 29 13:15:42 Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.

thanks
Mark

Thanks, Girish. I'm happy to test it once you've got it running if that helps?

Hi All,
Looking at the Redash forums the devs have indicated a number of times that the latest beta - 9.0.0-beta.b42121 is also the production version.

There doesn't seem much inclination at their end to create a new prod tag using the same beta baseline.

Is it possible to allow the use of this version in Cloudron?

It's apparently what they're using in the redash hosted offering. So it would seem to be production ready.

There are a number of features in 9.0 that would be very useful to me on my cloudron instances.

Thanks
Mark

Thanks Nebulon. I'll follow up with the team administering the db tomorrow. Using the nc command directly from the server running cloudron, I'm not getting an acknowledgement. So i'm hoping it's an issue at their end.

While the initial request will be outgoing, the db will respond on port 1433 as well won't it?

I can probably get help to get the logs, but it's a third party who manages the db so I'd prefer to rule out the obvious before I go down that path.

So is there something I need to configure to open up 1433 for redash?

Hi,
I'm currently trying to connect to a remote Sql Server DB on port 1433 (the default). I've had this port opened for my cloudron servers IP, but I still can't connect successfully.

Do I need to add port 1433 in some configuration somewhere to open this port for redash/sql server?

Thanks
Mark

Thanks, Girish,
That patch worked. I've successfully setup things.
cheers
Mark