We may have posted to quickly. No need to provide support. If we are unable to resolve, I will post a follow up. Right now we think this might be a misunderstanding on our end.
On Monday, March 19, 2018 at 9:46:14 AM UTC-7, [email protected] wrote: > > Hi, > > We are struggling to get access to a jupyter lab instance running on > localhost. We have a docker container running all the software. I checked > STDOUT to get the token information: > > [I 16:37:53.682 LabApp] Writing notebook server cookie secret to > /root/.local/share/jupyter/runtime/notebook_cookie_secret > > [I 16:37:53.951 LabApp] JupyterLab beta preview extension loaded from > /usr/local/lib/python2.7/dist-packages/jupyterlab > > [I 16:37:53.951 LabApp] JupyterLab application directory is > /usr/local/share/jupyter/lab > > [W 16:37:53.954 LabApp] JupyterLab server extension not enabled, manually > loading... > > [I 16:37:53.955 LabApp] JupyterLab beta preview extension loaded from > /usr/local/lib/python2.7/dist-packages/jupyterlab > > [I 16:37:53.955 LabApp] JupyterLab application directory is > /usr/local/share/jupyter/lab > > [I 16:37:53.959 LabApp] Serving notebooks from local directory: /files > > [I 16:37:53.959 LabApp] 0 active kernels > > [I 16:37:53.960 LabApp] The Jupyter Notebook is running at: > > [I 16:37:53.960 LabApp] > http://0.0.0.0:8888/?token=1b6ed13a41fc410b176d92eac341e7984589061e8d8e0b8e > > [I 16:37:53.960 LabApp] Use Control-C to stop this server and shut down > all kernels (twice to skip confirmation). > > [W 16:37:53.961 LabApp] No web browser found: could not locate runnable > browser. > > [C 16:37:53.961 LabApp] > > > > Copy/paste this URL into your browser when you connect for the first > time, > > to login with a token: > > > http://0.0.0.0:8888/?token=1b6ed13a41fc410b176d92eac341e7984589061e8d8e0b8e > > > > However that link, takes us to this error page shown in the attachment. > We tried to get help through the documentation and stack overflow but have > not been able to locate anyone with this exact issue. The next step for us > is to disable the password, but we're reading a lot of warnings about this > being a bad idea. > > We are confident that there is only a single docker container and a single > instance of Jupyter running. This is not at all caused by two instances > running on the same machine, nor related to port forwarding. We are > definitely connected to the same instance that gave the standard out shown > above, yet it refuses to accept the provided token for entry. > > Can you please advise on why the token provided is not being accepted? > > > > -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/9b48d2d5-b47b-43e2-b729-6a619c4832bc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
