-
Notifications
You must be signed in to change notification settings - Fork 10
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
Setting SSL to true causes the server to shutdown #9
Comments
Here's my issue with the starting sequence; dunno if it's related or not: |
@MuhsinunCool no it isn't, unless your issue also involves enabling SSL, and the server stopping the moment the websocket is started. |
@RoboMWM Just thot that since urs sed this: |
Not related, I get that regardless of the SSL setting I use. |
Have you followed the instructions for using https? From the bukkitdev page:
|
JPanel is also causing the server to stop when it's reloaded. Seeing that the message comes from another thread (not the main thread), my guess is that jetty or whatever is calling a System#exit or similar? |
It's not because of setting ssl to true. It's hard coded into the plugin.
Use ploader | bypass plugin limit restrictions to work around that issue.
…On Tue, Aug 28, 2018, 4:14 PM RoboMWM ***@***.***> wrote:
JPanel is also causing the server to stop when it's reloaded. Seeing that
the message comes from another thread (not the main thread), my guess is
that jetty or whatever is calling a System#exit or similar?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AL_oO7XU3mBRoRxoQg5FTUPKPO2-yttHks5uVbLNgaJpZM4J3YPP>
.
|
No idea what you're talking about here. What plugin limit restriction are you talking about? Where is this hardcoded into the plugin? (I did searches for "shutdown" with no results in github search). |
Also, not saying it's the root cause, but setting SSL to true without having a cert setup does cause the plugin (or whatever library) to shutdown the server. |
I guess @rymate1234 removed the Bukkit#shutdown call in onDisable in a recent commit, but once upon a time it was there and that's what I was referring to. ploader-bypass-plugin-limit-restrictions.56669/ |
He does have stop() (or did, idk rn), but I never saw shutdown(). Would you know what version had it? Because there was no shutdown() existing in the codebase last year |
No idea what that plugin is for other than allowing you to blacklist plugins that should not be reloaded when running a server reload. I do not use /reload but an arguably even eviler /plugman reload :p |
Also I should add that this has nothing to do with reloading the plugin, nor is the shutdown method called from the main thread given the provided log. |
Yea I know I don't have a SSL certificate, but something odd is causing the server to instantly shut down the moment the web socket is enabled:
The text was updated successfully, but these errors were encountered: