Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to Starting Proxy... #208

Open
ebtone opened this issue Oct 10, 2024 · 6 comments
Open

Failed to Starting Proxy... #208

ebtone opened this issue Oct 10, 2024 · 6 comments

Comments

@ebtone
Copy link

ebtone commented Oct 10, 2024

Couldn't Communicate With Proxy Console.
Please Make Sure You Have .NET Desktop v6 And ASP.NET Core v6 Installed On Your OS.

image

sdc_user_data_2024.10.10-09.14.41.zip

@msasanmh
Copy link
Owner

I've imported your data and it worked correctly.
Check your Anti-virus and any System security software you have and white list all the executable files in (Installation Directory -> SecureDNSClient -> binary) directory.
You can also disable your Anti-virus temporary to check if the app works.

@ebtone
Copy link
Author

ebtone commented Oct 11, 2024

I've imported your data and it worked correctly. Check your Anti-virus and any System security software you have and white list all the executable files in (Installation Directory -> SecureDNSClient -> binary) directory. You can also disable your Anti-virus temporary to check if the app works.

I'm no installation Anti-virus, and check Microsoft Defender Protection History not found SDC has been blocked.

If the SDC is used immediately after the system is started, it can work fine.
If the SDC is used some time after the system is started, only proxy module not working.

@msasanmh
Copy link
Owner

I'm no installation Anti-virus, and check Microsoft Defender Protection History not found SDC has been blocked.

If the SDC is used immediately after the system is started, it can work fine.
If the SDC is used some time after the system is started, only proxy module not working.

Somehow, the GUI can't write the commands to the proxy process input.
Can I know about your system specifications?
The CPU model, RAM capacity, etc.

And, are you using 64-bit Windows 10 home edition? If yes, then please try the 32-bit version of SDC and let me know.

@msasanmh
Copy link
Owner

Try new version 3.2.5

@ebtone
Copy link
Author

ebtone commented Oct 15, 2024

I'm no installation Anti-virus, and check Microsoft Defender Protection History not found SDC has been blocked.
If the SDC is used immediately after the system is started, it can work fine.
If the SDC is used some time after the system is started, only proxy module not working.

Somehow, the GUI can't write the commands to the proxy process input. Can I know about your system specifications? The CPU model, RAM capacity, etc.

And, are you using 64-bit Windows 10 home edition? If yes, then please try the 32-bit version of SDC and let me know.

Thanks for your reply~

My os is 64-bit Windows 10 home edition~

This is my computer information~

PS C:> Get-WmiObject -Class Win32_OperatingSystem

SystemDirectory : C:\Windows\system32
Organization :
BuildNumber : 19045
RegisteredUser : Admin
SerialNumber : 00326-70000-00001-AA667
Version : 10.0.19045

PS C:> Get-WmiObject -Class Win32_ComputerSystem

Domain : WORKGROUP
Manufacturer : Micro-Star International Co., Ltd.
Model : MS-7D22
Name : LAN_PC
PrimaryOwnerName : Admin
TotalPhysicalMemory : 17072504832

PS C:> Get-WmiObject -Class Win32_Processor

Caption : Intel64 Family 6 Model 165 Stepping 3
DeviceID : CPU0
Manufacturer : GenuineIntel
MaxClockSpeed : 2904
Name : Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
SocketDesignation : U3E1

PS C:> Get-WmiObject -Class Win32_BaseBoard

Manufacturer : Micro-Star International Co., Ltd.
Model :
Name : 基板
SerialNumber : 07D2211_L51D105993
SKU :
Product : B560M PLUS (MS-7D22)

PS C:> Get-WmiObject -Class Win32_PhysicalMemory

__GENUS : 2
__CLASS : Win32_PhysicalMemory
__SUPERCLASS : CIM_PhysicalMemory
__DYNASTY : CIM_ManagedSystemElement
__RELPATH : Win32_PhysicalMemory.Tag="Physical Memory 0"
__PROPERTY_COUNT : 36
__DERIVATION : {CIM_PhysicalMemory, CIM_Chip, CIM_PhysicalComponent, CIM_PhysicalElement...}
__SERVER : LAN_PC
__NAMESPACE : root\cimv2
__PATH : \LAN_PC\root\cimv2:Win32_PhysicalMemory.Tag="Physical Memory 0"
Attributes : 2
BankLabel : BANK 0
Capacity : 17179869184
Caption : 物理内存
ConfiguredClockSpeed : 2667
ConfiguredVoltage : 1200
CreationClassName : Win32_PhysicalMemory
DataWidth : 64
Description : 物理内存
DeviceLocator : Controller0-ChannelA
FormFactor : 8
HotSwappable :
InstallDate :
InterleaveDataDepth : 0
InterleavePosition : 0
Manufacturer : Colorful Technology Ltd
MaxVoltage : 1200
MemoryType : 0
MinVoltage : 1200
Model :
Name : 物理内存
OtherIdentifyingInfo :
PartNumber : CDPC16G2666D4N8
PositionInRow :
PoweredOn :
Removable :
Replaceable :
SerialNumber : 4E45D781
SKU :
SMBIOSMemoryType : 26
Speed : 2667
Status :
Tag : Physical Memory 0
TotalWidth : 64
TypeDetail : 128
Version :
PSComputerName : LAN_PC

PS C:> Get-WmiObject -Class Win32_DiskDrive

Partitions : 2
DeviceID : \.\PHYSICALDRIVE0
Model : WDC WD10EZEX-08WN4A0
Size : 1000202273280
Caption : WDC WD10EZEX-08WN4A0

Partitions : 6
DeviceID : \.\PHYSICALDRIVE1
Model : WDS500G3X0C-00SJG0
Size : 500105249280
Caption : WDS500G3X0C-00SJG0

@ebtone
Copy link
Author

ebtone commented Oct 15, 2024

Try new version 3.2.5

Okay, I will try this version later and provide feedback on the results

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants