This message was deleted.
# secoda-support
w
This message was deleted.
h
I have similar problem to this one https://secodacommunity.slack.com/archives/C01PT4WP0TE/p1629957842000200 can you please support with it?
e
Yup, this is due to an authentication error. Are you using Google Oauth on Metabase or just standard login?
Oh wait, this is due to a configuration issue with your self-hosted deployment. Let me take a closer look.
You'll have to change the
DOMAIN
variable in
.env
to be the IP address/domain of your installed instance of Secoda. Then when you reload the Metabase integration should work as expected @happy-finland-51108
l
Redsfhit is working, but we still have the problem with Metabase @happy-finland-51108
e
Hey @loud-afternoon-54978 I'll take a look into this tomorrow. Thanks for letting me know
l
we have another two problems • views are not showing lineage • we cannot upload logo images cc @happy-finland-51108
👀 1
@elegant-house-93198 thank you
e
Apologies about the delay here. I’ve added these items to our backlog which shows when we’re working on a particular item that you’ve flagged. We’re tracking the bugs and improvements that you’ve both identified here https://www.notion.so/secoda/Klar-mx-feedback-10139b22b2694f749c95eb092370e488. The image upload issue and Metabase issue are both something I’m looking into right now. The redshift lineage and popularity is more tricky because information on views are structured differently in Redshift’s system tables so it will require some work to get that information into Secoda.
🙌 1
@loud-afternoon-54978 @happy-finland-51108 the image upload issue has been fixed!
👍 1