Server-0.23.5.jar not starting

[Ze_Pico]

Exception in thread "main" java.lang.RuntimeException: File does not contain valid private key: .\server_embedded.pem
        at cc.blynk.utils.SslUtil.initSslContext(SslUtil.java:71)
        at cc.blynk.server.hardware.HardwareSSLServer.<init>(HardwareSSLServer.java:36)
        at cc.blynk.server.launcher.ServerLauncher.start(ServerLauncher.java:78)
        at cc.blynk.server.launcher.ServerLauncher.main(ServerLauncher.java:70)
    indent preformatted text by 4 spaces

Server 0.23.3 was ok

Blynk Server 0.23.3 successfully started.
All server output is stored in folder 'C:\Blynk_Server\.\logs' file.

[Dmitriy]

Hello. What is your server.properties?

[Ze_Pico]

@Dmitriy
Hello
my server.properties

#hardware mqtt port
hardware.mqtt.port=8440

#hardware ssl port
hardware.ssl.port=8441

#hardware plain tcp/ip port
hardware.default.port=8442

#http port
http.port=8080

#web sockets ssl port
ssl.websocket.port=8081
#web sockets plain tcp port
tcp.websocket.port=8082


#https port
https.port=9443

#application ssl port
app.ssl.port=8443

#by default server uses embedded in jar cert to simplify local server installation.
#WARNNING DO NOT USE THIS CERTIFICATES ON PRODUCTION OR IN WHERE ENVIRNOMENTS REAL SECURITY REQUIRED.
#provide either full path to files either use '.' for specifying current directory. For instance "./myfile.crt"
server.host=
server.ssl.cert=./server_embedded.crt
server.ssl.key=./server_embedded.pem
server.ssl.key.pass=

#Blynk server allows to use 2 hosts for same IP, below properties for second host
server2.host=
server2.ssl.cert=./server_embedded.crt
server2.ssl.key=./server_embedded.pem
server2.ssl.key.pass=

client.ssl.cert=
client.ssl.key=

#by default System.getProperty("java.io.tmpdir")/blynk used
data.folder=

#folder for logs.
logs.folder=./logs

#log debug level. trace|debug|info|error. Defines how precise logging will be.
log.level=info

#defines maximum allowed number of user dashboards. Needed to limit possible number of tokens.
user.dashboard.max.limit=10

#defines maximum allowed widget size in KBs as json string.
user.widget.max.size.limit=10

#user is limited with 100 messages per second.
user.message.quota.limit=100
#in case of consistent quota limit exceed during long term, sending warning response back to exceeding channel
#for performance reason sending only 1 message within interval. In millis
user.message.quota.limit.exceeded.warning.period=60000

#maximum allowed number of notification queue. Queue responsible for processing email, pushes, twits sending.
#Because of performance issue - those queue is processed in separate thread, this is required due
#to blocking nature of all above operations. Usually limit shouldn't be reached.
notifications.queue.limit=10000

#Number of threads for performing blocking operations - push, twits, emails, db queries.
#Recommended to hold this value low unless you have to perform a lot of blocking operations.
blocking.processor.thread.pool.limit=5

#this setting defines how often we can send mail/tweet/push or any other notification. Specified in seconds
notifications.frequency.user.quota.limit=60

#maximum size of user profile in kb's
user.profile.max.size=128

#period in millis for saving all user DB to disk.
profile.save.worker.period=60000

#period in millis for saving stats to disk.
stats.print.worker.period=60000

#specifies maximum period of time when application socket could be idle. After which
#socket will be closed due to non activity. In seconds. Default value 600 if not provided.
#leave it empty for infinity timeout
app.socket.idle.timeout=600
#specifies maximum period of time when hardware socket could be idle. After which
#socket will be closed due to non activity. In seconds. Default value 15 if not provided.
#leave it empty for infinity timeout
hard.socket.idle.timeout=15

#Enables native socket transport for Linux using JNI. Should be turned on only if you 100% sure.
#may not work on some environments. Used to increase server performance. Performance boost is ~20-40%.
enable.native.epoll.transport=false

#Enabled native openSSL support for SSL handlers. Should be turned on only if you 100% sure.
#may not work on some environments. Used to increase server performance. Performance boost is ~16%.
#For more details see - http://netty.io/wiki/forked-tomcat-native.html
enable.native.openssl=false

#mostly required for local servers setup in case user want to log raw data in CSV format
#from his hardware
#enable.raw.data.store=true

#enable raw data storage to DB
enable.raw.db.data.store=false

#size of async logger ring buffer. should be increased for loads >2-3k req/sec
async.logger.ring.buffer.size=8192


#ADMINISTRATION SECTION

admin.rootPath=/admin

#administration https port
administration.https.port=9443

#reset pass port
reset.pass.http.port=7444
#host for reset pass redirect. by default current server IP is taken. could be replaced with more friendly hostname.
#it is recommended to override this property with your server IP to avoid possible problems of host resolving
reset-pass.http.host=blynk-cloud.com

#comma separated list of administrator IPs. allow access to admin UI only for those IPs.
#you may set it for 0.0.0.0/0 to allow access for all.
#you may use CIDR notation. For instance, 192.168.0.53/24
allowed.administrator.ips=127.0.0.1


#comma separated list of users allowed to create accounts. leave it empty if no restriction required.
allowed.users.list=

[Dmitriy]

You need to have :

server.ssl.cert=
server.ssl.key=
server.ssl.key.pass=

In case you don’t use own certificates.

[Ze_Pico]

@Dmitriy

[Dmitriy]

What do you mean by this screen?

[Ze_Pico]

@Dmitriy

server.ssl.cert=
server.ssl.key=
server.ssl.key.pass=

ssl cert and keys are there

[Dmitriy]

How empty fields “are there”? Sorry, I do not understand what you are trying to say.

[Ze_Pico]

in my server.properties fields are not empty.
could you please explain.

#by default server uses embedded in jar cert to simplify local server installation.
#WARNNING DO NOT USE THIS CERTIFICATES ON PRODUCTION OR IN WHERE ENVIRNOMENTS REAL SECURITY REQUIRED.
#provide either full path to files either use '.' for specifying current directory. For instance "./myfile.crt"
server.host=
server.ssl.cert=./server_embedded.crt
server.ssl.key=./server_embedded.pem
server.ssl.key.pass=

#Blynk server allows to use 2 hosts for same IP, below properties for second host
server2.host=
server2.ssl.cert=./server_embedded.crt
server2.ssl.key=./server_embedded.pem
server2.ssl.key.pass=

[Dmitriy]

@Dmitriy

You need to have :

server.ssl.cert=
server.ssl.key=
server.ssl.key.pass=

In case you don’t use own certificates.

I explained above

[Ze_Pico]

did you read what i am typing?

server.ssl.cert=./server_embedded.crt
server.ssl.key=./server_embedded.pem

[Dmitriy]

Yes. And I gave you an answer of what you should do.

[Ze_Pico]

ok
where can i find a tutorial ?
as me and many others knows nothing in java.

Here you can find many requests.

[Dmitriy]

You just have outdated configs. That’s all. It is not related to java.

[Ze_Pico]

@Dmitriy @Pavel

More Help is needed

Continuing the discussion from Local Blynk Server Tutorial:

Continuing the discussion from Local Blynk Server Tutorial:

@Dmitriy

I agree, but all this is not simple at all. Generating free certs is a quest for few hours at least.

@mars

however i’m after more details step-by-step example/tutorial on setting up more advanced features such as SSL, mail (specifically SSL so i can ensure local server is well protected).e.g. questions i have include:

how do i create an account structure so a username and password needs to be entered to access local blynk admin server
how do I request password reset from admin server
how do i configure server/gateway so i can access admin page on my local blank server securely from outside my firewall/gateway (i.e. from wider internet)

hoping you can help as I believe this sort of information/tutorial would benefit the community as a whole.

[Dmitriy]

blynkkk/blynk-server

[Ze_Pico]

WARNING: You should have password for certificate. Certificates without passwords are not accepted.

openssl pkcs8 -topk8 -inform PEM -outform PEM -in server.key -out server.pem

can you tell us how to?

[Costas]

@Ze_Pico from memory it should ask you for a password as part of the process when you issue the command.

[Dmitriy]

@Ze_Pico

WARNING

@Ze_Pico

can you tell us how to?

This was fixed and password is not required anymore. However in case of those instruction you should be promted with password.

[Ze_Pico]

@Costas
Hi Costas

@Costas

it should ask you for a password as part of the process when you issue the command.

yes. but it don’t accept any entry. " only the enter key"

C:\My_Server>openssl pkcs8 -topk8 -inform PEM -outform PEM -in server.key -out server.pem
Enter Encryption Password:
Verifying - Enter Encryption Password:
Verify failure

can you try it for me.