Won't work with SSL enabled

[dm30]

What happened?

Thank you for these great little tool.
Unfortunately won't connect with client. But unchecking SSL makes connection flawless.
Windows firewall was set to private network when prompted.
Thank you for your help.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

Ubuntu 22.04 software center (2.4.0+gfsg version) Debian package

What OSes are you seeing the problem on? (Check all that apply)

Linux, Windows

What OS versions are you using?

Server: Ubuntu 22.04.
Client. Windows 11

Relevant log output

No response

Any other information

No response

[Desani]

I had the same issue when installing the server on a windows 10 machine. Apparently it is due to the fact that openssl isn't installed and can't be used to generate the required pem file.

I found this github issue and created my own pem file using the openssl command and moved it into the expected folder that was mention in the log file:

#231 (comment)

run in the cmd openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem

[dm30]

Thx. In my view this should be fixed.

[Offbeatmammal]

are there any downsides to having SSL set to off (local, private network)? This took me a moment to figure out (would be nice to have a very visible warning if this issue is encountered to get people working)

[UndyingSisyphos]

As long as port 24800 (the port used by the service) is not open it shouldn't matter if you enable SSL or not, as long as it is actually a private/home network and not the one at work with other employees.
If you use a Desktop as a server then it's fine, just be sure your wifi password is not 1234567890, if it's a laptop I would suggest turning off Barrier every time you connect to a public network, even at your workplace.

[adam4235]

I had the same issue (Linux Mint 21 server, Windows 10 client), am new to using Barrier, followed the instructions and thought it wasn't working. Only by viewing the log file did I discover there was an SSL error, making me think to disable SSL in the options. Took me a while to figure this out, and many users, especially non-power users, might give up.

As mentioned it doesn't seem to be that big a deal for security to disable SSL by default. But if you want to keep it enabled by default, then the instructions should list openssl as a dependency and/or tell people to disable that option if they don't have openssl, I believe.