starred/Quasar

Fork 0

mirror of https://github.com/quasar/Quasar.git synced 2026-04-25 15:25:59 +03:00

[GH-ISSUE #832] When Quaser server runs on Windows Server 2012 R2 it is not able to accept connections from clients #560

New issue

Closed

opened 2026-02-27 15:50:54 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 15:50:54 +03:00

Owner

Originally created by @haxpak on GitHub (Jun 16, 2020).
Original GitHub issue: https://github.com/quasar/Quasar/issues/832

Describe the bug
Unable to run server on Windows Server 2012 R2

System

Server OS: Windows Server 2012 R2
Client OS: Windows Server 2012 R2 / Windows 10 1803
Server installed .NET Framework version: v4.8
Client installed .NET Framework version: v4.8
Quasar Version: 4c4cde446d
Build configuration: Both Debug and Release Tested

Originally created by @haxpak on GitHub (Jun 16, 2020). Original GitHub issue: https://github.com/quasar/Quasar/issues/832 **Describe the bug** Unable to run server on Windows Server 2012 R2 **System** - Server OS: Windows Server 2012 R2 - Client OS: Windows Server 2012 R2 / Windows 10 1803 - Server installed .NET Framework version: v4.8 - Client installed .NET Framework version: v4.8 - Quasar Version: 4c4cde446d1d39d917bf2459916c3aacf89579fd - Build configuration: Both Debug and Release Tested

kerem

2026-02-27 15:50:54 +03:00

closed this issue
added the
cant-reproduce
label

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@MaxXor commented on GitHub (Jun 16, 2020):

Hello, can you confirm that connections on the same server work with localhost? Next, please check with ncat or similar, if the TCP port is accessible from outside? If the clients connect via another network, port forwarding (NAT) must be set up on the router.

Also check out the guide "Getting started": https://github.com/quasar/Quasar/wiki/Getting-Started

@MaxXor commented on GitHub (Jun 16, 2020): Hello, can you confirm that connections on the same server work with `localhost`? Next, please check with `ncat` or similar, if the TCP port is accessible from outside? If the clients connect via another network, port forwarding (NAT) must be set up on the router. Also check out the guide "Getting started": https://github.com/quasar/Quasar/wiki/Getting-Started

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@haxpak commented on GitHub (Jun 17, 2020):

Hi,
Thanks for the prompt response @MaxXor

I have been using quasar for some time now in my engagements.
I was keen on trying the new version with the updated chrome patch.
To do so, I setup the new server build on the existing server 2012 R2 where I am running Quasar currently, stopped the old server (to free up the port) and then ran the new server, after updating my .NetFramework to 4.8

I also imported the old certificate from the previous instance.

Neither did the old clients connect nor did new clients connect to the new server build.

I then ran new build server on a Windows 10 machine, where new created clients were able to connect without any problem.
So I raised this issue.

@haxpak commented on GitHub (Jun 17, 2020): Hi, Thanks for the prompt response @MaxXor I have been using quasar for some time now in my engagements. I was keen on trying the new version with the updated chrome patch. To do so, I setup the new server build on the existing server 2012 R2 where I am running Quasar currently, stopped the old server (to free up the port) and then ran the new server, after updating my .NetFramework to 4.8 I also imported the old certificate from the previous instance. Neither did the old clients connect nor did new clients connect to the new server build. I then ran new build server on a Windows 10 machine, where new created clients were able to connect without any problem. So I raised this issue.

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@MaxXor commented on GitHub (Jun 17, 2020):

That's weird, do you still have the old quasar installation available on the windows server? If you updated directly from the previous version (1.3.0.0) to the latest commit it is required to follow this update procedure: https://github.com/quasar/Quasar/wiki/Updating-a-Client

I'll try to setup a Windows server 2012 instance in the next few days to reproduce this issue.

@MaxXor commented on GitHub (Jun 17, 2020): That's weird, do you still have the old quasar installation available on the windows server? If you updated directly from the previous version (1.3.0.0) to the latest commit it is required to follow this update procedure: https://github.com/quasar/Quasar/wiki/Updating-a-Client I'll try to setup a Windows server 2012 instance in the next few days to reproduce this issue.

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@MaxXor commented on GitHub (Jun 21, 2020):

Okay, I've tested everything on a fully patched Windows Server 2012 R2 and it's working fine. However the firewall rule to allow remote connections needs to be manually added.

@MaxXor commented on GitHub (Jun 21, 2020): Okay, I've tested everything on a fully patched Windows Server 2012 R2 and it's working fine. However the firewall rule to allow remote connections needs to be manually added.

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@MaxXor commented on GitHub (Jun 21, 2020):

I've added the manual creation of windows firewall rules to the wiki: https://github.com/quasar/Quasar/wiki/Getting-Started#4-adding-a-firewall-rule

@MaxXor commented on GitHub (Jun 21, 2020): I've added the manual creation of windows firewall rules to the wiki: https://github.com/quasar/Quasar/wiki/Getting-Started#4-adding-a-firewall-rule