7 months ago
Hi!
I can't seem to connect to the mssql database using the tool from microsoft. I took the public proxy port and address from the variables + used the sa user + the sa password and left the certificate optional. Can you help me login to the server?
0 Replies
6 months ago
what error are you getting?
6 months ago
do you give me permission to attempt the connection myself?
6 months ago
i can connect just fine with dbgate
6 months ago
6 months ago
you don't need to use it, it just means that there's no issues with the database or connection
6 months ago
it's something
6 months ago
correct
6 months ago
this isn't anything on the railway side of things
6 months ago
yes because trial users attempt to deploy it not knowing that you need hobby to run it
ooooh, okay
so it's not something like "template needs perfecting" it might in fact be readable as "templates not used right"?
6 months ago
it could be either, but in this case it is the latter
It's the fact that SSMS (the official tool) is unable to parse ports at GUI data entry for servers. So you can't do server:port, you have to go to the tab Additional Connection Parameters and write it like this:
Data Source=yourrlwypublicaddres.proxy.rlwy.net,YourPortNumberNoQuotes;
Anything written there overrides the info you write in the default server connection tab
However, one must select mandatory encryption and most likely also check the field "trust server certificate" in the first tab
6 months ago
so you got it to connect?
Turns out this is a universal piece of info you can pass to other sufferers of Microsoft unique software design
it's always the formula: server,port if you have a non-default port for their services