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

Using dashboardUrl does not function properly #46

Open
audiovention opened this issue Nov 10, 2023 · 5 comments
Open

Using dashboardUrl does not function properly #46

audiovention opened this issue Nov 10, 2023 · 5 comments

Comments

@audiovention
Copy link

I followed the instructions and deployed packages/dashboard in my cloudflare pages.
The initial page loads fine, but navigating is impossible as the routing doesn't function properly when dashboardUrl is specified,
i.e. requests like mysub.mydomain.com/storage/bucket-name return 404

@G4brym
Copy link
Owner

G4brym commented Nov 10, 2023

Can you share the url for your instance in read only

@audiovention
Copy link
Author

No, sorry. Already moved it behind zero trust. The steps to reproduce are absolutely minimal.

  • npm create r2-explorer@latest and deploy
  • fork and create Cloudflare page for packages/dashboard (pointing to the master branch - maybe that's a problem, should I use the latest release tag?)
  • change dashboardUrl to the cloudflare page url and re-deploy worker

@audiovention
Copy link
Author

Oh and btw, I've temporarily removed the dashboardUrl option (so I'm using the default public frontend) and everything is working fine.

@G4brym
Copy link
Owner

G4brym commented Nov 15, 2023

I've just setup everything on a new account and it is working fine
when you enable the dashboardUrl, do you see any buckets on the sidebar? can you confirm the r2-explorer version you are using by accessing this path in your worker domain /api/server/config

@audiovention
Copy link
Author

Figured out my issue, when I deployed to cloudflare pages I didn't have a build step, so I was just uploading the Vue source.
Maybe consider adjusting the docs about that, it's not obvious for non-web people.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants