Open gdbarron opened 2 years ago
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 :)
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
to my moonraker config. I am now receiving a 502 when trying to connect.
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?