# Message was grey and need refresh page to appear **URL:** \ **Category:** Community Support\ **Created:** [August 26, 2022, 12:42pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782 "2022-08-26T12:42:20Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [August 26, 2022, 12:42pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/1 "2022-08-26T12:42:20Z")
### Description Hello, I’ve an issue with message in my fresh rocket.chat instance. I can hear the sound of message but don’t see them. To see the message I need to refresh page. ### Server Setup Information - Version of Rocket.Chat Server: 5.0.4 - Operating System: Debian 11 - Deployment Method: Tar - Number of Running Instances: 1 - DB Replicaset Oplog: - NodeJS Version: 14.20.0 - MongoDB Version: 5.0.11 / wiredTiger (oplog Activé) - Proxy: nginx - Firewalls involved: No FW ### Any additional Information I have a first Nginx reverseproxy with this conf : > **Summary** > > ```auto > upstream backend { > server IP_Of_RocketChat_Server:3000; > keepalive 32; > } > > server { > if ($host = chat.fqdn.fr) { > return 301 https://$host$request_uri; > } # managed by Certbot > > #listen 80 default_server; > server_name chat.fqdn.fr; > return 301 https://$server_name$request_uri; > } > > server { > listen 443 ssl http2; > server_name chat.fqdn.fr; > > http2_push_preload on; # Enable HTTP/2 Server Push > > # Enable TLS versions (TLSv1.3 is required upcoming HTTP/3 QUIC). > ssl_protocols TLSv1.2 TLSv1.3; > > # Enable TLSv1.3's 0-RTT. Use $ssl_early_data when reverse proxying to > # prevent replay attacks. > # > # @see: https://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_early_data > ssl_early_data on; > > ssl_ciphers 'ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384'; > ssl_prefer_server_ciphers on; > ssl_session_cache shared:SSL:50m; > # HSTS (ngx_http_headers_module is required) (15768000 seconds = six months) > add_header Strict-Transport-Security max-age=15768000; > # OCSP Stapling --- > # fetch OCSP records from URL in ssl_certificate and cache them > ssl_stapling on; > ssl_stapling_verify on; > > add_header X-Early-Data $tls1_3_early_data; > > location / { > proxy_set_header Upgrade $http_upgrade; > proxy_set_header Connection "upgrade"; > client_max_body_size 50M; > proxy_set_header Host $http_host; > proxy_set_header X-Real-IP $remote_addr; > proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; > proxy_set_header X-Forwarded-Proto $scheme; > proxy_set_header X-Frame-Options SAMEORIGIN; > proxy_buffers 256 16k; > proxy_buffer_size 16k; > client_body_timeout 60; > send_timeout 300; > lingering_timeout 5; > proxy_connect_timeout 90; > proxy_send_timeout 300; > proxy_read_timeout 90s; > proxy_http_version 1.1; > proxy_pass http://backend; > > } > > ssl_certificate /etc/letsencrypt/live/chat.fqdn.fr/fullchain.pem; # managed by Certbot > ssl_certificate_key /etc/letsencrypt/live/chat.fqdn.fr/privkey.pem; # managed by Certbot > } > > # This block is useful for debugging TLS v1.3. Please feel free to remove this > # and use the `$ssl_early_data` variable exposed by NGINX directly should you > # wish to do so. > map $ssl_early_data $tls1_3_early_data { > "~." $ssl_early_data; > default ""; > } > > ``` And this is the nginx conf on my rocketchat server : > **Summary** > > ```auto > upstream rocket_backend { > server 127.0.0.1:3000; > } > > server { > listen 80; > server_name chat.fqdn.fr; > access_log /var/log/nginx/rocketchat-access.log; > error_log /var/log/nginx/rocketchat-error.log; > > location / { > proxy_pass http://rocket_backend/; > proxy_http_version 1.1; > proxy_set_header Upgrade $http_upgrade; > proxy_set_header Connection "upgrade"; > proxy_set_header Host $http_host; > > proxy_set_header X-Real-IP $remote_addr; > proxy_set_header X-Forward-For $proxy_add_x_forwarded_for; > proxy_set_header X-Forward-Proto http; > proxy_set_header X-Nginx-Proxy true; > > proxy_redirect off; > } > } > > ``` Thank for reply 🙂 ---
**Author:** ![dudanogueira](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/dudanogueira/32/2529_2.png) [@dudanogueira](https://forums.rocket.chat/u/dudanogueira)\ **Post date:** [August 26, 2022, 12:53pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/2 "2022-08-26T12:53:45Z")
Hi! Welcome to our community 🙂 We have a comprehensive reverse proxy section in our docs here: > **[Configuring SSL Reverse Proxy](https://docs.rocket.chat/quick-start/environment-configuration/configuring-ssl-reverse-proxy)** Please, make your settings match those. Also, can you reproduce this error on a clean, fresh, docker install, accessing it locally? Let me know if this helps. ---
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [August 26, 2022, 12:55pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/3 "2022-08-26T12:55:50Z")
Which nginx need this conf ? The first ? Or the Nginx in the rocketchat ? This is a fresh install from TAR. I don’t wanna use Docker, sorry ---
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [August 26, 2022, 3:39pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/4 "2022-08-26T15:39:08Z")
I have changed my NGINX first reverseproxy with the conf like you said, but nothing change 😕 ---
**Author:** ![dudanogueira](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/dudanogueira/32/2529_2.png) [@dudanogueira](https://forums.rocket.chat/u/dudanogueira)\ **Post date:** [August 26, 2022, 5:55pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/5 "2022-08-26T17:55:04Z")
You should only have one NGINX… rocketchat will listen at port 3000 and your nginx will proxy request there. have you tried hard reloading it? Is there any outstanding logs in the browser console? ---
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [August 26, 2022, 6:07pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/6 "2022-08-26T18:07:30Z")
It’s not very simple for my case… In fact I have many web server behind same public IP and I need a fisrt reverseproxy behind other web server and rocketchat 😕 ---
**Author:** ![dudanogueira](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/dudanogueira/32/2529_2.png) [@dudanogueira](https://forums.rocket.chat/u/dudanogueira)\ **Post date:** [August 26, 2022, 6:35pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/7 "2022-08-26T18:35:32Z")
Oh… I hear you, hehehe. In theory… this should not be a problem. But… you know. The browser console errors may give us a hint. do you see any? or at the network tab, any faulty connection? ---
**Author:** ![dudanogueira](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/dudanogueira/32/2529_2.png) [@dudanogueira](https://forums.rocket.chat/u/dudanogueira)\ **Post date:** [August 26, 2022, 6:36pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/8 "2022-08-26T18:36:20Z")
Also, do you see this kind of error when acessing Rocket.Chat directly? Like, bypassing all those nginx on the way? ---
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [August 26, 2022, 6:47pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/9 "2022-08-26T18:47:11Z")
When I access to rocket with internal IP of server nothing change ---
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [August 26, 2022, 6:47pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/10 "2022-08-26T18:47:45Z")
Firefox can’t establish a connection to the server at wss://chat.fqdn.fr/sockjs/006/k04xwbwk/websocket. [de2a0a98a668e5a193ce98f6f7dfcb36e7148079.js:1311:22863](https://chat.fqdn.fr/de2a0a98a668e5a193ce98f6f7dfcb36e7148079.js?meteor_js_resource=true) The connection to wss://chat.fqdn.fr/sockjs/006/k04xwbwk/websocket was interrupted while the page was loading. ---
**Author:** ![dudanogueira](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/dudanogueira/32/2529_2.png) [@dudanogueira](https://forums.rocket.chat/u/dudanogueira)\ **Post date:** [August 26, 2022, 7:09pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/11 "2022-08-26T19:09:01Z")
Well… as you have two nginx on the way, they are probably not being able to pass the http2/websocket all the way down/between each other > [@AssoManager](#): > > When I access to rocket with internal IP of server nothing change Wait… so accessing RCHAT directly to where it’s installed, you still can’t use it? ---
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [August 26, 2022, 7:12pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/12 "2022-08-26T19:12:32Z")
> [@dudanogueira](#): > > Wait… so accessing RCHAT directly to where it’s installed, you still can’t use it? Yes 😅 I think it was normal ---
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [August 26, 2022, 7:13pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/13 "2022-08-26T19:13:36Z")
You know the way where is the websocket in the rocketchat folder ? To do something like that : ```auto location /wsapp/ { proxy_pass http://wsbackend; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $host; } ``` ---
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [August 30, 2022, 10:58am UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/14 "2022-08-30T10:58:31Z")
Hi @dudanogueira , No idea of folder/subfolder of wsocket ? ---
**Author:** ![dudanogueira](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/dudanogueira/32/2529_2.png) [@dudanogueira](https://forums.rocket.chat/u/dudanogueira)\ **Post date:** [August 31, 2022, 5:14pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/15 "2022-08-31T17:14:19Z")
Oh, wait. Check this out: > [@Support for installation in subdirectory will be discontinued](https://forums.rocket.chat/t/support-for-installation-in-subdirectory-will-be-discontinued/6371): > > We intend to drop official support for Rocket.Chat installation under subdirectories (with Release 4.0). Over the years there have been many times that we’ve added a new piece of functionality or a contribution merged and it’s ended up with subdirectory support broken. Subdirectory support is complicated in general. But for a large and complex code base like ours we don’t feel maintaining support for it is doing either of us favors. An example of subdirectory in use: [https://www.mydomain.co…](https://www.mydomain.com/chat) You should not use rocketchat under a subpath 🤔 This will cause some unexpected behaviors. ---
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [September 1, 2022, 1:44pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/16 "2022-09-01T13:44:34Z")
Unfortunatly, I’m already on right solution. I’m in this configuration : [chat.domain.fr](http://chat.domain.fr) ---
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [September 2, 2022, 9:54am UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/17 "2022-09-02T09:54:22Z")
May be my question was not very clear… Do you know in the rocketchat fodler on server, where is the path of websocket ? ---
**Author:** ![dudanogueira](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/dudanogueira/32/2529_2.png) [@dudanogueira](https://forums.rocket.chat/u/dudanogueira)\ **Post date:** [September 2, 2022, 1:26pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/18 "2022-09-02T13:26:14Z")
You mean where are files with the code? the url will live here, this is where clients will connect to it. wss://open.rocket.chat/websocket If you are taking about the source code, I don’t see this as being relevant to that issue. This most certainly a problem with the two NGINX you have. Also, have you tried disabling TLS 1.3? I have seen also some issues when this was on. ---
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [September 2, 2022, 1:37pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/19 "2022-09-02T13:37:57Z")
I can try to force tu use 1.2. I can’t imagine no one have an infra. like mine 😅 ---
**Author:** ![AssoManager](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AssoManager](https://forums.rocket.chat/u/AssoManager)\ **Post date:** [September 6, 2022, 7:23pm UTC](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782/20 "2022-09-06T19:23:28Z")
No chnages after force TLS 1.2 ☹ [Next page](https://forums.rocket.chat/t/message-was-grey-and-need-refresh-page-to-appear/14782.md?page=2)