translator

[1.3.0]

• Update Ackee to 3.3.0
• Full changelog

[1.22.0]

• Update n8n to 0.152.0

@snoopdoop What is the app package version listed in the Updates section of the app ? Maybe you are already on the latest?

Yup, we are also in DigitalOcean, AWS Markplace, Vultr as well. Time4VPS also has an image but it's outdated, unfortunately we don't control that image. If anyone knows other hosting providers where we should integrate let us know Even better if you have a contact in those providers...

@mastadamus for the moment, maybe you can edit the nginx conf temporarily as needed? It's in /home/yellowtent/platformdata/nginx/nginx.conf. That part of nginx conf is only updated on a new Cloudron release (and not on app updates).

@girish I don't understand why, but this works perfectly on a fresh install of WP dev, but not on the rest.

Could it be that some plugin interferes with the alias? I'm going to try to deactivate plugins to see if that's what it is.

Edited:
I disabled all plugins and it remains the same. We have redirect and protection plugins so I thought it might interfere. Nothing of that.

I have started to investigate and I have realized one thing. At first we used WP managed apps and then we moved on to WP developer.

What we did was export each WP managed installation with WP all in one migration plugin. Then we import every one with that plugin into a WP developer app, so we never really use a clean install of WP developer.

Is it possible that this has to do with some configuration that prevents alias domains from working?

@eganonoa OK, I have added this for our next release - https://docs.cloudron.io/domains/#well-known-locations

You can set the jitsi location and cloudron will respond accordingly as per the wiki:

$ curl https://cloudron.space/.well-known/matrix/client
{"m.homeserver":{"base_url":"https://synapse.cloudron.space:443"},"im.vector.riot.jitsi":{"preferredDomain":"jitsi.cloudron.space"}}

@potemkin_ai The endpoint /api/v1/cloudron/renew_certs is correct and so is the POST data that you are sending it. I think the logs that you are showing is for some other task tough. What is the response of the POST request? This will give a task id and then you can go into /home/yellowtent/platformdata/logs/tasks/{taskid}.log

@mastadamus we collect nginx stats from the logs via collectd. While the stats are currently not displayed anywhere, the plan is to use them at some point. This is the reason for the combined2 format.

@smilebasti missed this one somehow, did you figure this out?