Thanks Tony! I'm not sure I know where Metabase is running. I thought it was running on a google cloud docker server and I would access it from an IP address + 3000 link that I had saved in my bookmarks. I'm not aware that it runs somewhere else and how I would access the logs. Can you explain more what else it might be running on and how I would access that? Thanks!
Hey @nemanja, thanks for the help! I can login to the google cloud account, and everything seems to be running fine. I think it's using docker, but that's all I really know.
Yeah I understand that it's hard to help without knowing how it was set up, but I guess I feel like there has to be a way for me to figure out how it was set up.
Where would I go about looking to start figuring out how it was set up?
I haven't tried contacting google support yet, but yes I'm still getting billed from google cloud roughly the same amount as previous months. I think with google cloud you have to pay extra in order to get tech support.
Thanks @Luiggi ! It looks like the IP address is still the same. I'm not sure how to check the 2nd thing, but do you know if that's something that could have changed without someone changing it? No one ever logs into these accounts, so I can't seem to figure out why anything would have changed after working fine for over a year.
Unfortunately I don't know, infrastructure can be tricky to debug if you don't have many controls in place to wipe out possible errors. If you hit the IP and you can't connect to Metabase then it might be because Metabase is listening on a hostname (e.g. something.com).
Depends on the version you're running. Some versions ago we had a bug that the hostname was set up in the first hit to the instance, so the hostname could change without users noticing if you hadn't set up it via environment variables