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

[Question] What is the best way to stop a current caprover container and start it again on a different port? #753

Closed
unlimitedcoder2 opened this issue Jul 8, 2020 · 3 comments
Labels

Comments

@unlimitedcoder2
Copy link

I have tried stopping and removing all containers,
image
image

but they just come back. Since it is not possible to change the mapping of the ports on a running docker container. What is the best way to change caprover to not listen on port 80/443?

@unlimitedcoder2 unlimitedcoder2 changed the title What is the best way to stop a current caprover container and start it again on a different port? [Question] What is the best way to stop a current caprover container and start it again on a different port? Jul 8, 2020
@githubsaturn
Copy link
Collaborator

nginx listens to port 80 and 443 for Let's Encrypt to work. You cannot use CapRover with any other ports.

@unlimitedcoder2
Copy link
Author

I wanted to use an nginx server that was running on the server not in a container but that would require caprover to listen on another port so I can pass all the requests that do not match the ones in the nginx to the one that caprover has so it would be running on 80 anyway.

@githubsaturn
Copy link
Collaborator

CapRover as it stands is not designed to be working like that. You are welcome to fork the project and rebuild the Docker image with new ports - but you might face other problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants