-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document 'delete everything and start over' as a troubleshooting tactic #338
Comments
Thanks for opening this, @znicholls! When you say 're-booting', did you turn it off and on or delete and re-create? Knowing that would be useful. Related discussion at #128 |
Delete and re-create
…On Mon, 20 May 2019 at 1:41 pm, Yuvi Panda ***@***.***> wrote:
Thanks for opening this, @znicholls <https://github.com/znicholls>! When
you say 're-booting', did you turn it off and on or delete and re-create?
Knowing that would be useful.
Related discussion at #128
<#128>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#338?email_source=notifications&email_token=AFUH5G7ACOGZAFKAIH3BFS3PWIMXPA5CNFSM4HN5T3KKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVXTX7A#issuecomment-493829116>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFUH5G33T4GIOTBES6GVA3TPWIMXPANCNFSM4HN5T3KA>
.
|
@znicholls makes sense! I agree we should document that. Would love it if you can work on a PR to insert it. Is that something you're up for doing? |
yep will do in #325 |
I think it also be worth including how to do this on custom server, e.g., including steps/links to docs for taking down jupyterlab or which commands to run to restart the server. |
As raised in #325, I somehow managed to break my server, but a day later it worked after re-building the machine. I can't reproduce the issue and am not sure what I did, I might have installed and then uninstalled Apache so was blocking the port, I might have had the wrong security settings when I booted the VM, I might have somehow bungled my ports as I was playing around with firewalls, not sure...
Would it be worth adding a 'Have you tried re-booting from scratch?' reminder to the troubleshooting page of custom servers?
The text was updated successfully, but these errors were encountered: