Hmm, Mastonaut is not the biggest fan of being fullscreen

and Mast is abandoned

and Hyperspace Desktop doesn’t work, presumably because of Cloud Island’s CORS headers that need to be fixed

Which means that I should probably fix the CORS headers

except not always, the API routes aren’t setting the cors header

… why not

@aurynn are you running a separate instance for the "streaming" part of Mastodon?

@emilyst it’s a separate route in nginx, but it’s on the same server

@aurynn I think that nginx bit is possibly the part goofing up here.

Your server seems to report that the websocket is available at wss://, but if I try to make a websocket request, it 302s me over to your about page (unexpected behavior).

when i run the same experiment on my server, it gives me a JSON error because I'm not auth'd (expected behavior).

@aurynn here is how i tested against mine:

curl --include --no-buffer --header "Connection: Upgrade" --header "Upgrade: websocket" --header "Host:" --header "Origin: social-streaming.emilylilyli.m" --header "Sec-WebSocket-Key: SGVsbG8sIHdvcmxkIQ==" --header "Sec-WebSocket-Version: 13" -vvv social-streaming.emilylilyli.m

@emilyst hmm, interesting, I clearly don’t have websockets set up properly

@aurynn that's probably the issue, yeah. i keep the API server (which is its own separate node thing that happens to be bundled with mastodon) on a separate container with a separate server name, just to make things work right.

@emilyst the API server is on its own port with a custom nginx upstream, and I was using the example nginx config, so I expected it to work

time to figure out wss 😄

@aurynn what port is it on? that seems not to be making it to the metadata communicated on the web interface.

@emilyst it shouldn’t be being communicated forward, since its serving a specific route - /api/v1/streaming - off of an upstream on a different port

@aurynn hmm, well, i am not 100% sure i am correct then.

i noticed i get a 400 when i try to hit ` using curl, but that might be correct. (mine, again, just spits out an auth error.)

carry on. hard to debug from here when i don't know how things are meant to be set up.

@emilyst what’s the full curl command you’re using there? I’m getting a 500 if I do a bare GET, which is what I expect

@aurynn curl --include --no-buffer --header "Connection: Upgrade" --header "Upgrade: websocket" --header "Host:" --header "Origin:" --header "Sec-WebSocket-Key: SGVsbG8sIHdvcmxkIQ==" --header "Sec-WebSocket-Version: 13" -vvv

@emilyst so the 302 should be the https promotion kicking in

@aurynn hmmm, i don't know about that, but again, your setup seems to do things that i don't understand, so i'm content to let you do your thing and not butt in anymore.

@aurynn is this a server you can actually log into and issue requests locally? you could rule out some kinda nginx configuration issue by issuing a `curl` directly to the node instance on the server and see what the response looks like. then compare from outside.

if they're the same, nginx isn't the problem. if not, nginx is a problem.

@emilyst my browser is reporting wss as working fine, if I’m logged in to my server

@aurynn okay. welp. idk.

(i'm restarting my NAS, so my Mastodon instance will be down for a few minutes.)

Sign in to participate in the conversation
Cloud Island

A paid, early access, strongly moderated Mastodon instance hosted entirely in New Zealand.