Cloudron Forum

And we're all back up. Thanks for the quick response.

Yes, I found this post, and following the advice . .

appears to be doing the trick, now rebooting . . finger crossed.

Found a clue.

"Flag --graph has been deprecated . . "

I received an alert from community members telling me that the server is down.

Docker engine has failed to start.

systemctl status box shows that Cloudron is running.

What do I do??

I believe that Linode automatically updated Ubuntu to 22.04 . . because I installed the version, which Cloudron recommended.

What's your favorite VPS provider?

I've been happily using Linode, but not excited about the Akamai acquisition . .

Epik.com has been the go-to for me

Hello Cloudron community,
please share your experiences with Jitsi:

• How large of conference calls have you achieved?

• What was your experience with latency and call quality among larger groups?

• What limitations have you discovered while hosting large conference calls?

• What recommendations can you make for accommodating large conference calls?

. . .
Personally, my results have been excellent, however I have only tested with small conference calls of 2 to 3 individuals.

However, my client is having intermittent trouble connecting more than 2 callers. The client's intention is to host educational conference calls with tens or hundreds of callers. Is this a reasonable expectation? Further, the client's Jitsi instance is running on well equipped hardware on a Comcast Business internet connection. Any recommendations for improving connectivity will be greatly appreciated. Note: the Memory Allocation for the application is currently set to 1.45Gb although there are 16Gb available total on the hardware. I am increasing now to 12Gb.

Any further advise will be greatly appreciated.

@robi, very cool.

Usually, when I spend enough time getting familiar with the applications, I find that the Cloudron team has already dialed it in.

Will keep this in mind

It seems like the only / best way of modifying core files is adapting the Dockerfile and building a new image, as per the instructions here: https://forum.cloudron.io/topic/3102/building-custom-packages

Move the files from origin location to /app/data and replace with symlinks.

@frei I think you just read my mind . .

Trying to figure out the best practices for modifying core templates (eg, content-cta.hbs) without overwriting upon update.

Correction:

The content-cta.hbs is easily editable --as written directly in Ghost documentation.

Simply reference the default template, modify, and copy to the partials folder.

@abargel

Ghost is far more stable than Grav. It's easier to modify the style using Ghost/Handlebars vs. Grav/PHP/Twig (which was a total mess).

Also, if you have any authors who are not you (not technically highly proficient), then they can easily crash your Grav instance --I have yet to crash Ghost.

That's my two cents.

Thanks @nebulon for getting me seeking in the right direction. Found the answer:

WePay has changed their policy, they no longer support our self host users

That's why it works via invoicing.co but not self-hosted. Closed.

Alternatively, I'm seeing that Checkout.com & GoCardless.com make a pretty strong pair of payment providers,
and those appear to be integrating perfectly with the latest Invoice Ninja build.

Ok, I see the expected behavior, when setting up Invoice Ninja via Invoicing.co.

Everything looks identical to the hosted Invoice Ninja instance (which is great!), except for that the Payment Gateway Providers list is missing WePay as an option.

Yet, again, it looks like the Cloudron team has done a lot of work to set up WePay gateway, so I'm wondering:
Is there anything that we can do to make this option available?

Hello Cloudron community,

Does anyone have experience using WePay with Invoice Ninja within the context of latest Cloudron?
Invoice Ninja's articles on WePay claims that they integrate very well, and I'm seeing that there's been a lot of attention paid to WePay in the Package Updates for Invoice Ninja by @nebulon

The introduction from Invoice Ninja states:

Go to Basic Settings > Online Payments, and you’ll see the Accept credit cards option, with 5 major credit cards listed. Check the credit cards you want to accept, and then you’ll be prompted to complete your WePay account set up – in the familiar, friendly Invoice Ninja environment you’ve come to know and love. There’s no annoying redirects, no waiting for approval, and no need to re-verify your personal and financial details.

I'm not seeing how to initiate this process. Rather, I'm seeing: Basic Settings > Payment Settings > Configure Gateways, which shows me the Providers who can be integrated with --no mention of WePay.

Can someone tell me what I'm missing? And/or confirm that WePay registration is possible via latest Cloudron build of InvoiceNinja?

Thanks fam
--frei

Ahh, I see now.

As MedusaJS, is a Node-based application framework, I should be following the tutorial here to create a Cloudron-ready Node.js application. I guess my feature request is already fulfilled

Will keep posted --and possibly prepare a tutorial?-- if I get this running. Thanks, team

Hi there Cloudron community!

Does anyone know if the Cloudron team has the open-source, Medusa e-commerce platform on its radar?

Our design team likes working with Ghost and SnipCart, however many of our clients prefer for us to keep as much of the system integrated, self-hosted on the private VPS as possible --which is why we love using Cloudron

We've seen some information on preparing Docker containers for Cloudron . . does anyone else have an interest in this and would anyone be interested in collaborating on a build? Perhaps if we provided a community-backed image, it would encourage Cloudron to adopt and maintain into the future?

Thanks for any advice and input.

Hello Cloudron team/patrons,

I was going to ask for help, but we came up with the solution, so we'll pass it forward.

We needed to recover from a system outage, after temporarily running out of disk space. Besides corrupting the certificates (already fixed thanks to the forum here --thank you), we also borked the outgoing SMTP mailserver.

The obvious symptom from RoundCube showed "SMTP Error (-1): Connection to server failed."

Reviewing the 'mail' service logs revealed that there was a corrupted "queue file" (zero bytes), which was crashing the service.

To fix this issue, SSH into the machine, navigate to /home/yellowtent/boxdata/mail, move the haraka-queue to a backup location, and recreate that directory. After that, restart the mail service.

H there, Cloudron community.

I've often nearly posted questions here, but we always get it sorted out. So I just want to show some gratitude . . .

Our team is loving working with Cloudron! Thanks so much for this incredible service. We wouldn't be able to do what we do and provide the level of service to our community that we have been able to, if it weren't for the incredible work of the Cloudron team managing the configuration patterns . . THANK YOU

Hoping to see Jitsi Meet continue to be well supported.