Standalone SSL Inst...
 
Notifications
Clear all

Standalone SSL Installation for Enterprise Server and Server Components

1 Posts
1 Users
0 Reactions
6 Views
Posts: 30
Topic starter
(@mojoekita)
Trusted Member
Joined: 10 years ago

Hi there,

I trust you are well. 

Is it possible to perform a standalone installation using SSL for all SolidCP components?
I understand that the Web Portal can be configured to use SSL, but I would also like the backend components to communicate over SSL, specifically:

Enterprise Server: https://hostname:9003
Server Component: https://hostname:9002

However, when I configure these services to use SSL, I receive the error shown below.

Has anyone successfully implemented this configuration, or can you provide any guidance on the correct setup requirements?

Any advice would be greatly appreciated.
Thank you.

##############
An existing connection was forcibly closed by the remote host
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SocketException (0x2746): An existing connection was forcibly closed by the remote host]
System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) +226

[IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.]
System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) +811
System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) +48
System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) +228
System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) +361
System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation) +245
System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) +812
System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) +264
System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) +21
System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) +85
System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) +1131
System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) +62
System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) +124
System.Net.ConnectStream.WriteHeaders(Boolean async) +491


Share: