Cannot create pCloud config file on OSX

Firefox as well.
I have just realized that pcloud has registered the rclone access (look at the screenshot).

...but rclone is showing the error message.

i have the same link app as you.

and just now i created a second pcloud remote.
again, no problem.

C:\data\rclone\scripts>rclone config show pcloud:
[pcloud]
type = pcloud
token = {"access_token":"redacted","token_type":"bearer","expiry":"0001-01-01T00:00:00Z"}

C:\data\rclone\scripts>rclone config show pcloud01:
[pcloud01]
type = pcloud
token = {"access_token":"redacted","token_type":"bearer","expiry":"0001-01-01T00:00:00Z"}

C:\data\rclone\scripts>rclone lsd pcloud:
          -1 2020-04-07 16:32:01        -1 Crypto Folder
          -1 2020-04-07 16:25:09        -1 My Music
          -1 2020-04-07 16:25:09        -1 My Pictures
          -1 2020-04-07 16:25:09        -1 My Videos
          -1 2020-04-07 16:27:54        -1 System Volume Information

C:\data\rclone\scripts>rclone lsd pcloud01:
          -1 2020-04-07 16:32:01        -1 Crypto Folder
          -1 2020-04-07 16:25:09        -1 My Music
          -1 2020-04-07 16:25:09        -1 My Pictures
          -1 2020-04-07 16:25:09        -1 My Videos
          -1 2020-04-07 16:27:54        -1 System Volume Information

I do have still no remotes found in rclone config...

After removing the linked rclone application in pcloud I have tried it again. Same result, rclone got registered again in pcloud but rclone shows the same error message as always. :slightly_frowning_face:

No difference if I try to create a new remote or try a headless connection.

Yesterday, I have registered a new pcloud account and had the same issues with it.
So, one question is remaining. What could I have done different than you guys?
It's a little bit frustrating.

Is there any chance to create the json message myself for a headless installation by taking the information pieces from the debug log? I ask, because it seems to me that pcloud does register rclone correctly.

After looking through this thread, I remembered that the two-factor authentication on pCloud had to be turned off as well. Do you have two-factor authentication turned on in your new pCloud account? We turned it off to get the account setup, then turned it back on after getting pCloud and Rclone connected. It works correctly without error after that.

The 2FA is by default turned off in pcloud and I did not change that. I am trying to configure a rclone connection with a new account in pcloud.

To be honest, it is very strange.
I am able to configure Dropbox and Google Drive,no problem at all.

Then I have installed Windows7 32bit in a virtualbox...tried again connecting with pcloud...AND GOT THE SAME ERROR MESSAGE AGAIN!
I have absolutely no idea anymore, it seems using 'pcloud' is not possible for me...

Please, help me if you are able to point me in the right direction!

each time you try to create the remote on a different computer, are you?

  • creating a new config file for each computer
    or
  • reusing the same config file for each machines

I was trying to create new config files with new rclone installations. But I did try headless connections with ' ' rclone authorize "pcloud" 'as well.
And the config file was always empty (did not even exist), before and after.

the common denominator seems to be your pcloud.com account.
what else could it be?

create a new free pcloud account, using a different email address, do not change any settings.
then making sure not to use a preexisting config file, create a remote with rclone.

I know. I have done this already yesterday but with no sucess.
What I think is strange, is that pcloud is registering the rclone application sucessfully but rclone does not save the token because of an error...

Here, the screenshot, again.

have you contacted pcloud?

They will answer that rclone is registered successfully, I guess. :slightly_smiling_face:

Btw., I really appreciate that you trying to help me to figure this out!

I guess, the reason for the problem has to do with this section:

2020/06/30 14:53:24 DEBUG : HTTP RESPONSE (req 0xc0003f6c00)
2020/06/30 14:53:24 DEBUG : HTTP/1.1 200 OK
Connection: close
Content-Length: 57
Cache-Control: private, max-age=0
Content-Type: application/json; charset=utf-8
Date: Tue, 30 Jun 2020 12:53:24 GMT
Etag: "EtixHW............................"
Server: CloudHTTPd-API v1.1
Vary: Accept-Encoding
X-Error: 2012

{
"result": 2012,
"error": "Invalid 'code' provided."
}
2020/06/30 14:53:24 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2020/06/30 14:53:24 DEBUG : Closing auth server
2020/06/30 14:53:24 DEBUG : Closed auth server with error: accept tcp 127.0.0.1:53682: use of closed network connection
2020/06/30 14:53:24 Failed to configure token: failed to get token: oauth2: server response missing access_token

That message came from pcloud, so it seems like that they

  • have registered rclone successfully
  • have told rclone that the registration was invalid

So that looks like a bug somewhere.

I know pcloud have been re-doing their oauth flows recently so it is possible that there is a bug in their flow which affects your account for some reason.

One reason might be that you have an unusual character in your name or password or email address. We had a bug in the mega login which wouldn't work if the password had some unusual characters in!

Ok, thank you for your answer.
I will ask them to look into it.

Their answer has been fast but not really satisfying.

Hello,

Thanks for your e-mail.

If rclone send us a message that there's problem with their app when it's used with pCloud, we are going to assist them but we do not support rclone.

If there's an error message, you should contact rclone.

If you have any additional questions, please don't hesitate to ask.

Regards,

George Lewis,
pCloud Tech Support

I also want to point out that I am only using normal (english) alphanumeric characters in my email address and password - but you'll never know. :thinking:

Of course, I have asked them again to have a look into their log files to figure it out because the issue seems being conntected to my pcloud account (although I am having the same issue with a second pcloud account as well).

i just created a good pcloud remote on my android phone.
i used chrome as the browser.

i just created a good pcloud remote on my ubuntu seedbox.