Posts made by d19dotca

Hello,

I noticed recently (likely a bug I'm guessing as it seems to only started in the latest version) that the Graphs page only seems to show a few apps memory usage. It used to show every app broken out in the chart, but it seems to randomly only show anywheres now from 2-6 or so at a time in my experience over the last week. It seems to be different on reboot of the server. For reference, I have 19 apps that are running on this same (and only) server. So I'd expect to see all of them in that graph/chart.

Any assistance would be greatly appreciated.

Hello,

It seems that the new graph for disks is great, I definitely think it's a huge improvement over the previous versions. However, I'd love to see the ability to quickly know how much space is available on the disk. The way it is right now, I have to do the manual math to determine how much is left. While I can easily SSH to it and find out too, sometimes I want to keep an eye on it on the road and it isn't as easy to SSH to the box rather than just login to Cloudron. If I can hover over every other colour / section in that graph and know exactly how much it takes up, I should be able to use that same feature to find out how much is available too.

Just a thought anyways. Thanks in advance!

Dustin.

I just noticed mine at 10.24 GB for "Other". What is that and how do we clear it up (if it's even safe to do so)?

Side note: Would be great if the feature graph would also do the math to show how much remaining space exists so we don't have to do the math ourselves. I think I'll file that feature request separately later on.

@nebulon I would suggest it should be done according to server local time, but either will work. Basically I just want a way to see the logs in a way that makes sense timeline-wise when I need to look for errors that happen at 5 PM Pacific Time for example, want to make sure I'm not going to waste any time by messing up a manual time conversion.

How does one change the timezone so it's easier to view the logs? It would be a huge help in removing the task of converting the time every time I want to look at a certain time in the logs for an event. The logs are in UTC. I saw the documentation here (https://cloudron.io/documentation/settings/#timezone) and tried to run the command but nothing shows in the output, no error, nothing. It's as if functionality here doesn't exist anymore. Any ideas?

All I want to achieve is reading the system logs and email logs in my time zone rather than UTC (which is what it appears to be - example, it's 8:13 PM Pacific Time on Oct 27, but the logs show the next day (Oct 28) at 3:13 AM.

If this isn't currently possible, it'd be great to have this feature in the product as a setting.

You guy are are amazing and fast, thank you!

Hello,

A minor feature request (really more an enhancement) but would really help when needing to manually run through something where many mailboxes or mailing lists exist... It'd be great if we had the ability to sort the tables. So for example, we could sort the mailboxes table by Name, Owner, Aliases (although this one would be tricky as it'd only sort on the most alphabetic nature of the aliases listed with the mailbox), etc. Same for mailing lists, where we could sort by Name and List Members (mostly Name is the main one to sort with though).

Or even if an interim enhancement would be to just sort automatically by Name in each list, that'd be helpful. Because right now when I add a new mailing list for example, it just adds it at the bottom and later on it's still there, meaning I cannot see at a glance if a mailing list exists that I may be wanting to double-check, because it's not sorted properly so I then need to use the Find functionality of my browser.

Hopefully the above makes sense.

@girish So I found out how to restore from a backup using the CLI and that worked for me for the second app. It's still weird to me that it went to "Backup not found" when all other backups were fine and it was done by the one action on restoring the entire server. It makes me think there's a defect there somewhere, but it may be difficult to reproduce.

@girish I went ahead and changed the domain DNS to "no-op" and repaired it. It moved past the DNS thing but I ran into the same error as before. Here is the logs if it helps. I noticed the dates all seem random, unsure why that is but assuming it isn't related.

How can I get past this? Is there a way to pick a different backup? It seems I can't from the UI at this time, can only use CLI but I didn't have the best luck with that when I tested it earlier today for the first incident.

Jan 01 00:00:00 'Backup not found: 2019-10-15-010001-045/app_b858c18c-0e10-464a-b83b-0e6c2abb2b74_2019-10-15-012040-165_v2.6.4.tar.gz.enc' }
Oct 17 03:38:43 box:backups tarExtract: input stream error. { BackupsError: Backup not found: 2019-10-15-010001-045/app_b858c18c-0e10-464a-b83b-0e6c2abb2b74_2019-10-15-012040-165_v2.6.4.tar.gz.enc
Jan 01 00:00:00 at S3ReadStream.<anonymous> (/home/yellowtent/box/src/storage/s3.js:134:34)
Jan 01 00:00:00 at S3ReadStream.emit (events.js:189:13)
Jan 01 00:00:00 at S3ReadStream.EventEmitter.emit (domain.js:441:20)
Jan 01 00:00:00 at process.nextTick (/home/yellowtent/box/node_modules/s3-block-read-stream/lib/readstream.js:49:37)
Jan 01 00:00:00 at process._tickCallback (internal/process/next_tick.js:61:11)
Jan 01 00:00:00 name: 'BackupsError',
Jan 01 00:00:00 reason: 'not found',
Jan 01 00:00:00 message:
Jan 01 00:00:00 'Backup not found: 2019-10-15-010001-045/app_b858c18c-0e10-464a-b83b-0e6c2abb2b74_2019-10-15-012040-165_v2.6.4.tar.gz.enc' }
Oct 17 03:39:03 box:backups tarExtract: input stream error. { BackupsError: Backup not found: 2019-10-15-010001-045/app_b858c18c-0e10-464a-b83b-0e6c2abb2b74_2019-10-15-012040-165_v2.6.4.tar.gz.enc
Jan 01 00:00:00 at S3ReadStream.<anonymous> (/home/yellowtent/box/src/storage/s3.js:134:34)
Jan 01 00:00:00 at S3ReadStream.emit (events.js:189:13)
Jan 01 00:00:00 at S3ReadStream.EventEmitter.emit (domain.js:441:20)
Jan 01 00:00:00 at process.nextTick (/home/yellowtent/box/node_modules/s3-block-read-stream/lib/readstream.js:49:37)
Jan 01 00:00:00 at process._tickCallback (internal/process/next_tick.js:61:11)
Jan 01 00:00:00 name: 'BackupsError',
Jan 01 00:00:00 reason: 'not found',
Jan 01 00:00:00 message:
Jan 01 00:00:00 'Backup not found: 2019-10-15-010001-045/app_b858c18c-0e10-464a-b83b-0e6c2abb2b74_2019-10-15-012040-165_v2.6.4.tar.gz.enc' }
Oct 17 03:39:03 box:backups restoreApp: time: 82.216
Oct 17 03:39:03 box:apptask www.<domain-replaced> error installing app: BackupsError: Backup not found: 2019-10-15-010001-045/app_b858c18c-0e10-464a-b83b-0e6c2abb2b74_2019-10-15-012040-165_v2.6.4.tar.gz.enc
Oct 17 03:39:03 box:apptask www.<domain-replaced> updating app with values: {"installationState":"error","error":{"message":"Backup not found: 2019-10-15-010001-045/app_b858c18c-0e10-464a-b83b-0e6c2abb2b74_2019-10-15-012040-165_v2.6.4.tar.gz.enc","reason":"Unknown Error","taskId":"1032","installationState":"pending_restore"}}
Oct 17 03:39:03 box:tasks setCompleted - 1032: {"result":null,"error":{"stack":"BackupsError: Backup not found: 2019-10-15-010001-045/app_b858c18c-0e10-464a-b83b-0e6c2abb2b74_2019-10-15-012040-165_v2.6.4.tar.gz.enc\n at PassThrough.<anonymous> (/home/yellowtent/box/src/backups.js:508:19)\n at PassThrough.emit (events.js:194:15)\n at PassThrough.EventEmitter.emit (domain.js:441:20)\n at S3ReadStream.<anonymous> (/home/yellowtent/box/src/storage/s3.js:134:20)\n at S3ReadStream.emit (events.js:189:13)\n at S3ReadStream.EventEmitter.emit (domain.js:441:20)\n at process.nextTick (/home/yellowtent/box/node_modules/s3-block-read-stream/lib/readstream.js:49:37)\n at process._tickCallback (internal/process/next_tick.js:61:11)","name":"BackupsError","reason":"external error","message":"Backup not found: 2019-10-15-010001-045/app_b858c18c-0e10-464a-b83b-0e6c2abb2b74_2019-10-15-012040-165_v2.6.4.tar.gz.enc"}}
Oct 17 03:39:03 box:tasks 1032: {"percent":100,"result":null,"error":{"stack":"BackupsError: Backup not found: 2019-10-15-010001-045/app_b858c18c-0e10-464a-b83b-0e6c2abb2b74_2019-10-15-012040-165_v2.6.4.tar.gz.enc\n at PassThrough.<anonymous> (/home/yellowtent/box/src/backups.js:508:19)\n at PassThrough.emit (events.js:194:15)\n at PassThrough.EventEmitter.emit (domain.js:441:20)\n at S3ReadStream.<anonymous> (/home/yellowtent/box/src/storage/s3.js:134:20)\n at S3ReadStream.emit (events.js:189:13)\n at S3ReadStream.EventEmitter.emit (domain.js:441:20)\n at process.nextTick (/home/yellowtent/box/node_modules/s3-block-read-stream/lib/readstream.js:49:37)\n at process._tickCallback (internal/process/next_tick.js:61:11)","name":"BackupsError","reason":"external error","message":"Backup not found: 2019-10-15-010001-045/app_b858c18c-0e10-464a-b83b-0e6c2abb2b74_2019-10-15-012040-165_v2.6.4.tar.gz.enc"}}

@girish Ah okay, I see. Out of curiosity, why does it do it when it's set to manual? I would expect it to restore the files and operate regardless of DNS resolution, particularly in the case where the domain DNS is set to "manual". Is there a reason it behaves the way it does right now? I don't quite understand why it would care about the DNS state for the app when I asked it to restore itself.

By the way, in case it matters, the process I followed was in your documentation for migrating the entire server (in my case from DigitalOcean to OVH), not just a single app. And everything worked perfectly except for the two apps that are associated with the domain DNS setup of "manual".

I have one app remaining that needs to have the external DNS entries updated to the new server IP. I'm afraid of running into the same problem as before. I have a workaround but ideally I'd like to try and figure out why this happened, if possible. Would you suggest that I change the remaining one to "no-op" as you suggested? In that case, do you think that once the DNS is updated that I can then run the repair and it should succeed? I guess if it doesn't, I can try to get the extra logs like you suggested which may help too. This is more a learning experience than anything, so just trying to get the process nailed down.

@girish Sounds good, yes please. I can understand why it was limited but I think limiting to just 1 is a bit aggressive in real-world use-cases. Would love to see it at at least 3 deep for resolution of the user, but preferably a few more.

Hello,

I am running 4.2.6, and I have tried to migrate to a new provider. So I followed the documentation and restored everything to the new server in the new providers data centre. It works, however two apps fail to restore and that's maybe expected because it seems to do a DNS check (even though it's set to manual for these two domains) and the DNS is handled by another person so I can't make the change myself. So in other words, at this point, I had all my apps running fine, but two were in error state and due to the DNS not pointing to the new IP address.

I asked one of the providers to switch the IP for me, and once it did the app was still in error state so I hit the Repair option as it was basically the only option, and it would then move past the DNS error but then return a "Backup not found" error. This doesn't make sense, it was part of the same backup every other app came from. These two apps are automatically backed up.

Just trying to determine why this might happen. Trying to figure this out before migrating the last one over so I don't have to rebuild the whole thing manually as I ended up having to do with the first one today since I needed them up and running quickly.

First backup / restore experience, and generally went well with one exception (for two apps). I'm assuming the same thing will happen with the remaining one, though maybe it'll be fine after I hit repair, but worried about it not finding the backup again. The backup was just created yesterday, it still exists, it is unclear why it doesn't have it.

I have encountered a problem and it seems reproducible. Would appear to be a bug in the workflow, I think. I have been able to reproduce it on different domains too.

To reproduce the issue:

1. Use Cloudron 4.2.6
2. Create a Mailing List like so:

• info@example.com > sales@example.com
• sales@example.com > dustin@example.com

3. Send email to info@example.com

You should receive an error about "User does not exist" when the email is sent. It seems like there is a limitation or defect where if I have one mailing list forward to another mailing list which then forwards to a final target email address, it fails to see the second one as a user. In other words, info@example.com will not forward to sales@example.com because it's another mailing list.

This may be useful in some circumstances, but my concern is that in real-world use-cases such as one where we have two domains and so I have info@example.com forward to info@secondexample.com where info@secondexample.com forwards to the intended target, it will fail. And the overhead that creates is that I then have to go into every domain and look at every user and ensure the final target is used rather than being allowed to forward to other mail lists. In such a case, I would have been able to just update one target email address in one location rather than possibly 10+ across different domains.

Hopefully the above makes sense. I find it difficult to explain. I'll try to clarify if anything is needed or if the above is confusing. Ultimately, and maybe my expectation is not realistic, but I would have expected it to basically "follow the ball" where it will go through each hoop it needs to, rather than failing right away to any other mailing list.

I assume this may have been implemented as a precaution to avoid infinite loops, but maybe in this situation it'd be better to allow it to still forward to other mailing lists but limit it to 5 deep or something to avoid infinite loops.

Possibly related, unsure, but for what it’s worth I actually preferred the old UI for configuring an app. It seems the new way just involves at least one extra tap/click and doesn’t really solve anything, at least not in my own use of the product. Totally get the minimalism approach and I’m generally a fan of that but in this case the UI for configuring an app seems like it went back a step. Just my two cents. Maybe there’s a “meet in the middle” approach that would work better from how it was before to how it is now? It still works for me so that’s the most important part. Haha.

@nebulon So to confirm then... 4.2 isn't really released at all then yet. It's pretty much in a "beta" state, used for new installs but nobody with an existing install will have received it yet unless we formally request our domain be whitelisted. Is that correct? There seems to be confusion here with the way things are being worded. 17 days ago it was stated "The initial 4.2 was pushed out yesterday" but now you're saying "we don't push out 4.2.0 yet" -- this is creating a bit of confusion.

@nebulon & @girish - my Cloudron still shows 4.1.7 when I check for updates. I would definitely say this should be a feature request then that is a user manually clicks/taps the Check For Updates button, the latest build is presented. It would only generally be used when someone is aware of an update and expecting to install it. I understand the blacklist/whitelist thing but I would say it should be ignored when the button is pressed. The rollout using a blacklist/whitelist should only be done for those who don't manually use the button so it notifies them when it's ready.

@nebulon Okay, I kind of understand that methodology but I would still like to request then that for the future, when a user manually checks for an update it's because they want to update so that should be sort of auto-whitelisted (not to mention it would save you some unnecessary support emails). I can appreciate and totally understand scattering it for automatic download types, but it should be understandable from your side too that when a user is manually tapping the Check For Update button it's because they already know there's a new update out and are ready to deploy it. So it'd be great if that auto-whitelisted the domain.

I had recently already asked this and you may want to see this response: https://forum.cloudron.io/post/4373

@girish how do we force it? I assumed when you said it’s take a while to roll out to existing Cloudron’s I figured that’d only impact the automatic ones, but that it’d still be usable if manually requested in the Settings page using the Check for Update button, however it won’t find it when I do that. Is that intentional?

@nebulon Will it also show email disk usage? It’s not explicitly an app but it’d be very useful to understand how much disk space is used by email accounts and ideally digging deeper into which email accounts are consuming what amount of disk space.