You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have DrawIO self-hosted on our own GCP infrastructure. We tried to publish a diagram that is saved on Google Drive but whenever we try to access the diagram through the generated link, we always get this error:
We validated the authorized redirect URI for the Google Drive API credentials in the GCP project and they're correct. It is the same URL that is mentioned in the error details of this popup. We also tried to add other entries with or without a slash at the end and also with "http" or "https" but nothing worked.
We also validated the DRAWIO_VIEWER_URL and DRAWIO_LIGHTBOX_URL parameters and they're correct.
We updated to the latest version and it didn't fix ths issue either.
Finally, we tried disabling/enabling third party cookies but it didn't solve the issue.
Is there any extra step that is necessary to do in order for the Publish feature to work correctly on our own infrastructure?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We have DrawIO self-hosted on our own GCP infrastructure. We tried to publish a diagram that is saved on Google Drive but whenever we try to access the diagram through the generated link, we always get this error:
We validated the authorized redirect URI for the Google Drive API credentials in the GCP project and they're correct. It is the same URL that is mentioned in the error details of this popup. We also tried to add other entries with or without a slash at the end and also with "http" or "https" but nothing worked.
We also validated the DRAWIO_VIEWER_URL and DRAWIO_LIGHTBOX_URL parameters and they're correct.
We updated to the latest version and it didn't fix ths issue either.
Finally, we tried disabling/enabling third party cookies but it didn't solve the issue.
Is there any extra step that is necessary to do in order for the Publish feature to work correctly on our own infrastructure?
Beta Was this translation helpful? Give feedback.
All reactions