Skip to content
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

Octoprint - service cannot be started #3128

Closed
CarstenPueschel opened this issue Jan 28, 2018 · 6 comments · Fixed by #4096
Closed

Octoprint - service cannot be started #3128

CarstenPueschel opened this issue Jan 28, 2018 · 6 comments · Fixed by #4096
Labels

Comments

@CarstenPueschel
Copy link

Octoprint service won't start on DS-416play.
Protocol is empty ...
Version is 20160321-4

@ymartin59
Copy link
Contributor

Package has to be updated to DSM 6 generic service support. Related with #2599 and #2386

@broken-limiter
Copy link

#2599 has a workaround for missing unidecode
I'll test later today on my DS214play

thanks ymartin59 for the reference.

regards, broken

@Safihre Safihre added the dsm 6 label Mar 8, 2018
@Nickwren
Copy link

Is there any further progress on the octoprint issue?
I have tried the workaround but it doesn't seem to fix the issue.
This is such a useful tool for me.

Thanks.

@waazdakka
Copy link

One year later :) Any chance Octoprint could make a move to DSM6 ?

@vlotho
Copy link

vlotho commented Feb 10, 2020

hi,
I am also interested in this package.
I tried to modify the user in the octoprint.default file where
  it was set to "pi" and even adding "octoprint" to the sudoers file, nothing helps, it still does not start....

I use on version 6.1.

@hgy59 hgy59 mentioned this issue Apr 25, 2020
28 tasks
@Knedlos
Copy link

Knedlos commented Jun 4, 2020

Hi there,
I'm another one, who will be very happy to be able to use Octoprint on my DS 214 :-). Any chance to move this issue forward?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants