-
Notifications
You must be signed in to change notification settings - Fork 33
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
Can not start server. 500 Error #2
Comments
That sounds like a spawner error, rather than authenticator. Can you share
your jupyterhub_config.py and what spawner you are using?
…On Wed, Jan 18, 2017 at 1:10 AM, etikhomolov ***@***.***> wrote:
When I create new user/password which are not the users on Linux server
where jupyterhub is running I get:
500 : Internal Server Error
Failed to start your server. Please contact admin.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB23mNrTFYs9-CXAHGT2j1yreaoRdfJks5rTRk3gaJpZM4LmE2c>
.
--
Yuvi Panda T
http://yuvi.in/blog
|
Thank you for your prompt reply. Configuration file for jupyterhub.#------------------------------------------------------------------------------ Application(SingletonConfigurable) configuration#------------------------------------------------------------------------------ This is an application.The date format used by logging formatters for %(asctime)s#c.Application.log_datefmt = '%Y-%m-%d %H:%M:%S' The Logging format template#c.Application.log_format = '[%(name)s]%(highlevel)s %(message)s' Set the log level by value or name.#c.Application.log_level = 30 #------------------------------------------------------------------------------ JupyterHub(Application) configuration#------------------------------------------------------------------------------ An Application for starting a Multi-User Jupyter Notebook server.Grant admin users permission to access single-user servers.Users should be properly informed if this is enabled.#c.JupyterHub.admin_access = False DEPRECATED, use Authenticator.admin_users instead.#c.JupyterHub.admin_users = set() Answer yes to any questions (e.g. confirm overwrite)#c.JupyterHub.answer_yes = False PENDING DEPRECATION: consider using service_tokensDict of token:username to be loaded into the database.Allows ahead-of-time generation of API tokens for use by externally managedservices, which authenticate as JupyterHub users.Consider using service_tokens for general services that talk to the JupyterHubAPI.#c.JupyterHub.api_tokens = {} Class for authenticating users.This should be a class with the following form:- constructor takes one kwarg:
|
Closed by mistake |
is this issue solved?Any update?? |
Because this is 3 years old and too much has changed since with JupyterHub even though if this authenticator hasn't, it is simply too complicated to debug this without a fresh report of the situation. I'll close this issue and hope that someone that experience this problem and believes it is the authenticators fault submits a new issue and documents a fresh situation. |
The reason in my case simply seems to be that FirstUseAuthenticator does not work with LocalProcessSpawner. |
When I create new user/password which are not the users on Linux server where jupyterhub is running I get:
500 : Internal Server Error
Failed to start your server. Please contact admin.
The text was updated successfully, but these errors were encountered: