this post was submitted on 29 Sep 2024
11 points (86.7% liked)

Selfhosted

40211 readers
1242 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Hi. I've installed Filestash in a Docker container, which included passing a previously generated Dropbox access token to Filestash, as per the yaml file on the gihub page.

  • DROPBOX_CLIENT_ID=<dropbox_key>

When I connect to Filestash (just set up locally for now), and then click to connect to Dropbox, I get the following error from the Dropbox webpage that opens:

**Error (400) It seems the app you were using submitted a bad request. If you would like to report this error to the app's developer, include the information below.

More details for developers

Invalid client_id: .**

There's nothing that looks like an error in the Filestash logs. I've generated new tokens and tried again, same result.

Has anyone managed to add Dropbox to Filestash, and if so, would you mind explaining the steps you took?

(I've since set it up for external access via my domain, and npm, same error).

Thanks Rob

you are viewing a single comment's thread
view the rest of the comments
[–] catloaf@lemm.ee 1 points 1 month ago

Seems like a bug in the app. I'd open an issue on the project.