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

[Bug]: nextcloud client failed to parse netrc #7177

Open
5 of 8 tasks
130e opened this issue Sep 21, 2024 · 8 comments
Open
5 of 8 tasks

[Bug]: nextcloud client failed to parse netrc #7177

130e opened this issue Sep 21, 2024 · 8 comments
Labels
1. to develop approved bug approved by the team

Comments

@130e
Copy link

130e commented Sep 21, 2024

⚠️ Before submitting, please verify the following: ⚠️

Bug description

After upgrading to 3.14.0, nextcloud client commandline (nextcloudcmd) failed to parse netrc credential with -n option. As a result, nextcloud server prompt for credential.
On the other hand, using --user and --password options work.

Steps to reproduce

  1. Create the file ~/.netrc as:
default
login admin
password mypassword
  1. Run nextcloudcmd from bash.
nextcloudcmd -n --path /Documents /home/user/Nextcloud/Documents/ https://myserver.com
  1. nextcloudcmd failed to parse netrc and prompt for credentials.
09-20 17:27:56:193 [ debug default ]	[ OCC::NetrcParser::parse ]:	error fetching value for "default\nlogin admin\npassword mypassword\n"
Please enter username:

Expected behavior

nextcloudcmd should parsed netrc.

Which files are affected by this bug

netrc

Operating system

Linux

Which version of the operating system you are running.

NixOS 24.11.20240919.c04d565 (Vicuna) x86_64

Package

Distro package manager

Nextcloud Server version

29.0.4

Nextcloud Desktop Client version

3.14.0

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

  • Default internal user-backend
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Nextcloud Server logs

No response

Additional info

No response

@freundhein
Copy link

Same here, on:

  • Linux, Ubuntu 22.04.5 LTS
  • package version including nextcloudcmd is nextcloud-client 3.14.0-20240916.085658.d8fcb9273-1.0~jammy1
  • nextcloud server 29.0.6

I have evidence that it synced normally before the latest update of nextcloudcmd, i.e. before 2024-09-16

@mgallien mgallien added 1. to develop approved bug approved by the team and removed 0. Needs triage labels Sep 25, 2024
@pfassina
Copy link

pfassina commented Oct 3, 2024

I also had it working before, and now it is throwing an error.
I'm using a NixOS package.

Nextcloud version 3.14.0
Git revision d8fcb9273729c0e70f99d6f42ed7185c2bb69779
Using Qt 6.7.2, built against Qt 6.7.2
Using 'OpenSSL 3.0.14 4 Jun 2024'
Running on NixOS 24.11 (Vicuna), x86_64

@fatpat
Copy link

fatpat commented Oct 17, 2024

same here

Nextcloud version 3.14.1
Git revision 8b92fc33a289bf4fc7bc7cdd68d25a9ed1ae1782
Using Qt 6.7.2, built against Qt 6.7.2
Using 'OpenSSL 3.0.14 4 Jun 2024'
Running on Ubuntu 22.04.5 LTS, x86_64

@tarastella
Copy link

Same here, running FreeBSD:

Nextcloud version 3.14.1daily
Git revision 8b92fc33a289bf4fc7bc7cdd68d25a9ed1ae1782
Using Qt 6.7.3, built against Qt 6.7.3
Using 'OpenSSL 3.0.13 30 Jan 2024'
Running on FreeBSD 14.1-RELEASE-p5, x86_6

@ncartron
Copy link

ncartron commented Nov 6, 2024

I, too, have the same issue on FreeBSD 14.1-RELEASE-p5, following a Nextcloud upgrade.

@Rudiberto
Copy link

Rudiberto commented Nov 8, 2024

Do we have yet a solution for this Problem? Since that day my backup is not working!
:-(

Machine is Linux Ubuntu 22.04 - Nextcloud 3.14.3-20241107.180900
Server version 29.08

@tarastella
Copy link

@Rudiberto as temporary workaround, I am using something like "nextcloudcmd -u user -p $(cat $passwordfile)".

@Rudiberto
Copy link

[@Rudiberto] as temporary workaround, I am using something like "nextcloudcmd -u user -p $(cat $passwordfile)".

Thank You, very much. I will test that.
I'm passing temporarily user and password inside my script. Guess it makes not that much difference to your solution.
Hopefully it will work again soon. It's never a good sign, when something so essential is not working properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop approved bug approved by the team
Projects
None yet
Development

No branches or pull requests

8 participants