Cloudron Forum

@girish it seems the most recent update worked....while i did change some email settings, the only other action I took was manually bumping along the updates several versions. So there must have been some sort of inconsistent state that came up. It seems all is well with the world and no way to track down what happened. Thanks for the help, all.

I was unable to find any official documentation showing a breaking API change. However I did find this python library that seemed to be on top of its game: Citric. Their "save_responses"/"export_responses" method still worked, so as a temporary measure I was able to drop in their method to get data flow working again. I haven't dug into their code further yet to see what specifically changed/broke, but I'm going to mark this thread as resolved (before I lose it), as someone can read that code to find the specific solution if needed.

Also, for those that don't know what HLS is (I didn't prior to running into this issue), here's a link to get you started with "HTTP Live Streaming": **Adaptability ** To enable a player to adapt to the bandwidth of the network, the original video is encoded in several distinct quality levels. The server serves an index, called a "master playlist", of these encodings, called "variant streams". The player can then choose between the variant streams during playback, changing back and forth seamlessly as network conditions change. https://en.wikipedia.org/wiki/HTTP_Live_Streaming#Adaptability

@girish After thinking about this a bit more, it seems the optimal solution for "developer apps" isn't a published app, but some git repos of a few starter custom apps (dockerfile + ldap login + config instructions for a database if needed) specifically. I know all the published cloudron app repos can be viewed (as linked in the packaging tutorial). Perhaps that is sufficient. I'm building what is effectively a cloudron mashup (tying multiple apps together, LDAP, + private dns so API calls are local). I'll provide further feedback if the current tutorial materials seem insufficient.

@luckow Sounds like this could be adapted to a Cloudron App having it install in the appropriate directories for 'w' and 'ro' filesystems.

The root cause for this was the Cloudron server had the hostname as "box.domain.com" (same as the relay). Debian/Ubuntu has a quirk that it will put the hostname in /etc/hosts to resolve as 127.0.1.1. This meant that when we try to set it as relay, it resolves to 127.0.1.1 instead of the actual IP. To add to the confusion, I suggested using the host command which does not use /etc/hosts (i.e the nsswitch mechanisms) and uses only the DNS. If I had suggested using ping then we would have narrowed down the issue more quickly... Anyway, the fix is simply to hostnamectl set-hostname somethingelse.domain.com and also edit /etc/hosts (for some reason, hostnamectl doesn't change hosts file even after reboot, ).