5 Other known problems

Jason Volk edited this page 2021-02-05 21:34:56 -08:00

Before problems, here's a few tips to see whether there is a problem:

• You configure The Construct by using the console (or the !control:SERVERNAME room). Settings get stored in RocksDB. No config file is not a problem.

• Database/configuration is stored in SERVERNAME folder, that's the only parameter you have to use starting the server. You can try various server configurations in parallel by using a different server name.

There are some things which is not yet fixed and knowing it may help to new admins:

• Updating git pulls advised to make cleaned before (re)build. (https://github.com/matrix-construct/construct/issues/84)

• Using LetsEncrypt certificates works well, but you have to give fullchain.pem twice:

  • net listen matrix * 8448 privkey.pem fullchain.pem fullchain.pem

• You may be unsatisfied with the default DNS caching resolvers (namely 4.2.2.2 really breaks things), you can change it as:

  • conf set ircd.net.dns.resolver.servers 1.1.1.1 8.8.8.8 9.9.9.9

• If you screw up the config and the server doesn't start you can force configuration by using environment variables like:

  • ircd_client_sync_linear_buffer_size=524288 bin/construct SERVERNAME

• Your helpful crowd sits in the room #construct:zemos.net (alias #admins:matrix.org, #construct:maunium.net, #construct:colab.de)