Hello all,
--
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 jupyter+unsubscribe@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/7b7224d9-638f-4564-8cc0-d08b6e64d2dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Are you perhaps visiting the internal port (8081) with your browser rather than the public one? That would result in bypassing the proxy, which will give you a redirect loop-Min
On Thu, Mar 22, 2018 at 6:22 PM, Hongyu Pang <vic...@umich.edu> wrote:
Hello all,
I am currently using jupyterhub but get stuck by the redirect loop issue for a few days. I am using: ubuntu14 in virtualbox, installed jupyterhub using pip, here is my configuration in attached image cong.JPG, and the issue I run into is shown in juphub.JPGBasically I am running jupyterhub using root, then after I log in as pompy, there seems error related to redirect loop. I am using PAM and has not configured any redirect loop. Any idea what happened and how to solve this?Victor
--
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 jupyter+u...@googlegroups.com.
Hello Min,Thanks very much for the reply! I feel this should be the reason. I tried the next few things:1) tried to visit the 443 port. but it seems I cannot find it. like in img1, proxy is at *:443. Also I found a proxy:304 log: adding missing default route to 127.0.0.1:80812) I modified my configuration, adding c.JupyterHub.ip='127.0.0.1', the log is in img2, now I can visit 127.0.0.1, but it says connection not secure, firefox refused to connect3) I generated the ssl using "openssl req -x509 -nodes -days 365 -newkey rsa:1024 -keyout jupyterhub.key -out jupyterhub.crt", next I did not encrypt, I think this is the problem. Then I tried letsencrypt. But I don't have a domain name. I tired localhost , or 127.0.0.1, but neither works.So my question is, do I need a domain name to deploy jupyterhub? What next thing do you think I should try? From img3 we can see the server is up, the only problem happens at visiting that page.
Victor
On Friday, March 23, 2018 at 5:07:02 AM UTC-4, Min RK wrote:Are you perhaps visiting the internal port (8081) with your browser rather than the public one? That would result in bypassing the proxy, which will give you a redirect loop-MinOn Thu, Mar 22, 2018 at 6:22 PM, Hongyu Pang <vic...@umich.edu> wrote:--Hello all,
I am currently using jupyterhub but get stuck by the redirect loop issue for a few days. I am using: ubuntu14 in virtualbox, installed jupyterhub using pip, here is my configuration in attached image cong.JPG, and the issue I run into is shown in juphub.JPGBasically I am running jupyterhub using root, then after I log in as pompy, there seems error related to redirect loop. I am using PAM and has not configured any redirect loop. Any idea what happened and how to solve this?Victor
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 jupyter+u...@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/7b7224d9-638f-4564-8cc0-d08b6e64d2dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 jupyter+unsubscribe@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/ea0e1d87-83e4-4718-a780-20c801d49a1f%40googlegroups.com.
You don't need a domain name, but if you want to use SSL, getting SSL set up without a domain can be tricky. For trusted SSL you do need to either have a real domain or manually trust the certificate at the system level. Different OSes have different ways to do this. Using self-signed and clicking through the scary warnings tends to work (websockets on Safari being one exception). I think some browsers may refuse to trust a certificate issued for 127.0.0.1, though.-Min