[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Campo Popo updated OPENMEETINGS-1822:
-------------------------------------
    Affects Version/s: 4.0.1

> Running Apache OpenMeetings with Nginx Reverse Proxy?
> -----------------------------------------------------
>
>                 Key: OPENMEETINGS-1822
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1822
>             Project: Openmeetings
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Campo Popo
>            Assignee: Maxim Solodovnik
>            Priority: Minor
>         Attachments: Image 12.png
>
>
> I am trying to install Apache OpenMeetings. I however wants to use Nginx as 
> the reverse proxy to run the application on port 443 using Let's Encrypt free 
> SSL.
> If I try to load the application on port 5080, I successfully get the 
> interface, but when try using the domain name on port 443 HTTPS, It is not 
> loading the resources.
> Here's my nginx virtual host file.
> upstream openmeetings {
>  server 127.0.0.1:5080;
>  }
>  
>  server {
>  listen 80;
>  server_name openmeetings.example.com;
>  return 301 https://$host$request_uri;
>  }
>  
>  server {
>  listen 443;
>  server_name openmeetings.example.com;
>  
>  ssl_certificate /etc/letsencrypt/live/openmeetings.example.com/fullchain.pem;
>  ssl_certificate_key 
> /etc/letsencrypt/live/openmeetings.example.com/privkey.pem;
>  
>  ssl on;
>  ssl_session_cache builtin:1000 shared:SSL:10m;
>  ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
>  ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
>  ssl_prefer_server_ciphers on;
>  
>  access_log /var/log/nginx/openmeetings.access.log;
>  
>  location / {
>  proxy_pass http://openmeetings;
>  proxy_set_header X-Real-IP $remote_addr;
>  proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
>  proxy_set_header Host $http_host;
>  proxy_set_header X-NginX-Proxy true;
>  proxy_redirect off;
>  }
>  }



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to