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

Securing Plesk innstance on port 8443 #30

Open
rishm069 opened this issue May 16, 2020 · 0 comments
Open

Securing Plesk innstance on port 8443 #30

rishm069 opened this issue May 16, 2020 · 0 comments

Comments

@rishm069
Copy link

The Plesk instance has been deployed from the Docker image and updated to the latest version (18.0.27.0).

An SSL certificate (from Let's Encrypt) was set up to secure Plesk panel as per the following instruction: How to secure a Plesk hostname on port 8443 with an SSL certificate (Let's Encrypt / other certificate authorities) but Plesk returns page subdomain.examample.com:8443 (subdomain.examample.com is the hostname) with a default certificate anyway.

At the same time, the domain examample.com has been successfully secured via Let's Encrypt certificate and served correctly.

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

1 participant