# caprover

Published articles for caprover.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Using CapRover on AWS

DevFeed: [Using CapRover on AWS](<https://devfeed.tech/articles/using-caprover-on-aws-28133.md>)

Original publisher: [Read original article](<http://fuzzyblog.io/blog/caprover/2019/11/10/using-caprover-on-aws.html>)

Author: Fuzzygroup

Published: 2019-11-10T00:00:00Z

Content type: tutorial

Language: en

Sources: [Scott Johnson](<https://devfeed.tech/sources/scott-johnson.md>)

Topics: [Deployment](<https://devfeed.tech/topics/deployment.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Heroku](<https://devfeed.tech/topics/heroku.md>), [Ruby on Rails](<https://devfeed.tech/topics/ruby-on-rails.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [caprover](<https://devfeed.tech/tags/caprover.md>), [commands](<https://devfeed.tech/tags/commands.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [docker](<https://devfeed.tech/tags/docker.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [rails](<https://devfeed.tech/tags/rails.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [snap](<https://devfeed.tech/tags/snap.md>)

### AI overview

A hands-on guide to running CapRover on AWS EC2. It covers resolving port conflicts caused by nginx, installing Docker without the problematic Snap package, and configuring AWS security groups for port 3000 and IPv4/IPv6 access.

### Source excerpt

I am a Ruby on Rails guy and I censored hate deploying Ruby stuff. I've been deploying Rails stuff now since 2007 and, quite honestly, it sucked in 2007 and it sucks today. The only way I've ever found Rails deployment to not suck is by using Heroku which is absolutely magical and wonderful - but expensive. Now I've recently become hooked on Heroku and the ease of its Git push based deployment structure. The problem is that I need more power / flexibility with respect to what I'm deploying and this has let me to the CapRover open source project. This project aims to give you a version of Heroku but running on your own hardware. Given that I'm an AWS guy, I wanted to use CapRover on AWS EC2 instances. Setup - 1 I started by installing the CapRover software and here was the first problem that I hit: sudo docker run -p 80:80 -p 443:443 -p 3000:3000 -v /var/run/docker.sock:/var/run/docker.sock -v /captain:/captain caprover/caprover docker: Error response from daemon: driver failed programming external connectivity on endpoint quizzical_snyder (f72be52bf809d139cc012debeadb87b813e02e8fd2ada6fbba97d4503d624c43): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use. ERRO[0000] error waiting for container: context canceled The issue here is that one of these 3 ports is already in use. And the easiest way to figure this out is to run a succession of netstat commands: sudo netstat -pna | grep 3000 That returned nothing. So onto the next one, 443: sudo netstat -pna | grep 443 Again this returned nothing, onto 80: sudo netstat -pna | grep 80 tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 21331/nginx: master tcp6 0 0 :::80 :::* LISTEN 21331/nginx: master unix 2 [ ACC ] STREAM LISTENING 16380 1/init @ISCSIADM_ABSTRACT_NAMESPACE unix 3 [ ] STREAM CONNECTED 22180 949/dockerd unix 3 [ ] STREAM CONNECTED 38086 4225/python3 unix 2 [ ] DGRAM 18052 1010/systemd-logind unix 3 [ ] STREAM CONNECTED 18081 954/dbus-daemon /var/run/dbus/system_bus_socket unix 3 [ ] STREAM CO