{"action":"closed","issue":{"url":"https://api.github.com/repos/ether/etherpad-lite/issues/2503","labels_url":"https://api.github.com/repos/ether/etherpad-lite/issues/2503/labels{/name}","comments_url":"https://api.github.com/repos/ether/etherpad-lite/issues/2503/comments","events_url":"https://api.github.com/repos/ether/etherpad-lite/issues/2503/events","html_url":"https://github.com/ether/etherpad-lite/issues/2503","id":56798185,"number":2503,"title":"Users see different versions of the same pad","user":{"login":"necramirez","id":167253,"avatar_url":"https://avatars.githubusercontent.com/u/167253?v=3","gravatar_id":"","url":"https://api.github.com/users/necramirez","html_url":"https://github.com/necramirez","followers_url":"https://api.github.com/users/necramirez/followers","following_url":"https://api.github.com/users/necramirez/following{/other_user}","gists_url":"https://api.github.com/users/necramirez/gists{/gist_id}","starred_url":"https://api.github.com/users/necramirez/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/necramirez/subscriptions","organizations_url":"https://api.github.com/users/necramirez/orgs","repos_url":"https://api.github.com/users/necramirez/repos","events_url":"https://api.github.com/users/necramirez/events{/privacy}","received_events_url":"https://api.github.com/users/necramirez/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-02-06T10:58:13Z","updated_at":"2015-02-08T14:51:14Z","closed_at":"2015-02-08T14:51:14Z","body":"* Node v0.10.35\r\n* Etherpad Lite v1.5.1\r\n* CentOS 6.6\r\n* Nginx 1.6.2\r\n* Passenger 4.0.58\r\n\r\nI used to serve Etherpad Lite straight out of a plain node process on default port 9001.  Now, I tried to serve it using Nginx + Passenger, so I only need to monitor the Nginx process.  Etherpad Lite is now accessed on port 443 (SSL via Nginx; SSL is not enabled in `settings.json`).  My Nginx + Passenger config looks like this:\r\n```\r\nserver {\r\n    listen       443 ssl;\r\n    server_name  my.server.com;\r\n\r\n    ssl_certificate      /etc/pki/tls/certs/my-cert.pem;\r\n    ssl_certificate_key  /etc/pki/tls/private/my-private.key;\r\n\r\n    ssl_session_cache    shared:SSL:1m;\r\n    ssl_session_timeout  5m;\r\n\r\n    ssl_ciphers  HIGH:!aNULL:!MD5;\r\n    ssl_prefer_server_ciphers  on;\r\n\r\n    passenger_app_root /home/etherpad-lite/etherpad-lite;\r\n    passenger_enabled on;\r\n\r\n    passenger_app_type node;\r\n    passenger_startup_file node_modules/ep_etherpad-lite/node/server.js;\r\n    root /home/etherpad-lite/etherpad-lite/src/static;\r\n\r\n    passenger_restart_dir /home/etherpad-lite/etherpad-lite;\r\n    passenger_min_instances 2;\r\n}\r\n```\r\n\r\nHowever, since I did that, my teammates are reporting that they aren't seeing each others edits to the same pad.  Is it perhaps because of Passenger running multiple instances?"}}