Cloudron Forum

Within the dashboard, it's been telling me that there is a critical update available to update. Not sure if there is a way to get this pushed through from our end? Or do we wait?

Haven't been able to find a solution and just dealing with the notification of not using a CDN while using the S3 storage.

@james Yeah, meant the object storage instead.

Setting up a new Discourse install using Hetzner Storage Box as the S3 and wanting to use BunnyCDN, but the images are broken (not showing). When I inspect the network it's coming up that the images are 404, but within Bunny traffic is showing going through the CDN.

Should add that the Hetzner Storage Box works after adding the S3 details and the images show up with the right URL to the box. It's just when I add the BunyCDN credentials that things mess up.

Found the issue in that it was a simple typo that was messing everything up.

@jdaviescoates

#https://code.castopod.org/adaures/castopod/-/blob/develop/env
analytics.salt=XXXXXXXXX=
logger.threshold = 4
media.fileManager="s3"
media.s3.pathStyleEndpoint="true"
media.s3.endpoint="https://s3.us-west-004.backblazeb2.com"
media.s3.bucket="rollforaudio"
media.s3.key="XXXXXXXX"
media.s3.secret="XXXXXXXXXX"
media.s3.region="us-west-004"
app.baseURL="https://rollforaudio.com"
media.baseURL="https://rollforaudio.s3.us-west-004.backblaze2.com"

Added the last line to see if it would fix but, it doesn't.

Searching around and found that will have to add app.baseURL "...." in the .env file. Have done that and now the site comes up again. New problem though is that for podcast artwork, all the links are broken.

Freshly installed castopod and have added the following into the env file

media.fileManager="s3"
media.s3.pathStyleEndpoint="true"
media.s3.endpoint="https://rollforaudio.s3.us-west-004.backblazeb2.com"
media.s3.bucket="rollforaudio"
media.s3.key="XXXXXXXXXXXXXXX"
media.s3.secret="XXXXXXXXXXXXXXXXX"
media.s3.region="us-west-004"

Now, the site is unreachable, giving me a localhost refused to connect.

Found the issue!!

You must use the main account API key and secret and not a subaccount key for everything to work.

Recently installed NodeBB and I thought I had everything setup correctly. The issue is that when trying to send test emails, I'm not receiving them within my box. I have the domain setup within Cloudron as a relay to Mailjet and the status is showing a green bubble.

I also have it that the app is in control of email as well. My understanding is that Mailjet or a service like it, will handle the sending of outgoing email. This doesn't seem to be the case though as it seems that Cloudron reports that the email is sent and delivered but, nothing is ever received.

I try to send a test email as well from within NodeBB but, that too doesn't seem to work.