Mind if I ask do you use coolify? Or
Mind if I ask do you use coolify? Or something else? I use coolify and with internal it gives me the same error u wrote and with public url it just shows me postgres timeout
20 Replies
hey yes I use coolify but not the template I have my own compose file following the convex docs for easier maintaining
I explained my setup here: https://discordapp.com/channels/719702312431386674/1383661609758490774/1385033690530447400
I'm also a maintainer at coolify so happy to help if you run in to any issues
if the public url doesn't work as well make sure to check your firewall rules at vps provider level as well as on machine like ufw
for the internal url you must enable "connect to predefined network" checkbox for your services
Hi! Oren same boat here I checked the connect to predifined networks in my convex service and it still shows
the public url works file when access via tableplus but throws postgres connection timeout
also my normal convex works fine when not connecting to db
can you check if your postgres url starts with "postgresql://" and doesn't have db name at the end
checked āļø
it should be like: postgresql://${{PGUSER}}:${{POSTGRES_PASSWORD}}@${{PRIVATE_URL}}:${{PGPORT}}
thats the value for POSTGRES_URL env var in your backend service
not working public url makes me think it is either the env var setup incorrectly, you shouldn't have problem with public url at all
also remember DO_NOT_REQUIRE_SSL=true
its set to 1
try with true
I posted my whole env and setup here https://discordapp.com/channels/719702312431386674/1383661609758490774/1385033690530447400
my whole setup is https://discord.com/channels/1019350475847499849/1393081247152078858 here, um i do not see any particular difference
i tried with true it still fails to look up want me to try it with ur docker compose?
i am currently using the default convex github recommends not the template
my compose should be similar to convex docs as well, one thing I noticed in your recording is you are using pgvector's pg image not sure if it might cause any difference
it does not I tried with both
i have been trying this for like 6 hrs
good old missing a semi colon i bet
š
yeah maybe try with my compose setup as a new service
if not happy to jump on a call to compare our setups
having problem with public url makes me question something in the setup is off, I never had a problem with public url
i think do not require ssl to true instead of 1 might fix the issue i think i haven't tried that with public url
but i will try your setup and if not i might come and seek ur guidance
Hmm not working I am also gonna try ur setup it's 1 am here so probably tomorrow
Oren everything works if i copy ur setup in tanstack thread ty
only the integrations are not working any idea? they recently made it so that integrations work when self hosting
I am on Convex v1.25.1
Honestly It could be a dashboard version related thing since we are using convex backend latest while using a select version of dashboard
Yup changing the dashboard version fixes it
Thank you oren
happy to hear that, good luck with your projects folks
sorry to hijack this thread, came across your convex self hosted setup, and tried it, but it seems like i keep running into this error, when trying to implement my postgres url. is it true that once i start a convex backend/ dashboard instance that is built on the base sqlite, i cannot simply add a postgres url to env var and force it to use my postgres db? so i just simply need to recreate a new convex self hosted instance with the right postgres url from the start?
I would recommend creating a new instance, you can backup the existing one with "npx convex export" and then in new instance with postgres "npx convex import" https://docs.convex.dev/database/import-export to not lose any data
errors you shared doesn't seem to be related to that, seems like it is failing to resolve addresses e.g. internal urls
I know once you connect postgres, it will throw if you try to go back to sqlite but never tried with your steps before, might be possible
right, i was following half and half, and knew i messed up somewhere in the middle. because i started off directly with coolify's current docker compose files, and then tried replicating yours by simply copy pasting the contents of the compose file. now im doing a clean fresh installation directly from yours, and it seem thats what i shouldve done from the start.
thanks alot!!