[NextCloud] Connection to Files via Nemo Fails #580
Labels
No Label
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
help wanted
Howto
In progress
🤔️ Investigate
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
Themes
TOR
Urgent!
Website
windows
wontfix
xmpp
Yearly Report
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#580
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Greetings and I hope this finds you well, today.
I have, recently, initiated use of a hardware key for 2FA. An issue I have encountered is within Nemo (file manager provided by Linux Mint).
I have created an app password via Nextcloud for connecting my account within Linux Mint for the purpose of using Nemo to access files stored on Nextcloud. Upon completion of having created the app password and Online Services connection, I attempt to connect to Files via Nemo and am met with...
I have no desire of utilizing multiple file managers when all I need is one and am very pleased with it.
Could I have some assistance in resolving this? Thank you very much.
-Shadowstreik
address should be
davs://cloud.disroot.org/remote.php/dav/files/shadowstreik/Recreated Nextcloud online account within Linux Mint Debian Edition like so...
Netcloud service was connected using the newly created app password.
The result was...
I utilize a hardware key for 2FA and am not prompted to use it when connecting.
What may be the solution? This may be an inherent issue with Nextcloud, itself, so I only need a definitive answer before putting in an Issue with Nextcloud, should that happen to be the case.
Thank you.
tbh, I've no idea. I've 2FA enabled (but with no hardware key). I created the app password via Nextcloud, enter the given address in nautilus in the address line. It worked directly.
What I suggest, is first try without 2FA on Nemo see if there is already a problem at this level.
Hello. I was using Nemo, before, without 2FA of any kind and it operated normally. I may test OTP, though that isn't entirely desired; a hardware key is so much easier.
Thoughts?
then I would test with 2FA software before teting with 2FA hardware.
@muppeth any idea?
I have removed hardware key security. The previous Nemo connection has been restored. Testing TOTP will be forthcoming.
Testing using TOTP on my personal account and YouTube channel account work as expected. However, the household account with a username of two words separated by a . does not work. Something tells me it may have to do with that period/dot/what-have-you. Bah; details. A tougher password will result of that. :)
Correction. Connection is denied with use of TOTP.
Connection within Nemo cannot be made with use of any 2FA within Nextcloud.
I think nemo just like gnome's online accounts does not use any form of two factor so you need to create app password for those.
I created app passwords and it remained non-functional. Odd.
have you found any solution @Shadowstreik ?
The solution was to remove the use of 2FA in favor of password-only; my password is complex enough.