Looking forward to this. Need to track all my IP addresses & subnets somehow and it would be great to have it in cloudron!

@fbartels It works now with the fix from my colleague m4rg4sh (he submitted a pull request). Also there is a new version 1.8.0 - I just updated to it and everything looks great so far

Hi @fbartels

Thank you for your great work! This is definitely on a good path

Some few things I noticed:

• Saving a config throws a Error saving config: IOError. I also checked with a reboot and it seems it really can't be saved right now. (also smtp wouldn't be possible without this fixed)
• When accessing the admin panel when not logged into cloudron, you get a password prompt. A 403 HTTP would probably be more suitable and secure

And as a small Bonus: As the app is getting in a pretty good shape, it is time for a logo =D
here you go: https://github.com/bitwarden/brand/blob/master/icons/256x256.png

My whole cloudron was not really working after the update. I did a reboot, nothing really changed, System looked like this:

After the fix from @girish and restart of box everything worked again.

Hope you push a hotfix pretty soon for all others. Still wish for a GUI option to choose if i want auto or manually install system updates, just for cases like this (this exists for the apps and has existed for the cloudron itself in the past). Auto updates always have this bitter aftertaste of waking up next day and it could work or not work.

Hi @fbartels

Build and install worked without problems, but i'm facing the same issue as @necrevistonnezr

Couln't really find something on the first view, but i'm not that familiar with containers. Would be great to see it running, thank you for your efforts you already made!

You're welcome

I hope this pr is going to be merged into bitwarden_rs soon: https://github.com/dani-garcia/bitwarden_rs/pull/396

It would make it a lot easier for the user management. Currently registration is open to the world until you set ENV SIGNUPS_ALLOWED=false, which only makes sense after you created a first account. After setting it you could work with invites, but the invitation model sucks (you can just invite when having an Organisation or you can do it in the admin panel, but you have to set another env variable to access it and you can't save stuff there).

So currently not really usable for the normal user. As far as I understood, with the ldap integration accounts / invites will be synced for all ldap users, which is exactly what we want. I also hope the admin panel gets some love, as in my eyes the token system to log in there isn't really easy to handle. And there seems to be a problem saving the settings you set there, but that's probably a problem in the cloudron integration.

That seemed to solve it, even if a server reboot did not solve it. I also got a mail, that this was also visible from other mail-servers (not just from my mail client), as I use DANE for certificate pinning.
Thx girish!

@girish Just checked, yes i'm already on 5.6.1.
And good to know, thx

I also got SSL errors after the upgrade, but in Thunderbird. It seems like the default self signed Cert is used.

A possibility to postpone updates for like 2 weeks would be nice, to not run into such things.

My whole cloudron was not really working after the update. I did a reboot, nothing really changed, System looked like this:

After the fix from @girish and restart of box everything worked again.

Hope you push a hotfix pretty soon for all others. Still wish for a GUI option to choose if i want auto or manually install system updates, just for cases like this (this exists for the apps and has existed for the cloudron itself in the past). Auto updates always have this bitter aftertaste of waking up next day and it could work or not work.

Hi @fbartels

Thank you for your great work! This is definitely on a good path

Some few things I noticed:

• Saving a config throws a Error saving config: IOError. I also checked with a reboot and it seems it really can't be saved right now. (also smtp wouldn't be possible without this fixed)
• When accessing the admin panel when not logged into cloudron, you get a password prompt. A 403 HTTP would probably be more suitable and secure

And as a small Bonus: As the app is getting in a pretty good shape, it is time for a logo =D
here you go: https://github.com/bitwarden/brand/blob/master/icons/256x256.png

You're welcome

I hope this pr is going to be merged into bitwarden_rs soon: https://github.com/dani-garcia/bitwarden_rs/pull/396

It would make it a lot easier for the user management. Currently registration is open to the world until you set ENV SIGNUPS_ALLOWED=false, which only makes sense after you created a first account. After setting it you could work with invites, but the invitation model sucks (you can just invite when having an Organisation or you can do it in the admin panel, but you have to set another env variable to access it and you can't save stuff there).

So currently not really usable for the normal user. As far as I understood, with the ldap integration accounts / invites will be synced for all ldap users, which is exactly what we want. I also hope the admin panel gets some love, as in my eyes the token system to log in there isn't really easy to handle. And there seems to be a problem saving the settings you set there, but that's probably a problem in the cloudron integration.

@fbartels It works now with the fix from my colleague m4rg4sh (he submitted a pull request). Also there is a new version 1.8.0 - I just updated to it and everything looks great so far

Hi @fbartels

Build and install worked without problems, but i'm facing the same issue as @necrevistonnezr

Couln't really find something on the first view, but i'm not that familiar with containers. Would be great to see it running, thank you for your efforts you already made!

I'm having the same issue. I think at least since 3.5.1.

In my eyes all DNS checks out of the PTR are broken. When I check it manually with dig everything looks fine.

I'm using manual DNS entries and never changed anything there (but suddenly the checks went to red).

Hi @girish

Thx for your answer!

Yes, it's 3.5.2 on the 16.04 and 18.04 VM

I see the size as I made a bucket for tar and a bucket for rsync and i can see the size of each at the page of my provider. This behavior is something I could reproduce. Even tough there is some compression a compression rate of 1:10 made me wonder..

What do you think about the mails that weren't synced? Could it be in relationship to one of the errors?