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

public links are not working after updating to the latest version #8347

Closed
Shra25 opened this issue Aug 17, 2018 · 8 comments
Closed

public links are not working after updating to the latest version #8347

Shra25 opened this issue Aug 17, 2018 · 8 comments
Labels
Administration/Permissions Collection or Data permissions Priority:P3 Cosmetic bugs, minor bugs with a clear workaround Reporting/Dashboards Type:Bug Product defects

Comments

@Shra25
Copy link

Shra25 commented Aug 17, 2018

browser and the version: Chrome Version 68.0.3440.106 (Official Build) (64-bit)
operating system: Windows 10
databases: MySQL Metabase version: 0.30
Metabase hosting environment: Linux/Ubuntu 16.04
Metabase internal database: H2 (default)
Repeatable steps to reproduce the issue
public links are not accessible

@Shra25 Shra25 changed the title public links are not working after updating to the latest version public links are not working after updating to the latest version.browser and the version: Chrome Version 68.0.3440.106 (Official Build) (64-bit) Your operating system: Windows 10 Your databases: MySQL Metabase version: 0.30 Metabase hosting environment: Linux/Ubuntu 16.04 Metabase internal database: H2 (default) Repeatable steps to reproduce the issue public links are not accessible Aug 17, 2018
@Shra25 Shra25 changed the title public links are not working after updating to the latest version.browser and the version: Chrome Version 68.0.3440.106 (Official Build) (64-bit) Your operating system: Windows 10 Your databases: MySQL Metabase version: 0.30 Metabase hosting environment: Linux/Ubuntu 16.04 Metabase internal database: H2 (default) Repeatable steps to reproduce the issue public links are not accessible public links are not working after updating to the latest version Aug 17, 2018
@lwqcz
Copy link

lwqcz commented Aug 17, 2018

Can you share an image of issue or what was done before issue occured, even some log file records about this issue? It would help a lot.

@mazameli
Copy link
Contributor

Are you getting a 404 when trying to go to a public link? Is this only happening with old public links, or only with new ones, or both?

@Shra25
Copy link
Author

Shra25 commented Aug 18, 2018

Not tried with new links because of already many people using the old links and I cannot update everywhere with new links.

@jornh
Copy link
Contributor

jornh commented Aug 19, 2018

Linking to the related Discourse #bug-report

@mazameli
Copy link
Contributor

I tried all of our own previously existing public dashboard and question links, and all of them worked.

Could you provide a screenshot with sensitive data scrubbed out to show us what you're seeing (or not seeing)? We'll need to figure out if there are any commonalities between the questions/dashboards that aren't working. Any javascript or server log errors that you can provide would also be helpful.

@Shra25
Copy link
Author

Shra25 commented Aug 21, 2018

check server log

08-21 10:43:39 INFO middleware.cache :: Query took 52 ms to run; miminum for cache eligibility is 300000 ms
08-21 10:43:39 DEBUG metabase.middleware :: GET /api/public/dashboard/-----/card/258 200 (58 ms) (16 DB call s). Jetty threads: 8/50 (8 busy, 3 idle, 0 queued)
08-21 10:43:39 INFO middleware.cache :: Query took 71 ms to run; miminum for cache eligibility is 300000 ms
08-21 10:43:39 DEBUG metabase.middleware :: GET /api/public/dashboard/-----/card/265 200 (80 ms) (16 DB call s). Jetty threads: 8/50 (7 busy, 4 idle, 0 queued)
08-21 10:43:39 DEBUG metabase.middleware :: GET /api/user/current 401 (114 µs) (0 DB calls).

@toddheslin
Copy link

I had this same issue and it was actually a problem with one of the dashboard cards. After the recent upgrade it went a bit funky but the result was that the public URL was returning a 400 error.

After I removed this card, the report worked.

The preview looked like this:
image

But the actual display on the dashboard looked like this:
image

Couldn't quite pin down what the issue was but deleting and re-adding the card worked.

@salsakran salsakran added Type:Bug Product defects Priority:P3 Cosmetic bugs, minor bugs with a clear workaround Reporting/Dashboards Administration/Permissions Collection or Data permissions labels Dec 28, 2018
@flamber
Copy link
Contributor

flamber commented May 25, 2020

Closing, since without detailed logs or reproducible steps, it's hard to know what happened.

@flamber flamber closed this as completed May 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Administration/Permissions Collection or Data permissions Priority:P3 Cosmetic bugs, minor bugs with a clear workaround Reporting/Dashboards Type:Bug Product defects
Projects
None yet
Development

No branches or pull requests

7 participants