Sub-domains with port exposed doesn't work with ssl


I have created a single certificate for main domain and sub-domain. The sub-domain runs on port 4200.
But ssl doesn’t work for the sub-domain with the port exposed.


Hi @sandeep

if you have the certificate created and if the certificate has the required two names, then the port shouldn’t be the problem.

But without your domain name and your exact command (only certificate, certificate + installation) it’s impossible to find a solution.



It gives me below error for sub-domains.
“it is possible that this site uses an unsupported protocol or cipher suite such as RC4”


Please share your domain name.

Certificates are logged, so they are public.


My domain name is
And the issue i’m facing is for the sub-domain When i access it doesn’t give me any error, but when i try to access with the port , it throws me error.


Your sends a SSL_ERROR_RX_RECORD_TOO_LONG error.

That means, that this port sends too much data. This is often the result, that there is http content sent.


Yep, there is a page and a redirect to with a login.

So you must configure your 4205 as https - port, not http - port.


Now, i have removed the redirect and it works fine.
Another thing i’m looking it is to make both http and https work in the sub-domain. What is the setting i need to setup in my virtual host file.


What does this mean?



I want the sub-domain to work with http and https too. Currently, it works either with https or http.


If you have one port 4205, you can use this port with http or with https - not with both.

Now this port works with http -

If you want an additional https, then use the next port 4206.

But I would remove the http - login, because login data should always secured.

And the browser shows a bad warning, if there is a login via http.



This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.