@girish said in We need the Matrix Authentication Service (MAS):
@jdaviescoates @nebulon also attended the matrix talk in FOSDEM and they mentioned MAS is the way forward. It's in our internal task list, let's see when @vladimir.d can get to it.
@ntnsndr FYI I think this is the latest (saw you commented on the related thread about Element X)
@nostrdev you can pass -p or --port-bindings to cloudron install . It will query it.
You can also pass directly using -p NEO4J_BROWSER_PORT=someportnumber,BOLT_BROWSER_PORT=anotherport .
@msbt said in Cloudron 9.0 (beta) bug reports:
After deleting a mailbox, I got back to the /#/mailboxes view but all accounts just show "Loading..." and nothing happens. Would be cool if it remembered the mailbox size or at least start collecting the data again.
this is fixed in https://git.cloudron.io/platform/box/-/commit/3a760282f15259f461e0db4181883ac9d82aac06
@Teiluj said in 2FA enforcement issue on Cloudron 9.0.13:
(major issue) 2FA enforcement does not work.
Fixed in https://git.cloudron.io/platform/box/-/commit/76f2c5f9fc7ea673ddbe02e5aed9e691c85cd5c6
Thanks for reporting!
I'm encountering this as well. It is really disappointing as a statement on the Matrix ecosystem that the flagship Matrix app can't always log into the standard Matrix server. Do we have any ability to build in a workaround for Cloudron?
Same here about the backup.
I have also witnessed the automatic update to from v8 to v9. However, this was on only my unlicensed/free Cloudron servers. All licensed ones were waiting on manual trigger (probably because v9 is still officially not released), which once triggered went smoothly.
@timconsidine As part of maintenance, there are database migrations that are part of the update process. The more complex the update process, the more likely there will be issues.
@woolfdrs3 It seems the server is running on OpenVZ which Cloudron doesn't actively support. However, it works after I added this workaround:
# cat /etc/systemd/system/docker.service.d/openvz.conf
[Service]
Environment="DOCKER_IGNORE_BR_NETFILTER_ERROR=1"
Also make sure that the firewall on your VPS/VDS is not enabled or blocking the required ports. For example, on Amazon EC2, if the inbound security group rules for the necessary RTC ports are not configured, the service will not work...
@maxman I still cannot ping the IP address on your dashboard domain . Could there be some router/firewall setting that need to be tweaked since the IP changed? From the troubleshooting you posted, I think you can safely ignore Cloudron at this point. Cloudron itself is running fine, the server is just unreachable .
[1.0.1]
Update opodsync to 0.4.7
Full Changelog
Add some client tests (still incomplete)
Refactor API error and route handling
Fix register button was hidden when no user existed
Fix login after registration
Fix various warnings for PHP 8.5 compatibility (please report any issue)
