Any attempt to download dashboard as PDF fails with error


(Vik) #1

Here’s the error from the log.

2019-02-09 16:43:55.559 +0530 [INFO|00850|event:render] :: chromium_render:, type=‘pdf’, target_type=‘wysiwyg_dashboard’, render_success=‘false’, render_message='An attempt was made to access a protected resource: […]

tried both chromium and chrome - always the same.

(Nicholas Wong) #2

Hey Vik! In order to download your file from looker, press on the gear button on the most right hand side. (Just located beside the run button as shown below)

Click on the “Download…” tab from the drop down and you will get the download options.

If you’re facing an error trying this method, perhaps you might want to share your screen? Was it working before you tried pushing a production/editing the lookerML? If it was, perhaps you might want to off the developer option and try downloading it. Hope this helps! :slight_smile:

(Vik) #3


Thanks for your reply. I think you misunderstood the issue.

It’s about downloading a dashboard as PDF. What you are showing is explore as XLS.

(Nicholas Wong) #4

Hmmm my bet! This is an uncommon issue. There is however a similar issue posted on the community in November 2018. You can find the post at Email schedule purgatory when Show Filters is turned off. It will be faster if you contact Looker through the live chat to get your problem solved.

(Izzy) #5

Nicholas is right— This is an uncommon issue that we’re working on fixing! This usually occurs when you try to access something on the looker server on a different port than what looker is running on, and when you use a loopback address instead of the hostname.

If this sounds like something you’ve set up, then changing your config to use the hostname ie: instead of https://localhost:777/catpicture.jpg should fix it.

If not, and if your Looker server is running clustered (another reason it’d be calling out for local resources), then I think Nicholas’s advice is again the best route— contact support :slight_smile:

(Vik) #7

Thanks guys,

Checked the hostname and it’s all right (not localhost or I have reported the issue to the support team.