Mastodon: Global and Local timeline won't refresh automaticaly.

[Letiteuf55]

Hi, i run my instance but as i see on other instance, my Global and Local Timeline doesn't show new toot unless i refresh manually my browser. Is there a file to configure to allow this?

---

• [x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.-
• [x] This bug happens on a tagged release and not on master (If you're a user, don't worry about this).

[mjankowski]

What is your server setup like? Is the streaming node server running?

[Letiteuf55]

My setup is a Virtual server : 2 vCores@2,4 GHz - 8 Go RAM - SSD 40 Go Running Debian8.
I follow this guide https://angristan.fr/installer-instance-mastodon-debian-8/
I check the streaming service and i'ts alive : active (running)

[DanielGilbert]

If you are using Chrome, press F12 to open up the dev tools. Now, look for any errors relating to "wss://" or "ws://" protocol. If they appear, Chrome isn't able to build a websocket connection, which is needed to refresh the timelines.

[Letiteuf55]

Oh yes... i have "Refused to connect to 'wss://mastodon.crazypanda.fr//api/v1/streaming/?access_token=* [...} because it violates the following Content Security Policy directive: "connect-src 'self' wss://mstdn.io" " How can we fix this ?

[DanielGilbert]

Well - don't copy the CSP Headers of other instances.^^ Replace wss://mstdn.io with your host and protocol, so use wss://mastodon.crazypanda.fr

In theory, it should work than. :)

[Letiteuf55]

Hum, ok, i find that i forgot to remove mstdn.io and replace by my own but i still have the wss:// issue...

[Letiteuf55]

I restart nginx and seems to be ok with the wss:// issue :+1:

[DanielGilbert]

Awesome, great! :)

Don't forget to close the issue when your problem is solved. :)

[Letiteuf55]

YEEEES it's working great ! I still have some Red issues on the F12 dev tools but i think it's an other thing.
Thanks a lot !