Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to establish TOTP. #452

Closed
1 task done
Welved opened this issue Jul 15, 2024 · 4 comments
Closed
1 task done

Unable to establish TOTP. #452

Welved opened this issue Jul 15, 2024 · 4 comments

Comments

@Welved
Copy link

Welved commented Jul 15, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I had to wipe my container because some instance breaking change I have made. Upon re-installation it's as if I have already established a TOTP. All that I am able to do is generate backup codes. There isn't a option to reset the TOTP or even establish it in the first place.

I've went through all the relevant forums and stumbled on this:
docker exec -it -u www-data php occ twofactorauth:disable totp

But, when I try it; it just gives me this error:
unable to find user www-data: no matching entries in passwd file

Expected Behavior

Get either a TOTP secret to input manually or scan the TOTP QR code to establish TOTP.

Steps To Reproduce

  1. Wipe and re-install Nextcloud.
  2. Install Nextcloud as normal.
  3. Go through the admin settings to the security tab.
  4. Click the radio button to force 2FA.
  5. Go to admin's personal settings to do a TOTP.
  6. Only able to establish backup codes.

Environment

- OS: RaspberryPi4
- How docker service was installed: Can't recall.

CPU architecture

arm64

Docker creation

Used portianer to pull from docker hub and followed the configuration that is laid out on the linuxserver docker hub documentation.

Container logs

Setting resolver to  192.168.x.x
Setting worker_processes to 4
generating self-signed keys in /config/keys, you can replace these with your own keys if required
[KEY]
Initializing nextcloud 29.0.3.4 (this can take a while) ...
Setting permissions
New nextcloud instance
Please run the web-based installer on first connect!
Initializing finished
After completing the web-based installer, restart the Nextcloud container to apply default memory caching and transactional file locking configurations.
Alternatively, you can apply your own configurations by editing /config/www/nextcloud/config/config.php following the documentation:
https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/caching_configuration.html
https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/files_locking_transactional.html
[custom-init] No custom files found, skipping...
[ls.io-init] done.
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@LinuxServer-CI
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@drizuid
Copy link
Member

drizuid commented Oct 4, 2024

i suggest coming on discord for support, however, note that we do not support deploying our container with portainer or other UIs.

further,

I've went through all the relevant forums and stumbled on this:
docker exec -it -u www-data php occ twofactorauth:disable totp

But, when I try it; it just gives me this error:
unable to find user www-data: no matching entries in passwd file

this is a clear indication you didn't read the readme.

I'm going to close this as out of scope. i suggest reading the readme to understand how to use occ and coming on discord if you still have issues, though bear in mind, we support the container, not the application within. I can tell you my totp works without any issue.

@drizuid drizuid closed this as not planned Won't fix, can't repro, duplicate, stale Oct 4, 2024
Copy link

github-actions bot commented Nov 4, 2024

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Development

No branches or pull requests

3 participants