Securing Plesk innstance on port 8443
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker
- Domain
- infrastructure, security
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.
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.
- Dominant language
- Dockerfile
- Stars
- 98
- Forks
- 49
- Avg merge
- 57m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from plesk/docker
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
After deploying plesk in Kubernetes Engine (GKE) It redirecting me to login page again and againOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
Similar issues
-
priority: P3 type: devops
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jiegui2025/hwspec#57 ·
Maintainers usually reply within 1 day
-
area: release bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TMHSDigital/subenum#102 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
ai-inspected
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
dockur/windows-arm#611 · 3 comments · 1 reaction ·