SolidCP Forum - Recent Posts

Standalone SSL Installation for Enterprise Server and Server Components

mojoekita — Wed, 17 Jun 2026 05:34:05 +0000

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:

System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) +226

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

RE: SolidCP to FuseCP

Beamer — Tue, 16 Jun 2026 09:43:38 +0000

@m-tiggelaar Yes, i can understand, this gonna be major leap from wsp > scp and so on and what we required as on today with new standards, its just all other softwares are getting updated day by day its gonna get difficult to keep SCP alive and working error free.

Looking forward for FCP.

All the best

Thanks

RE: SolidCP to FuseCP

Marco Tiggelaar — Mon, 15 Jun 2026 20:58:49 +0000

@hemens We are making good progress.
A little delayed as we had to switch AI agents (had to build our own AI Server as the pricing changes where pushing it through the roof which ofcourse took time with all equipment being delivered etc...).

Quite a few modules are tested and ready to go to beta, but not everything just yet (refactoring Web / Certificates for example currently).

If i had to guess + - 3 more weeks.

Public site should also be up soon.
Just keep in mind what we are working on is a very strong "new" base, we cutted out outdated and EOL software, refactored existing to modern standards (code and function) and so on.
So it's not just a .net10 conversion.

RE: SolidCP to FuseCP

Beamer — Mon, 15 Jun 2026 09:14:06 +0000

@m-tiggelaar Hi Marco

Are we getting closer to FCP beta testing.

RE: Assistance with WHMCS Plugin PHP8.1

MrBios — Thu, 21 May 2026 21:32:30 +0000

@trobinson using the version downloaded from here

https://installer.solidcp.com/Files/plugins/SolidCP.WHMCSModule.zip

i thinks its v. 1.1.3 - 15 June 2021 based on the change log

RE: Assistance with WHMCS Plugin PHP8.1

Trevor Robinson — Thu, 21 May 2026 13:27:12 +0000

Hey,

Which version of the plugin are you using? You can download the latest from https://github.com/FuseCP/FuseCP/tree/SolidCPv1/SolidCP.WHMCSModule/

Regards,

Trevor

RE: SolidCP to FuseCP

Marco Tiggelaar — Thu, 21 May 2026 06:38:49 +0000

@mrbios We are working hard on getting the new version ready.
It's almost beta testing time (I would expect within the next month assuming nothing un-expected pops up).

That being said the old panel is relatively easy to secure:
- make sure you lock down admin level access to only specific ip's/ ranges
- enable MFA (for everyone).
- make sure enterprise and server modules aren't publically accessible.

Regards,

Marco

RE: SolidCP to FuseCP

MrBios — Thu, 21 May 2026 03:21:15 +0000

Do you have a timeline as to when FuseCP will be out.

With all the security issues due to AI recently, worried this old software is a sitting duck.

might have to ditch windows hosting or move to Plesk since we been waiting for some time for the updated panel to come out.

RE: Assistance with WHMCS Plugin PHP8.1

MrBios — Thu, 21 May 2026 03:12:57 +0000

did you get a fix for this ?

i have same error on PHP 8.x

RE: Incorrect link for manual update 1.4.8 to 1.4.9

Marco Tiggelaar — Thu, 23 Apr 2026 20:32:49 +0000

Thanks for the heads up.

I updated it to just pick the latest solidcp stable manual update.