Cloudron Forum

Seconding the call for support. I'd love to get this up and running eventually.

@girish Thank you, that did the trick! Not entirely sure how and why my install looked the way it did. I think I installed it first thing once it showed up in the app store, but back then it was still marked as unstable. Anyway, it's all good now, thank you!

Hello! I've discussed this before in the chat, and would just like to start a discussion around that topic again. I'm currently using Cloudron to run a few websites on different domains. In order to make www.example.com work for websites that run at example.com, I've set up LAMP apps for each of those, then have a redirect inside those redirecting to the naked domain. This is currently the only workaround to not get an SSL warning when accessing the www.example.com address.

My plan is the basic one, and from the pricing table I see that it's capped at 20 apps. I'm currently still under 20, but I'm guessing that sooner or later I might go over 20, at which time I need to think about how to deal with the fact that I'm basically running an additional app for every extra domain I've attached to my Cloudron.

Now, what are the chances that at some point, when setting up an app, we will have the ability to simply add a subdomain like www to redirect to the actual naked domain, without having to work around this by setting up a separate LAMP app? That would make both the setup easier and lower the number of used apps on the Cloudron.

I've noticed that for the past few weeks, some apps don't update successfully, and then display "error" as their status. While the apps are still running fine, despite the error status, it seems the update process failed with error messages like this one:

An error occurred during the update operation: Docker Error: Unable to pull image cloudron/io.n8n.cloudronapp:202411271257520000. Please check the network or if the image needs authentication. statusCode: 500

It's happening to n8n, ghost, and a few others.

Running the update process again manually usually solves it, until the next time an update is available.

Any ideas?

I second this. Would be great to use this as a Goodreads alternative.

@jdaviescoates Thank you! Apparently it was one of my plugins, but they needed to be deactivated manually, simply renaming the folder didn't work. I guess I'm gonna do that with my other installs now and see which one it is there that breaks the site.

@girish said in IPv6 for Mastodon - how?:

@stormgrass This one - https://docs.digitalocean.com/products/networking/ipv6/how-to/enable/#on-existing-droplets . Did you do this?

Ah, no, that point I missed. Am trying to fix it now, but the yaml indicated in the doc doesn't exist. So, I've created it and get hit with a syntax error, even though it's a copy of the contents specified.

Anyway, I'll keep investigating, but I think you can mark this as resolved now. Thank you!