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

HTTPS support is broken for a printer farm #439

Closed
RomRider opened this issue Nov 29, 2021 · 0 comments · Fixed by #452
Closed

HTTPS support is broken for a printer farm #439

RomRider opened this issue Nov 29, 2021 · 0 comments · Fixed by #452
Labels
⚡ Type: Bug Something isn't working

Comments

@RomRider
Copy link
Contributor

RomRider commented Nov 29, 2021

Describe the bug:
I'm running Mainsail in https and in docker.
In this setup, multiple printer setup is not possible as the browser complains that the websocket needs to be opened using the wss protocol.

Note: I'm also running my Moonraker instances behind HTTPS.

This line always returns ws://:

return state.socket.protocol+'://'+state.socket.hostname+':'+state.socket.port+'/websocket'

Expected behavior:
I can use the printer farm feature while running Mainsail and Moonraker behind HTTPS

Screenshots:
N/A

Logfiles:
Please upload your Logfiles here or upload them to pastebin.com and paste your log links here.

  • klippy.log
  • moonraker.log
@RomRider RomRider added the ⚡ Type: Bug Something isn't working label Nov 29, 2021
@RomRider RomRider changed the title HTTPS support is broken for a printer farm. HTTPS support is broken for a printer farm Nov 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⚡ Type: Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant