What's coming in 9.1
-
I think in @msbt 's case the Cloudron already updated to 9.1.x unexpectedly (from a previous post). So, this is expected. For those on 9.1.x already, it is correct to update 9.1.0 -> 9.1.1 -> 9.1.2 -> 9.1.3 . Basically, we can't and don't test all the possible code paths when we make new releases. 9.0.17 -> 9.1.3 was explicitly tested since most people are on 9.0.17.
-
@timconsidine 9.1.3 is being rolled out . The upgrade path will be straight from 9.0.17 to 9.1.3
@timconsidine 9.1.3 is being rolled out . The upgrade path will be straight from 9.0.17 to 9.1.3
I still get the "This update is a pre-release and not considered stable yet. Please update at your own risk." warning:
-
@timconsidine 9.1.3 is being rolled out . The upgrade path will be straight from 9.0.17 to 9.1.3
I still get the "This update is a pre-release and not considered stable yet. Please update at your own risk." warning:
@jdaviescoates that's the correct behavior. it's being rolled out in phases. are you expecting something else?
the alternate message here would be "This update is being rolled out." but given our small team size, we want something deterring people from all updating at once.
-
@jdaviescoates that's the correct behavior. it's being rolled out in phases. are you expecting something else?
the alternate message here would be "This update is being rolled out." but given our small team size, we want something deterring people from all updating at once.
-
Hello @murgero
Currently, we use the message
This update is a pre-release and not considered stable yet. Please update at your own risk.in two cases.Case 1:
What the message states exactly.
The update is pre-release and not considered stable yet.Case 2:
We also use the same message when we are rolling out the finished update to lower the load so not all systems automatically update at the same time.
DDoS protection against ourselves and to catch regressions that we might have missed early with fewer instances effected.
In Case 2, the automatic update would still trigger at some point when it is your systems turn to update.When we post the announcement in the Forum that e.g.: 9.1 is released, case 2 is in effect, but the message is still the same.
I understand the confusion here, and we will improve the message in this case to reflect what is actually happening.
We simply did not get to it, yet.
Apologies for the confusion, we will improve this in the future! -
I upgraded from 9.0.17 to 9.1.3 yesterday and everything went smooth as butter! Thanks to the Cloudron team for the awesome work!
-
Hello @murgero
Currently, we use the message
This update is a pre-release and not considered stable yet. Please update at your own risk.in two cases.Case 1:
What the message states exactly.
The update is pre-release and not considered stable yet.Case 2:
We also use the same message when we are rolling out the finished update to lower the load so not all systems automatically update at the same time.
DDoS protection against ourselves and to catch regressions that we might have missed early with fewer instances effected.
In Case 2, the automatic update would still trigger at some point when it is your systems turn to update.When we post the announcement in the Forum that e.g.: 9.1 is released, case 2 is in effect, but the message is still the same.
I understand the confusion here, and we will improve the message in this case to reflect what is actually happening.
We simply did not get to it, yet.
Apologies for the confusion, we will improve this in the future! -
9.1.5 is now in unstable. It fixes many minor issues and one major issue related to passkeys in 9.1.3.
[9.1.5]
- services: lazy start services / on demand services
- restore: fix restore of trusted ips and blocklist
- dashboard: wait for dashboard reload when version has changed
- graphite: fix aggregation of block/network read/write
- Workaround chrome quirks on file drop handling
- notifications: add empty text, progress bar and inifinite scroll
- rsync: throttle log messages during download
- backup logs: make them much terse and concise
- oidc: implement Device Authorization Grant
- operator: fix viewing of backup progress and logs
- notification: automatic app update failure notification
- backup sites: identify conflicting site locations
- update: add policy to update apps and platform separately
- passkey: fix issue where passkeys were lost on restart
- passkey: implement passwordless login
- oidcserver: fix jwks_rsaonly response
-
9.1.5 is now in unstable. It fixes many minor issues and one major issue related to passkeys in 9.1.3.
[9.1.5]
- services: lazy start services / on demand services
- restore: fix restore of trusted ips and blocklist
- dashboard: wait for dashboard reload when version has changed
- graphite: fix aggregation of block/network read/write
- Workaround chrome quirks on file drop handling
- notifications: add empty text, progress bar and inifinite scroll
- rsync: throttle log messages during download
- backup logs: make them much terse and concise
- oidc: implement Device Authorization Grant
- operator: fix viewing of backup progress and logs
- notification: automatic app update failure notification
- backup sites: identify conflicting site locations
- update: add policy to update apps and platform separately
- passkey: fix issue where passkeys were lost on restart
- passkey: implement passwordless login
- oidcserver: fix jwks_rsaonly response
Subject: Passkey verification failed on desktop, login failure, and 2FA "Confirm" button disabled
@girish Hi, I updated to the latest version, but I'm unfortunately still running into issues with the Passkey feature. Here are the full details of what I'm experiencing across my devices, along with the relevant logs.
-
Initial Setup & Mobile Success:
I successfully set up a passkey using the Dashlane app on iOS. The initial login worked perfectly, and the passkey login continues to work fine whenever I use that specific phone. -
Desktop Login Issue & Fallback Failure:
The next day, I tried to log in via the web on my Windows desktop PC using the passkey, but the login failed. I then tried to fall back to a standard password login. However, when I reached the 2FA screen, the "Confirm" button was greyed out/disabled, leaving me locked out on my PC. -
Desktop Passkey Setup Error:
Thinking I needed to reconfigure it, I tried to set up the passkey again directly from my Windows desktop using the Dashlane extension. When I do this, it throws an error stating: "passkey verification failed".
Troubleshooting I tried:
Tested across multiple desktop browsers (Firefox, Chrome, and Edge) — both the 2FA button issue and the setup error happen on all of them.
Double-checked my desktop's time and date settings to ensure everything was properly synced for 2FA.
My Workaround:
I ended up logging into Cloudron via my phone (where the passkey still functioned perfectly) and removed the passkey from my account entirely. Once the passkey was deleted, I was able to successfully log in on my desktop using my normal password + 2FA.Logs:
I pulled the logs from when I attempted the setup on the desktop, and it looks like it's failing on the user verification step:Plaintext
Mar 27 14:16:17 passkeys: getRegistrationOptions: generated for user uid-xxxxxxx-xxxx-46a5-80e5-d95d5451d588
Mar 27 14:16:19 passkeys: verifyRegistration: verification failed for user uid-xxxxxxx-xxxx-46a5-80e5-d95d5451d588: Error: User verification was required, but user could not be verified
Mar 27 14:16:19 at verifyRegistrationResponse (file:///home/yellowtent/box/node_modules/@simplewebauthn/server/esm/registration/verifyRegistrationResponse.js:119:15)
Mar 27 14:16:23 apphealthmonitor: app health: 10 running / 1 stopped / 1 unresponsive
Let me know if there's anything else I can test or provide to help track this down! -
Hello @dualoswinwiz
What Cloudron version are you currently using where this issue is present?Hello @dualoswinwiz
What Cloudron version are you currently using where this issue is present?9.1.5
-
Hello @dualoswinwiz
I was not able to reproduce your described issue.@james do you want me to share a screen recording ? Or share any logs i have 4 cloudron instances and i faced the same. I use Dashlane for credential management all my passkeys stored in that
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login