-
-
Notifications
You must be signed in to change notification settings - Fork 170
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
Not able to use a certificate to allow HTTPS for the webserver #3869
Comments
When it says keystore pass is incorrect, the -passout password and Store_pass don't match. Make sure you didn't include the {} around the password, e.g. -passout 123 instead of -passout {123} |
I did not include the {}, and I ran several attempts to make sure that the password is actually correct. I can guarantee that I typed the exact same password for both fields prompted in the cmd line tool and typed the same passwords into the config file. |
Could you send the command that you used? And did you use windows or Linux to execute? Did you try removing the \ in the example? Those sometimes cause trouble. Also did you create the empty p12 file with the command specified in the tutorial? (Just making sure) - using an FTP client to create the file can make it a text file that fails to be written to Also is the password 123 or something more complicated? Using a $ in bash might interpret it as start of a variable rather than a $-character |
Was not a misconfig -- kept the exact same config & pkcs file and updated my server to 1.21 and it worked flawlessly. It simply seems that PLAN bugs out when the server is an older version. Closing the ticket as this has been solved (for me atleast). |
Describe the issue
I was attempting to set up the certificate for the webserver but it keeps telling me the certificate password is wrong. After the first attempt, i recreated it with no passes as said in the wiki, then I recreated it with the pass "123", which didn't work, then I tried not using the pass option like the wiki says and manually entering "123", which also didn't work. Plan was reloaded between attempts and all other settings where changed properly.
Exceptions & Other Logs
Exception Log
What was logged in console upon reloading the plugin (specifically what was logged on the most recent attempt, which was the last attempt described in the describe the issue section)
Relevant config section
Plugin versions
Plan version: 5.6 build 2883
Additional information
Minecraft Version: 1.16.5
If I missed anything let me know please! I tried to add as much info as possible.
The text was updated successfully, but these errors were encountered: