github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #1625] Windows 10 Failed to generate SSL #1202

New issue

Open

opened 2026-05-05 07:35:56 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 07:35:56 -06:00

Owner

Originally created by @ludificorpayne on GitHub (Mar 31, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1625

What happened?

The program fails to generate the requisite SSL keys. Tests and disabling ssl confirmed it works sans key, but I'm not willing to risk not using some kind of security.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

Chocolatey & Github release.

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

Windows

What OS versions are you using?

Server: Windows 10 Home | Version 21H2 |
Client Windows 10 Pro | Version 21H2

Relevant log output

[2022-04-01T00:29:22] INFO: OpenSSL 1.0.2l  25 May 2017
[2022-04-01T00:29:22] ERROR: ssl certificate doesn't exist: C:\Users\USERNAME\AppData\Local\Barrier\SSL\Barrier.pem
[2022-04-01T00:29:28] INFO: service command updated
[2022-04-01T00:29:29] INFO: process started but command is empty, shutting down

Any other information

Sorry man but building and exporting custom SSL keys for the functionality this program provides exceeds my needs and goes way over my head.

I've followed every test on the wiki, installed OpenSSl, reinstalled the program, confirmed the server connects and finally just disabled SSL and it worked, so the problem is just the lack of SSL keys.

I don't know what else I can think of - maybe uninstalling and finding where any configs are to regenerate it? I noticed that deleting the Temp files didn't reset anything, so a fresh install sans configs might work?

Originally created by @ludificorpayne on GitHub (Mar 31, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1625 ### What happened? The program fails to generate the requisite SSL keys. Tests and disabling ssl confirmed it works sans key, but I'm not willing to risk not using some kind of security. ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? Chocolatey & Github release. ### What OSes are you seeing the problem on? (Check all that apply) Windows ### What OS versions are you using? Server: Windows 10 Home | Version 21H2 | Client Windows 10 Pro | Version 21H2 ### Relevant log output ```shell [2022-04-01T00:29:22] INFO: OpenSSL 1.0.2l 25 May 2017 [2022-04-01T00:29:22] ERROR: ssl certificate doesn't exist: C:\Users\USERNAME\AppData\Local\Barrier\SSL\Barrier.pem [2022-04-01T00:29:28] INFO: service command updated [2022-04-01T00:29:29] INFO: process started but command is empty, shutting down ``` ### Any other information Sorry man but building and exporting custom SSL keys for the functionality this program provides exceeds my needs and goes *way* over my head. I've followed every test on the wiki, installed OpenSSl, reinstalled the program, confirmed the server connects and finally just disabled SSL and it worked, so the problem is just the lack of SSL keys. I don't know what else I can think of - maybe uninstalling and finding where any configs are to regenerate it? I noticed that deleting the Temp files didn't reset anything, so a fresh install sans configs might work?

gitea-mirror commented

2026-05-05 07:35:59 -06:00

Author

Owner

@ludificorpayne commented on GitHub (Apr 1, 2022):

I figured this out for anyone curious - the latest version doesn't generate its own SSL, however 2.3.4 does.
I downgraded on both machines, connected them both as a client and a server, then uninstalled 2.3.4 and reinstalled 2.4. It didn't remove the files in %APPDATA%/Local/Barrier and instead used them for the latest version.
The only issue I ran into was needing to delet the previous barrier.randomstring in the TEMP folder, (also in appdata/local) as it was throwing errors about duplicate screen names.

@ludificorpayne commented on GitHub (Apr 1, 2022): I figured this out for anyone curious - the latest version doesn't generate its own SSL, however 2.3.4 does. I downgraded on both machines, connected them both as a client and a server, then uninstalled 2.3.4 and reinstalled 2.4. It didn't remove the files in %APPDATA%/Local/Barrier and instead used them for the latest version. The only issue I ran into was needing to delet the previous barrier.randomstring in the TEMP folder, (also in appdata/local) as it was throwing errors about duplicate screen names.

gitea-mirror commented

2026-05-05 07:36:00 -06:00

Author

Owner

@skipmorris commented on GitHub (Apr 5, 2022):

A couple workarounds:
Copy the Barrier.pem from any other Windows machine into: C:\Users$USER\AppData\Local\Barrier\SSL\Barrier.pem
/or/
If you have Git or OpenSSL installed on your Windows box, then:
openssl req -x509 -nodes -days 365 -subj //CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem

@skipmorris commented on GitHub (Apr 5, 2022): A couple workarounds: Copy the Barrier.pem from any other Windows machine into: C:\Users\$USER\AppData\Local\Barrier\SSL\Barrier.pem /or/ If you have Git or OpenSSL installed on your Windows box, then: openssl req -x509 -nodes -days 365 -subj //CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem

gitea-mirror commented

2026-05-05 07:36:02 -06:00

Author

Owner

@ChangcongWang commented on GitHub (Apr 5, 2022):

Thank you, downgrading is the easiest way.

@ChangcongWang commented on GitHub (Apr 5, 2022): Thank you, downgrading is the easiest way.

gitea-mirror commented

2026-05-05 07:36:03 -06:00

Author

Owner

@indrajeetgour commented on GitHub (May 21, 2022):

Thanks @skipmorris for your comment, it workout for me.

What I followed was -

Open the gitbash
went into desire location(my case dir was - /c/Users/USERNAME/AppData/Local/Barrier/SSL )
generated the certificate as mentioned by @skipmorris, like this
openssl req -x509 -nodes -days 365 -subj //CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem
the sooner the Barrier.pem is generated, my another machine popup to ask for accept the certificate from barrier server.
That all was required in my case.

Hope this will help few of us, in future.

@indrajeetgour commented on GitHub (May 21, 2022): Thanks @skipmorris for your comment, it workout for me. What I followed was - - Open the gitbash - went into desire location(my case dir was - /c/Users/USERNAME/AppData/Local/Barrier/SSL ) - generated the certificate as mentioned by @skipmorris, like this ` openssl req -x509 -nodes -days 365 -subj //CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem` - the sooner the `Barrier.pem` is generated, my another machine popup to ask for accept the certificate from barrier server. - That all was required in my case. Hope this will help few of us, in future.

gitea-mirror commented

2026-05-05 07:36:04 -06:00

Author

Owner

@Fauzdar1 commented on GitHub (Jul 16, 2022):

Thanks @skipmorris for your comment, it workout for me.

What I followed was -

Open the gitbash

went into desire location(my case dir was - /c/Users/USERNAME/AppData/Local/Barrier/SSL )

generated the certificate as mentioned by @skipmorris, like this
openssl req -x509 -nodes -days 365 -subj //CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem

the sooner the Barrier.pem is generated, my another machine popup to ask for accept the certificate from barrier server.

That all was required in my case.

Hope this will help few of us, in future.

Thank you @indrajeetgour, I just used your solution to make it work in Windows and it worked properly. For others, they can find the detailed solution for both MAC and Windows here.

@Fauzdar1 commented on GitHub (Jul 16, 2022): > Thanks @skipmorris for your comment, it workout for me. > > What I followed was - > > * Open the gitbash > * went into desire location(my case dir was - /c/Users/USERNAME/AppData/Local/Barrier/SSL ) > * generated the certificate as mentioned by @skipmorris, like this > ` openssl req -x509 -nodes -days 365 -subj //CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem` > * the sooner the `Barrier.pem` is generated, my another machine popup to ask for accept the certificate from barrier server. > * That all was required in my case. > > Hope this will help few of us, in future. Thank you @indrajeetgour, I just used your solution to make it work in Windows and it worked properly. For others, they can find the detailed solution for both MAC and Windows [here](https://github.com/debauchee/barrier/issues/1609#issuecomment-1186281717).

No labels

Rows
Columns