Access Workspace Web does not work with returning Code 302

Hi all, I'm trying to setup sagemath with jupyter. I got everything running and

sage -n jupyter

sage -n jupyter

via supervisord in the background and an access via the main.tf file, but jupyter returns a 302 to the location

/tree?

/tree?

and it seems the code-server passes that 302 towards the users freshly opened browser window resulting in the browser to got to

coder.domain.com/tree?

coder.domain.com/tree?

which returns a 404. How can i tell coder to follow redirects, before returning the response to the user?

Codercord•11/29/24, 4:11 PM

<#1312088599444983808>

**Category**

Help needed

**Product**

Coder OSS (v2)

**Platform**

Linux

Logs

Please post any relevant logs/error messages.

SpaceMoehre-i-nator™OP•11/30/24, 12:30 PM

well i guess using the jupyter module i can still use sage, but the problem with http codes 302 persists

Phorcys•12/2/24, 9:55 AM

hello @SpaceMoehre-i-nator™, Coder is acting as a reverse-proxy for Jupyter, and redirects are always supposed to be passed down to the user

Phorcys•12/2/24, 9:55 AM

following redirects on the reverse-proxy side of things is very likely to introduce unwanted behavior

Phorcys•12/2/24, 9:59 AM

the issues you're encountering just means that Jupyter doesn't know its own path

Phorcys•12/2/24, 9:59 AM

are you using sub-paths or a wildcard domain to proxy your apps?

Phorcys•12/16/24, 5:32 PM

hey @SpaceMoehre-i-nator™, any luck?

SpaceMoehre-i-nator™OP•12/17/24, 8:50 AM

i found out that i can use the jupyter module and choose the sage interpreter in there

but for some reason i get this error for the last weeks:

SpaceMoehre-i-nator™OP•12/17/24, 8:50 AM

weird is that i dont use ipv6 anywhere, so where is that address coming from?

SSpaceMoehre-i-nator™weird is that i dont use ipv6 anywhere, so where is that address coming from?

Phorcys•12/17/24, 8:55 AM

this ipv6 is owned by tailscale, which is what we use to establish p2p connections to workspaces

SpaceMoehre-i-nator™OP•12/17/24, 8:56 AM

ok so the problem must originate from an incorrect tunnel to tailscale...

Phorcys•12/17/24, 8:56 AM

check the "DERP" section of the health page of your deployment, it should have some insight on this

Phorcys•12/17/24, 8:56 AM

maybe it is being firewalled away

SpaceMoehre-i-nator™OP•12/17/24, 11:13 AM

ok i guess i found the issue somewhere non network related
the log /tmp/jupyterlab.log showed

turns out juypter-lab has python3.13 in the shebang, which is not installed on my system since i need 3.9 for dependencies. is there a jupyter module version that uses python3 or <=python3.9 ?

SSpaceMoehre-i-nator™ok i guess i found the issue somewhere non network related the log /tmp/jupyterl...

Phorcys•12/17/24, 1:42 PM

oh yeah, the fact you sent it as text confused me

Phorcys•12/17/24, 1:43 PM

this is just an error on the web ui right?

Phorcys•12/17/24, 1:43 PM

the "502 - Bad Gateway" error

SSpaceMoehre-i-nator™ok i guess i found the issue somewhere non network related the log /tmp/jupyterl...

Phorcys•12/17/24, 1:44 PM

there is nothing we can do about the shebang, but you can just install on the side and it should work

SpaceMoehre-i-nator™OP•12/17/24, 2:25 PM

no prob, i fixed it. installing pipx via debian bookworms apt package defaulted to python3.13. installing via fixed my issue

SpaceMoehre-i-nator™OP•12/17/24, 2:26 PM

this is why on clicking the jupyterlab button, the new window displayed coders 502 code with "connection refused", since jupyterlab was unable to start due to misconfigured pipx

CodercordAPP•3/4/25, 5:59 PM

@Phorcys closed the thread.