Why port 80 443 is closes?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker
- Domain
- devops
Research direction
Start with the documented docker run command and its -p 80:80 and -p 443:443 mappings, then compare those ports with the working 2082, 2083, and 8447 mappings. Done means identifying why ports 80 and 443 are unreachable and confirming they accept connections under the same container setup.
Written by the indexing model from the issue text.
Description
I run Plesk latest version with this command
sudo docker run -d -p 80:80 -p 443:443 -p 2082:8880 -p 2083:8443 -p 8447:8447 plesk/plesk
responded
port 2082 2083 8447 is open but 80 and 443 is close
- 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 4/5 3-5 days Newbie friendliness 20/100