Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

Support Installation & Updates
  1. OpenProject
  2. Forums
  3. Support Installation & Updates
  4. OpenProject Docker container not accessible after running in AWS EC2

OpenProject Docker container not accessible after running in AWS EC2

Added by Debabrat panda over 4 years ago

Hi There,

Before trying to run the OpenProject:11 image in EC2, I've tried the following

  1. Able to run and access the OpenProject container app in localhost
  2. Able to run and access the OpenProject container app from Linode
  3. Then tried to run the Open project container app from EC2
    1. Added appropriate inbound rule under security group
    2. Install docker and started the docker service
    3. tested a sample container - Able to access the sample app using EC2 public IP

When I started the OpenProject container in EC2, I do not see any error log. But, the app is not accessible using EC2 Public IP.

Below docker run command used to test in all environments i.e. localhost, Linode, and AWS.

docker run -d -p 8080:80 --name openproject -e SECRET_KEY_BASE=xxxxxxxx  -v /var/lib/openproject/pgdata:/var/openproject/pgdata  -v /var/lib/openproject/assets:/var/openproject/assets \ openproject/community:11

Appreciate your input on this.

Thanks

Deb


Replies (4)

RE: OpenProject Docker container not accessible after running in AWS EC2 - Added by Cyril Rohr over 4 years ago

Hello, what inbound rule did you add to your security group?

RE: OpenProject Docker container not accessible after running in AWS EC2 - Added by Debabrat panda over 4 years ago

I have tried by adding below 

  1. HTTP >> TCP >> 80 >> 0.0.0.0/0
  2. Custom TCP >> TCP >> 8080 >> 0.0.0.0/0

RE: OpenProject Docker container not accessible after running in AWS EC2 - Added by Cyril Rohr over 4 years ago

Can you confirm that you can access OpenProject from within the EC2 instance by running curl localhost:8080 ?

If not, have a look at the logs with docker logs openproject

RE: OpenProject Docker container not accessible after running in AWS EC2 - Added by Debabrat panda over 4 years ago

I am able to access the OpenProject app within the EC2 instance using 

$ curl http://localhost:8080

Excerpt of Curl output

HTTP/1.1 200 OK

**Date**: Wed, 14 Oct 2020 05:48:59 GMT

**Server**: nginx/1.18.0 + Phusion Passenger 6.0.6

**Content-Type**: text/html; charset=utf-8

**Status**: 200 OK

**Cache-Control**: max-age=0, private, must-revalidate

**Vary**: Accept-Encoding

**Referrer-Policy**: origin-when-cross-origin

**X-Permitted-Cross-Domain-Policies**: none

**X-XSS-Protection**: 1; mode=block

**X-Request-Id**: 9eafc895-e6fa-463e-b143-8ae4748b7431

Below is the application log while starting.

--> Installing Nginx 1.18.0 engine

--------------------------

[passenger_native_support.so] trying to compile for the current user (app) and Ruby interpreter...

     (set PASSENGER_COMPILE_NATIVE_SUPPORT_BINARY=0 to disable)

     Compilation successful. The logs are here:

     /tmp/passenger_native_support-vcgq67.log

[passenger_native_support.so] successfully loaded.

=============== Phusion Passenger Standalone web server started ===============

PID file: /app/tmp/pids/passenger.8080.pid

Log file: /app/log/passenger.8080.log

Environment: production

Accessible via: http://0.0.0.0:8080/

You can stop Phusion Passenger Standalone by pressing Ctrl-C.

Problems? Check https://www.phusionpassenger.com/library/admin/standalone/troubleshooting/

===============================================================================

/usr/local/bundle/gems/bundler-2.0.2/lib/bundler/rubygems_integration.rb:198: warning: constant Gem::ConfigMap is deprecated

[ N 2020-10-14 05:45:05.7974 374/T7 age/Cor/SecurityUpdateChecker.h:519 ]: Security update check: no update found (next check in 24 hours)

App 409 output: /usr/local/bundle/gems/bundler-2.0.2/lib/bundler/rubygems_integration.rb:198: warning: constant Gem::ConfigMap is deprecated

Forcefully loading the application. Use :environment to avoid eager loading.

  • (1 - 4/4)
Loading...