Securing Plesk innstance on port 8443
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 98
- Forks
- 49
- Avg merge
- 57m
- Merged PRs (30d)
- 1
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The payload names the Plesk Docker image, the hostname, and port 8443, but no repository file or test. Start by reproducing the certificate mismatch using the linked Plesk instructions, then compare the certificate served on port 8443 with the configured Let's Encrypt certificate. Done means the Plesk panel serves the intended certificate rather than the default one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100