Open ash-development opened 1 month ago
i'd also like to note that the database connects fine when ran with a local dev instance, it simply just fails when deploying in vercel.
this is the error that is displayed on the actual deployed page:
hii @ash-development, have you found a way to fix it?
@h4MeMengoding nope 🤷🏼♀️ i just gave up because this was after two days straight of troubleshooting. wasn't THAT worth it to me lol. its very odd that the database works with a dev installation (still via remote SQL database) but not thru prod with hosting on vercel
it seems that support for self-hosting is pretty nonexistent unfortunately
me too!, 2 weeks ago I tried to find the problem for 1 week in a row, and no results, it seems that dub prioritizes its users only using their web version, maybe
@ash-development what are you using for the MySQL proxy? Where is your MySQL DB hosted on? That could be the source of the error here
I'm also seeing this same issue. Any luck on getting this to work?
@ash-development what are you using for the MySQL proxy? Where is your MySQL DB hosted on? That could be the source of the error here
using both of these via docker compose, had to change the ports as the originals are also running on my server lol https://github.com/ash-development/my-dub/blob/main/apps/web/docker-compose.yml
i am currently trying to self-host Dub based off of this repo. i am running into the following errors:
i have set up my mysql and planetscale proxy based off of this docker compose file and added them as environment variables in vercel as follows:
the only thing the build logs display as errors are what is below, although i doubt that it is directly related to the error. any help is appreciated, thank you!!