[1.3.10rc1] Connect not possible with disabled access control

[trendelkamp]

#### What were you doing?

1. Upgrade to 1.3.10rc1
2. Rebootet
3. Not possible to connect anymore

#### What did you expect to happen?
Connect OctoPrint to the printer

#### What happened instead?
The whole connection options are disabled. Only Disconnect is available but with no effect after pressing the button.
Also i´m not able to switch back to the stable version. Nothing happens after i select the stable channel.

#### Did the same happen when running OctoPrint in safe mode?
Yes

#### Version of OctoPrint
OctoPrint 1.3.10rc1 auf OctoPi 0.14.0

#### Operating System running OctoPrint
OctoPi

#### Printer model & used firmware incl. version
CR-10; MKS Gen 1.4 Board, Marlin 1.1.9

#### Browser and version of browser, operating system running browser
Chrome & Edge, latest Version

#### Link to octoprint.log

https://pastebin.com/wRcM0MEC

Link to contents of terminal tab or serial.log

Empty

Link to contents of Javascript console in the browser

https://pastebin.com/vNjku5Q2

Screenshot(s)/video(s) showing the problem:

[GitIssueBot]

Hi @trendelkamp,

It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).

If you did not intend to report a bug but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines.

Please do not abuse the bug tracker as a support forum - that can be found at discourse.octoprint.org. Go there for any kind of issues with network connectivity, webcam functionality, printer detection or any other kind of such support requests or general questions.

Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please.

I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2018-11-20 16:30 UTC) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.

[foosel]

Looks like a duplicate of #2875, please try and report back on what's suggested there. Your Pi is also reporting undervoltage - check your power supply, it doesn't seem to be beefy enough.

[foosel]

Reopening because it appears to be a different issue than #2875 after all:

So, the debug session with @trendelkamp revealed that there is a still a bug in the new Force Login plugin that doesn't handle disabled ACLs correctly. Disabling the plugin and restarting OctoPrint made it work again for @trendelkamp.

[foosel]

Fixed by the above commit (with slightly misleading message -_-), will be part of 1.3.10rc2.

[mattgaspar]

@foosel I also had this issue and disabling the Force Login plugin allowed it to connect again.

What do you mean by "disabled ACLs"? I think when I first setup OctoPi, I skipped setting a password. Is that what you are referring to? When I skipping setting a password I figured I could set it up later but I looked everywhere for a setting or instructions and was unable to find anything. I even tried connecting to the PI thru SSH and looking for a configuration file. (this was almost a year ago)
Is there something I missed? Or do I need to do a clean install?

Thanks
Matt

(It is currently accessible through my firewall although it's usually turned off!)

[foosel]

What do you mean by "disabled ACLs"? I think when I first setup OctoPi, I skipped setting a password. Is that what you are referring to?

Yes

Is there something I missed?

My money would be on the documentation ;)

[foosel]

1.3.10rc2 was just released.