Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flowing API policy misconfiguration? #37

Open
moonmilk opened this issue Apr 20, 2017 · 7 comments

Comments

@moonmilk
Copy link

@moonmilk moonmilk commented Apr 20, 2017

Refused to connect to 'wss://oulipo.social//api/v1/streaming/?access_token=[]&stream=public:local' because it violates the following Content Security Policy directive: "connect-src wss://example.com 'self'".

Possibly example.com ought to say oulipo.social at that spot?


  • I searched or browsed the repo’s other issues to ensure this is not a duplicate.
@moonmilk

This comment has been minimized.

Copy link
Author

@moonmilk moonmilk commented Apr 20, 2017

@starlit-void

This comment has been minimized.

@etjossem

This comment has been minimized.

Copy link

@etjossem etjossem commented Apr 21, 2017

I saw this too.

image

Cmd-R is thusly a must to pull new toots.

@etjossem etjossem referenced this issue Apr 21, 2017
0 of 1 task complete
@ecmendenhall

This comment has been minimized.

Copy link

@ecmendenhall ecmendenhall commented Apr 25, 2017

I'm looking at Rails for this, but I think this is down to a bash var in prod such as this, or an Nginx config such as this, which should say "oulipo.social".

@mouse-reeve

This comment has been minimized.

Copy link
Owner

@mouse-reeve mouse-reeve commented Apr 29, 2017

fixing my apache2 config did fix that JS log but now it's 500ing. chuggin' along

@starlit-void

This comment has been minimized.

Copy link

@starlit-void starlit-void commented Apr 29, 2017

now browsing output has: application-eb0878a….js:1894 WebSocket connection to 'wss://oulipo.social//api/v1/streaming/?access_token=<TOKEN>&stream=user' failed: Error during WebSocket handshake: Unexpected response code: 500 non-stop

@mouse-reeve

This comment has been minimized.

Copy link
Owner

@mouse-reeve mouse-reeve commented Apr 29, 2017

yup, hoping to work out why and fix that soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.