Connecting to ClickHouse
Just deployed the Plausible template. I connected to Postgres with TablePlus. But not sure how to do it with ClickHouse. Gettting errors.
24 Replies
Project ID:
bf2ae1ac-d8c4-4c77-8f8a-581f43851d8dbf2ae1ac-d8c4-4c77-8f8a-581f43851d8d
it crashed at first btw, but after restart everything is working fine. It's recording events.
does clickhouse communicate with http or tcp?
@Brody i think it can do both. https://clickhouse.com/docs/en/guides/sre/network-ports
I have tried connecting via http and tcp with all the various ports. Used the urls in the settings -> networking panel.
The docker app uses this connection url, which seemingly works.
"h ttp://default:@password@clickhouse:8123/plausible_events_db"
@Brody Did you make the Umami template? Not sure if its intentional but I did have to add these last 3 ENVs to make it possible to use the data browser and connect via GUI. Otherwise it's really nice, ill enjoy checking it out.
I'm not the original creator, but I was recently given it to do a refresh, and I intentionally left those variables out, I really can not recommend you use the built in data browser, I recommend using proper desktop softwares like dbgate
you can only access http apps external from 443
I intentionally left those variables out@Brody I thought they were needed to connect via a desktop app, but now I connected without them so seems not.
they aren't, they are just used by the inbuilt data browser
only thing you would have needed to do was enable the tcp on the database like the overview noted
@Brody Yup
Could not connect with 443 from http on clickhouse
do you have a PORT service variable set to 8123
also, just a friendly reminder #🛂｜readme #5
Ah ok wont ping you more. I wasn't getting notified of this thread but I think I fixed it now.
no worries
I did add one now and redeployed. Same message.
is clickhouse running on host 0.0.0.0?
ClickHouse docs say 127.0.0.1 / localhost. So not 0.0.0.0 by default I'm guessing. I'm not sure how to set the host, did random ENVs in dockerfile but nah.
did random ENVs in dockerfile but nah.read their docs
clickhouses?
yes
you should try the tcp proxy too
yes did
seems the next step is to dig deeper into docker and clickhouse to continue on this
then yeah my recommendation would be to familiarize yourself with the technologies involved, read through clickhouse's docs
is it possible to look inside the clickhouse volume. Did you make a template for that actually?
i have made a filebrowser template, but you have to deploy that and then swap the volumes around
if youre going to do that, please make sure to read the overview
will do