Skip to content

ICE server not accessible through jupyter proxy #305

@sam-cohan

Description

@sam-cohan

Hi I am trying to use the Ought ICE server on a SageMaker notebook which only allows access to the local server through the jupyter server proxy. I am finding that when I go to the proxy path <notebook_path>/proxy/8935/ there is a blank page because the assets are not accessible since they are trying to be loaded from <notebook_path>/assets/ instead of <notebook_path>/proxy/8935/assets. I tried to manually change the index.html to look at the correct path and wrote a small flask server to make the assets available but now I am greeted with another internal server error which I am not even able to debug because there are no logs to be found anywhere (I was hoping to find logs under ~/.ought-ice/ but none were to be found.
Screenshot 2023-06-20 at 10 10 13 PM

I was wondering, any chance you could provide proper support for running the server behind jupyter proxy to enable working from inside SageMaker jupyter notebooks?. If that is not on your roadmap, any thoughts on how I can go about debugging this issue to get it working?

Thank you very much for your attention to the issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions