hwittenborn / celeste

GUI file synchronization client that can sync with any cloud provider
GNU General Public License v3.0
1.19k stars 39 forks source link

Can't connect to any provider #126

Open lduktus opened 1 year ago

lduktus commented 1 year ago

I am currently running Silverblue 38, tried Celeste from Flathub and Flathub Beta. I tried to connect to:

No success at all, after the login in my browser I always got an error message. Steps I tried for debugging:

  1. I tried to run Celeste from within a terminal and it opened with an error (main panicking)
  2. After rm -r ~/.var/app/com.hunterwittenborn.Celeste/ I was able to run Celeste from withtin a terminal
  3. This time an error occurs even before coming to the login part

Here a dump of the error message:

2023/08/24 11:52:35 NOTICE: Config file "/var/home/username/.var/app/com.hunterwittenborn.Celeste/config/celeste/rclone.conf" not found - using defaults
Warning: STATE URL: 
Warning: DEBUGGING: 2023/08/24 11:52:52 NOTICE: Config file "/var/home/username/.var/app/com.hunterwittenborn.Celeste/config/rclone/rclone.conf" not found - using defaults
2023/08/24 11:52:52 NOTICE: Make sure your Redirect URL is set to "http://127.0.0.1:53682/" in your custom config.
Error: config failed to refresh token: failed to start auth webserver: listen tcp 127.0.0.1:53682: bind: address already in use
Usage:
  rclone authorize [flags]

Flags:
      --auth-no-open-browser   Do not automatically open auth link in default browser
  -h, --help                   help for authorize

Use "rclone [command] --help" for more information about a command.
Use "rclone help flags" for to see the global flags.
Use "rclone help backends" for a list of supported services.

2023/08/24 11:52:52 Fatal error: config failed to refresh token: failed to start auth webserver: listen tcp 127.0.0.1:53682: bind: address already in use

Rocket has launched from http://127.0.0.1:8000
Adwaita-Message: 11:52:53.411: AdwMessageDialog mapped without a transient parent. This is discouraged.
Adwaita-Message: 11:52:53.921: AdwMessageDialog mapped without a transient parent. This is discouraged.
  1. Cleaning leftover files & reinstalling, results in the same error message as printed above

And as a sidenote: I love the idea of this app. I would love to replace my rclone scripts with a nice GUI, that ideally will integrate nicer into my desktop (handling passwords, encryption, etc.) and maybe integrates other rclone providers. Thanks for the development!

hwittenborn commented 1 year ago

Hey @lduktus, terribly sorry for the delay on my part. I tried to make it fairly obvious in the GUI, but the issue you're experiencing is from the port used for authentication already being in use:

2023/08/24 11:52:52 Fatal error: config failed to refresh token: failed to start auth webserver: listen tcp 127.0.0.1:53682: bind: > address already in use

There was an issue where if authentication was cancelled that that port issue might start happening, but that was fixed a couple months back (specifically in v0.5.0).

Has restarting your system fixed the issue? When that port issue was happening that was what fixed it for me. If not that then I'm suspecting it might be an issue with the Flatpak, but I haven't ever had any issues in my local testing.

Thanks for the kind words as well! I appreciate it a ton :)

lduktus commented 12 months ago

Hey @hwittenborn, sorry for my late reply. I had no time and hadn't my Linux Machine around. Nope restarting and reinstalling didn't fixed the issue.

I tried v0.8.0 from a shell inside the Flatpak. It is kind of weird:

I also changed my default Browser from Junction to Brave and afterwards to a completely clean Firefox Profile, however this doesn't seem to be the problem.

Screenshot from 2023-11-14 11-44-08

hwittenborn commented 11 months ago

You're all good @lduktus. Regarding that Google Drive issue, that got fixed up a few minutes ago (see https://github.com/hwittenborn/celeste/issues/161#issuecomment-1817710686).

Regarding that issue with pCloud, I'm not quite sure what's going on. With the new changes from the above issue comment I was able to sign in to both Dropbox and pCloud just fine, so I think we should see how things behave for you after that gets done.