@d19dotca unfortunately I do not have a macOS device to test this with safari and it seems chromium and firefox do not hit this issue.

We didn't get to the bottom of this but the user solved it by moving to sendgrid.

Thanks to @nebulon. After troubleshooting a few things on my network, we figured out that the access problem to my Cloudron is due to my ISP suddenly blocking ports 80 and 443. Please mark this issue as resolved!

@brutalbirdie sorry about that, by 'it was' i meant that it was on my secondary machine. I am new to these things and I apologise for anything annoying.

@sebgg have you tried clearing out postgresql directory entirely ? Assuming you have backups, docker stop postgresql rm -rf /home/yellowtent/platformdata/postgresql/* ``` Then, go to services -> postgresql -> restart. That will rebuild the postgresql container.

@luckow It seems the multipart copy is not succeeding. What is the backup provider (minio?) ? If minio, do you see any errors on the minio side? Do you know how big the data for that app is?

This was a regression in 7.0. When user profiles are locked, the password is not reset properly. This is fixed in next release. Workaround for now is to disable locking of user profile. Alternately, you need this change - https://git.cloudron.io/cloudron/box/-/commit/37f066f2b0e4aa50ec45b387dd1d79b539d1aaf5

@chicagogregg By chance did you or someone write up a step by step guide on this? I'm needing to do something similar but for whatever reason, ssh proxying and I don't seem to get along.

The API docs are now also updated for the invite routes.

@nebulon Ok so weird thing, it works in Firefox (I normally use Safari). Let me do some more investigating, I guess Safari is probably blocking something for privacy reasons…

@girish Thank's a lot

@samuelbevan2000 you have to port forward port 443 in the router to the vm.

@jodumont from experience I know MX doesn’t work because the mailserver doesn’t respond to IPv6. That way we’ve lost some mails before we discovered that.

@girish I have removed that file. done sudo apt auto clean and rebooted the server. After reboot and runnning the /home/yellowtent/box/setup/start.sh command, everything worked again. That key was the issue.

@girish Thanks, that seems to have taken care of it

I have improved the check now to see if there is atleast 1GB before applying an update.

@girish I went ahead and made the change manually and we are back in business. In case anyone else looks at this, the home/yellowtent/box path is on the server hosting cloudron.