Version 2025.2.2 on Linux not starting

Hello,

Starting "/usr/bin/devolutions-gateway --service" manually gives no output.

This is strange. Try to remove `--service`, and see if you get an output? `--service` is intended to be appended only by the service manager, and it may have an impact.

strace output stops right after reading the ssl certificate and key

If I had to make an educated guess, I think it may be related to this:


If the certificate does not contain these extensions, the Gateway will now fail as soon as possible, potentially on startup.
The reason is that these extensions are required by more and more clients (e.g.: Chrome, macOS), and it’s much harder to troubleshoot when it works with some client and not others.

Let me know how it turns out! If you really need to use such a certificate, let me know, we could add an option to let it pass through.

Best regards,

oh, silly, when running without the --service parameter it properly outputs an error message which mentions MISSING_SERVER_AUTH_EXTENDED_KEY_USAGE.
It would be even better if the message had ended up in the logs as well, but I should've tried this :)
The certs are self-signed so I can just recreate them with the proper extensions. Thanks!

It would be even better if the message had ended up in the logs as well, but I should've tried this :)

Agreed! The tricky part is that it’s possible to configure the path of the log file in the configuration file, and so it’s difficult to log anything into the log file before we are done handling the configuration.
That being said, it could be possible to process partially the configuration file, or to delay the actual processing of the TLS configuration part, we could try to include more things in the logs, even if it’s not possible to include everything.

I was also thinking about issuing syslogs, so you could use tools such as journalctl for instance.

The certs are self-signed so I can just recreate them with the proper extensions. Thanks!

Great! Happy I could help. Let me know if you have any other question.

Have a great day,

Syslog is more the Linux way of handling stuff, and the deb package could drop a config file in /etc/rsyslog/conf.d directory to configure the logfile.
Good to know that the logfile can be moved to a different location, because tbh the default location of /etc/devolutions-gateway was bothering me :)

Just saw the release notes of the latest version! <3

Hi!

I’m happy to see you are pleased with the release notes ;)

We just finalized the release a few hours ago, please give it a try!

Let me follow up on this previous message:

Syslog is more the Linux way of handling stuff, and the deb package could drop a config file in /etc/rsyslog/conf.d directory to configure the logfile.

Indeed. I have a work in progress for basic syslog support for Linux/macOS, and Windows Events Logs for Windows, unfortunately, I couldn’t deliver that for the 2025.2.3, but I’m confident I can get something ready for 2025.2.4. My thinking is not to completely replace the current gateway.log files though. Syslog isn't designed for high-volume, very verbose application logs, or so I heard, as these could flood or overwhelm the syslog daemon. There is even a maximum message size to be mindful of, although it’s configurable. Instead, I’m thinking about an hybrid approach where we would only use syslogs for high-level logs such as:

• Errors,
• Warnings,
• Security-related events,
• Startup/shutdown messages.

And we would keep using our rotational logs for all the other details.

I’ll need to dig a little bit more the rsyslog configuration though, I never used it personally.

Good to know that the logfile can be moved to a different location, because tbh the default location of /etc/devolutions-gateway was bothering me :)

Actually, I just realized we didn’t officially stabilized this option, but it’s called `LogFile`, you can add that in your `gateway.json` file if you want to give it a try!