-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
[Bug] Midi config preventing server start #760
Comments
There no difference between the two versions that could explain that (v1.11.0...v1.11.1). I also went through the packaging logs to verify nothing went weird for this release. I'll test on a windows system when I can. |
I installed the most recent version on a different Windows machine, and the error is gone. Turns out this is a (very mysterious) problem on my side... |
Glad to hear that, thanks for the update. |
i am having the same error ((ERROR, HTTP) Could not setup http server, maybe try a different port ?) without any midi settings, after having moved to windows 11. same settigns work fine on other PCs (windows 10). |
Did you try setting the port option to anything else than the default
8080 as suggested in the error message ? The operating system may be
using it already.
Le 06/06/2022 à 13:29, nilsporrmann a écrit :
…
i am having the same error ((ERROR, HTTP) Could not setup http server,
maybe try a different port ?) without any midi settings, after having
moved to windows 11. same settigns work fine on other PCs (windows 10).
—
Reply to this email directly, view it on GitHub
<#760 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIESZ4B5NCGFEBFNSMJO53VNXOLPANCNFSM5JHPY4KQ>.
You are receiving this because you commented.Message ID:
***@***.***>
|
If I enter something on the midi router config box (e.g.
midi:0,1
) I get the following error:(ERROR, HTTP) Could not setup http server, maybe try a different port ?
With all settings empty the server starts and everything works.
Version is 1.11.1. I'm on 64-bit Windows.
The previous version (1.11.0) works, so it seems this was introduced in one of the latest commits.
The text was updated successfully, but these errors were encountered: