Resolved I need help with customer login https:www.mydomain.com:8443 Not secure

[Spirogg]

my setup is below

OS ‪CentOS Linux 7.6.1810 (Core)‬
Product Plesk Onyx
Version 17.8.11 Update #61, last updated on July 24, 2019 10:42 PM

I need help with lets encrypt and customer control Panel not being secure on https://www.mydomain.com:8443

I added a customer and added the domain and then I set lets encrypt to customers domain.

wait a few and check https://www. domain.com is perfect and secure

so i see in that default webpage this message below:

If you are seeing this message, the website for domain.com is not available at this time.
If you are the owner of this website, one of the following things may be occurring:

• You have not put any content on your website.
• Your provider has suspended this page.

Please login to https://domain.com:8443 to receive instructions on setting up your website.
------------------------------------------------------------------------------------------------------------------------------------------


Why is the login page to the customer control panel not secure?
https://domain.com:8443

this should be secure and using the Lets Encrypt cert, but its not



Your connection is not private
Attackers might be trying to steal your information from domain.com (for example, passwords, messages, or credit cards). Learn more

NET::ERR_CERT_COMMON_NAME_INVALID


please help me fox this

thanks

 

[Spirogg]

my hostname is secure when logging in as admin
https://server.mydomain.com:8443


but on the client side
login https://clientdomain.com:8443 it's not secure - even though the clients main domain is secure https://

is this not a feature of Plesk ?

example
- cPanel has WHM for admins https:// host.name.com:2087 that is secure

- as Plesk has host.name.com:8443 as well for admins and is secure

- cPanel user login screen is secure https:// for users and resellers

- but I don't see this for Plesk Users to login from their domain:8443 (this is not secure)

If I am missing something or some setting please tell me where to look.

If anyone can direct me or give me the solution It would be greatly appreciated

Spiro

 

[IgorG]

Issue - domain:8443 NET::ERR_CERT_COMMON_NAME_INVALID

 

[Spirogg]

I have read this Below:

Issue - domain:8443 NET::ERR_CERT_COMMON_NAME_INVALID

That's normal behaviour: The Plesk control panel server (sw-cp-server) runs on port 8443, which is an independent service that is not connected to your domains' certificates. The control panel server uses the certificate for your server's hostname.
You can't have multiple certificates on port 8443, see: How to secure multiple Plesk login URLs (port 8443) with single SSL certificate on single Plesk server?
So all your customers should login on server.domain.com:8443 and not customer.com:8443

@IgorG I followed the link above see: How to secure multiple Plesk Login Urls (port 8443) with single SSL certificate on single Plesk Server?

but that page is no longer avail.


* Second question : why would Plesk Developers create a Default Template that says this below :


If you are seeing this message, the website for domain.com is not available at this time.
If you are the owner of this website, one of the following things may be occurring:

• You have not put any content on your website.
• Your provider has suspended this page.

THIS ----> Please login to https://domain.com:8443 to receive instructions on setting up your website.


When its not possible for users to login to their Plesk Panel that way, why add that address to the template for confusion ??

Will this ever be a feature for Plesk?

- users will be able to login with their domain.com:8443 or another way ? https://domain.com:8553 or https://domain.com/userpanel

How can cPanel make it capable to allow all users to login through their own domains

example: https://usersdomain.com:2083

all accounts get the free cert and the cpanel login page for is https:// secure

sorry for the long winded questions.

thanks so much in advance for your answer and reply

Regards,

Spiro

 

[IgorG]

Following KB article may be useful for you How to configure a redirect from the domain name/IP address to the server hostname on port 8443?

 

[Spirogg]

OK I think this might work for 1 domain, except what about for other clients domains ?

how can I make this code default for all users accounts I create?

it says to :

change the "example.com" website in the directives below to the correct website resolved to Plesk server. ( what if its multiple website ( domains )

Change the "hostname.com" website to the correct Plesk server hostname. ( THIS IS OK )



QUESTION: if I wanted to use the CODE: below is there a way to make example.com as {users-domain}.com

so {users-domain}.com would grab from plesk each real domain of each client and fill it in.

kinda like DNS it has a default template so when we add a clients domain in plesk it know to grab that domain from the default template .

How can I make this work for me here. or is this not possible for multiple clients domains?

creating some type of code

example: {users-domain}.com would be default template for each users domain.com I create and it would add the real domain in that line?



CODE:

if ($host ~ 'example.com'){
rewrite ^/(.*)$ https://hostname.com:8443/$1 permanent;
}



thanks again @IgorG for your time and assistance

Spiro