Cloudron Forum

I pushed out a new package with 4.0.1. Had to bump up the memory limit to 1GB to make things work a bit more reliably.

I was able to reproduce both issues, thanks for reporting! The proxy auth cookie secret is not persisted. It's stored in platform runtime data. I have migrated this into the database. Redirection logic was incorrect when the token is invalid. This is also fixed.

As you probably have access to the IP of the server, you could simply display a link once the setup is complete in the CLI: https://<IP>?<token> So not even copy/paste needed for most.^^

@mehdi this was indeed a bug in the restore code path. the setupToken, as you guessed, should be sent in the top level object and not as part of the backupConfig . Fixed now.

@mehdi thanks for reporting, this is fixed now. Next time a separate thread might be better to track those things if possible.

@mehdi I see the issue here as well. I've pushed a fix for this for the next release. Thanks for your attention to the details here

@savity you have to reboot the server using your VPS control panel or "reboot" via SSH. Do not use the reboot button in Cloudron dashboard, it doesn't work. We will make a new release most likely end of this month (6.4) where it will get fixed.

I learnt a few things about the python world as part of fixing this: There is now something called poetry. Projects now contain a poetry.toml file which can be converted into a requirements.txt using poetry export --format requirements.txt > requirements.txt . There is something called an "editable install" - https://www.python.org/dev/peps/pep-0660/ . Idea being you can just run the code and the code just "installs" away packages as needed. See https://www.python.org/dev/peps/pep-0660/#id5 . pyproject.toml is some new project settings file that possibly replaces setup.py

@nebulon Oh yeah, I had not thought to try the right-click, good catch. Right-clicking on a webpage never feels intuitive to me, except when I want the browser's context menu

@girish I don't know if it was installed before the upgrade, but it wasn't enabled, because unbound managed to run without problem I'm not sure how it got there. It was supposed to be a clean Ubuntu 16.04. The only things I installed manually besides cloudron are basically ZSH and screen. In any case, I marked this as solved, thanks !

OK, I have fixed the expiry.

OK, this got sorted out by enabling basicAuth flag. Thanks for testing @mehdi

I created another thread, as this is not sickchill related https://forum.cloudron.io/topic/4702/proxyauth-addon-basic-auth-semi-broken-in-6-2

@nebulon Sorry, totally missed your line about the shortcuts in the previous message my bad

This is fixed with https://git.cloudron.io/cloudron/dashboard/-/commit/99f096c9711528406144e0245f8020c502d6490a and will be part of 6.2 then

Ok, thanks for the update. Works for me as it is, but was curious if the ideas discussed above are still to be implemented.

@mehdi Indeed this was a regression, this is fixed now in 6.1

@girish Yes, it does appear to pass the correct credentials, and the function in question seems to give no error. I'll try to debug further on the app side, but for now I think we can just file this as an unexplained weird thing