[randomlurking]

Im working exclusively with a remote connection (although inside the company network, so some security concerns don’t apply). I have Jupyter running as a service on Linux and am using a password instead of the generated token. So the URL stays the same and I don’t have to worry about anything much. The setup is working good for me - there are a couple of nuisances but they’re all related to the rest of my circumstances and use case, not to anything mentioned above.

[nerdponx]

Ah, so you have Jupyter itself running remotely? I was hoping you had a good workflow for starting or connecting to remote kernels using a local Jupyter frontend. This seems like such an obvious use case, but the ecosystem support for it is surprisingly poor. I've tried and failed several times over the years to figure out a workflow that a regular scientist or industry data analysit could follow.