Bootstrap mode fail with error 500, no more hints anywere

General
1

Hi,

I was trying stalwart 0.16.4, and when booting and doing the setup I receive a 500 error, I’m trying to configure it with SQLite and everything stored in it.

I could boot another testing instance and worked fine, the only difference I see in this environment is that I do have the port 80 and 443 used by an http server which is actually going to proxy stalwart http access.

Another point in the new setup I do not see options to enable/disable/configure any of the listeners or services, this is probably going to create issues with the existing http server.

2

You could always try stopping your proxy server and run the setup again to confirm? You edit the listener bindings in bootstrap mode. Connect to http://<hostname>:8080/admin and go into Settings > Network > Listeners. You can change IP and port bindings there.

3

Hi,

Yes I was thinking to do that, but I need to do some fancy tunnel for avoid to do a setup on clear net, anyway I do not see any menu from admin mode, I didn’t manage to arrive at the level that I see any menu, I’m still in bootstrap.

Is there any way I can see the enable additional logging? like a “RUST_LOG” env variable ? (spoiler, tried that and it don’t works)

Obviously no I can’t open the Settings menu.

yes I went trough the docs here Console | Stalwart

Also OpenTelemetry | Stalwart

OpenTelemetry is an open-source standard for distributed tracing and metrics. It defines a common set of APIs, SDKs, and collector services that applications use to emit traces, logs, and metrics to an observability backend.

Sure I can read that from the homepage of opentelemetry

OpenTelemetry is an open source observability framework for cloud native software. It provides a single set of APIs, libraries, agents, and collector services to capture distributed traces and metrics from your application.

But still I do not know how to enable the logs if I do not have a UI working …

I’m going to hack in the code soon, but I’m giving the docs and this forum a chance

4

Hi,

So I figured out some of the issues, when I was configuring the sqlite storage I was putting there the path of the parent folder instead of the path of the file, I figure this out removing the proxy, when I did that the error showed up in the right place, not sure what was messing with it, I do need to investigate more.

So for anyone coming by be aware of the path of the sqlite config need to be a file.

Will update when I do get more details on where the real error got lost.