Skip to content
This repository has been archived by the owner on Dec 17, 2024. It is now read-only.

502 after latest update and PolicyKit permissions #39

Open
gdbarron opened this issue Jun 16, 2022 · 1 comment
Open

502 after latest update and PolicyKit permissions #39

gdbarron opened this issue Jun 16, 2022 · 1 comment

Comments

@gdbarron
Copy link

I've recently updated klipper, moonraker, and fluidd via the UI and received a subsequent warning regarding PolicyKit. I followed option 2 at https://moonraker.readthedocs.io/en/latest/installation/#policykit-permissions and added

[machine]
provider: systemd_cli

# Edit your existing [update_manager] section to disable
# PackageKit.  This will fallback to the APT CLI Package Update
# implementation.
[update_manager]
#..other update manager options
enable_packagekit: False

to my moonraker config. I am now receiving a 502 when trying to connect.
image

Unfortunately, I must have had bad timing and upgraded to the 1.18 release which is no longer allowing me to ssh. As I can't login to fix the moonraker config, do I have any other path forward than to rebuild?

Also, why did the addition of those 2 entries cause the 502?

@matmen
Copy link
Member

matmen commented Jun 27, 2022

Sorry for the late response, but so far I have only seen this error occur when moonraker was being restarted and fluidd tried to access it while it was down. Usually a refresh fixed it for me.
If this issue persists I imagine moonraker failed to start, so this is most likely a configuration error (though I'm not sure why it would fail to start up again..). The SSH login has already be fixed upstream and will be included in the next release. Please let me know if there's any additional help you need :)

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

No branches or pull requests

2 participants