@senthilkumaran said in Cloudron Subdomain pointing to a different IP for Apps not on Cloudron:
https://i.imgur.com/3gtJVw1.png - wildcard means that all the *.thinnal.org will point to the cloudron's ip.
If you have *.domain.org and foo.domain.org entries in your DNS provider , then foo.domain.org being more specific wins. One crucial note: this is not a feature of DNS since DNS protocol itself no concept of wildcard. This feature comes from the DNS providers (I think this comes from bind9 configuration files).
But interestingly, I have the root domain thinnal.org pointing to a different IP and it works fine.
Yes! because *.domain.org does not include domain.org . It only includes subdomains of domain.org but not the bare domain itself. This is another important DNS quirk to know.
@archos
Thank you. That command helped. Now I have some broken images next to some profile pictures like using verified status pic (or something). I think, I check that next. But this was a huge help!
@senthilkumaran https://github.com/TryGhost/Ghost/releases . there were 5 releases just this week. You can change update schedule in the settings -> update
@senthilkumaran I also suggest you check out the sample apps which Cloudron made and are available for testing proof of concept and as a base for your own package(s).
Also look on git.cloudron.io : there are many custom apps there from users (not Cloudron staff). Those can give you a good idea of how people approach the task of packaging, and i particular the task of separating read only /app/code and read write /app/data.
Could it be that ip address of the instance changed the service is not able to resolve to the new ip address?
The AWS LightSail IP-Address had changed, I had to manually go to my Google Cloud DNS, and update the ip-address to new ip-address and do a DNS Sync for other apps to update the ip-address.
I am bit surprised that DNS sync wasn't automatic when the host ip-address had changed. Am I missing anything?
@nebulon said in Authentication Servers are Down. Please try again later, sorry! - Error message with Minecraft App 1.9.2:
oh this might then actually be an unbound issue.
Indeed, it was. Problem resolved.
Thank you, @nebulon , @girish and @scooke .
@nebulon said in Google Sign In for Surfer:
so you could write small shell scripts for each site to avoid the risk of uploading to the wrong instance.
Yes, I do the same. Thank you.
@nebulon said in Access Control of Surfer content:
there is no real way to logout otherwise, since I didn't want to add any kind of overlay with a button or so.
Got it. Thanks for closing on this topic.
@senthilkumaran The CORS issue is covered here - https://forum.cloudron.io/topic/5589/cors-timeout-error-when-searching-for-public-rooms . Essentially, try giving synapse a lot of memory.
@senthilkumaran @potemkin_ai The upstream project has published a compatible plugin - https://github.com/taigaio/taiga-contrib-slack/issues/79#issuecomment-697182708 . I have pushed a new package with the plugin installed.
Please give it a try when possible. Please follow https://docs.cloudron.io/apps/taiga/#slack for enabling it. As always with plugins, only use it if you really need it since they break from time to time.
