Skip to content

Setup wizard custom db ports dont work for dbs other than SqlServer #2400

@Furrior

Description

@Furrior

Describe the bug
Setup wizard parses port only for SqlServer, so if you selected other database, it tries to lookup dns for the address and port together which leads to an error.

To Reproduce
Steps to reproduce the behavior:

  1. Run setup wizard
  2. Select one of MariaDB, MySql, PostgresSql
  3. Enter <any ip or domain>:<any port>
  4. See error Unable to resolve address: Name or service not known

Expected behavior
To parse address and port correctly like it does with SqlServer

Logs

Welcome to tgstation-server!
This wizard will help you configure your server.

What port would you like to connect to TGS on?
Note: If this is a docker container with the default port already mapped, use the default.
API Port (leave blank for default of 5000):


NOTE: If you are serious about hosting public servers, it is HIGHLY reccommended that TGS runs on a database *OTHER THAN* Sqlite.
It is, however, the easiest option to get started with and will pose few if any problems in a single user scenario.
What SQL database type will you be using?
Please enter one of MariaDB, MySql, PostgresSql, SqlServer or Sqlite: MySql

Enter the server's address and port [<server>:<port> or <server>] (blank for local): localhost:1234
Attempting to resolve address...
Unable to resolve address: Name or service not known

Server State: (please complete the following information):

  • OS: Linux
  • Version: 6.18.0
  • Database Type/Version: MariaDB, MySql, PostgresSql
  • BYOND Version Used: N/A
  • git Repository Used: N/A
  • Origin Commit hash Used: N/A
  • Active Test Merges: N/A
  • Client Version: N/A

Additional context
The parsing works only with SqlServer

Metadata

Metadata

Assignees

Labels

BugSomething's fuckyReproduction RequiredReproduction steps required for issue

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions