PostGreSQL install on Windows 10 - not enabled

Hi,
I have latest version of Blynk Server running locally on Windows 10 - all is working well. Now I would like to enable the database.

Followed the steps as outlined, but since on windows, instead of install postgresql through command, I used the windows installer. Server properties updated, saw output for step 6 running the sql. Updated the table access in postgresql.

Can you confirm using the postgresql installer, it isn’t working? How can I run install properly on windows 10? I’m more a data scientist than a programmer…

Thank you!

postgres log:
09:36:31.504 - Separate DB storage disabled.

Blynk log:
09:36:31.488 INFO - Using data dir ‘C:\Users\paulh\Blynk\Data’
09:36:31.847 INFO - Region : local
09:36:32.910 INFO - Initializing gmail smtp mail transport. Username : XXXXX@gmail.com. SMTP host : smtp.gmail.com:587
09:36:32.941 INFO - Didn’t find custom user certificates.
09:36:32.941 INFO - Didn’t find Let’s Encrypt certificates.
09:36:32.941 WARN - You didn’t specified ‘server.host’ or ‘contact.email’ properties in server.properties file. Automatic certificate generation is turned off. Please specify above properties for automatic certificates retrieval.
09:36:32.941 WARN - ATTENTION. Server certificate paths (cert : ‘C:\Users\paulh\Blynk’, key : ‘C:\Users\paulh\Blynk’) not valid. Using embedded server certs and one way ssl. This is not secure. Please replace it with your own certs.
09:36:33.863 INFO - Hardware plain tcp/ip server listening at 8442 port.
09:36:33.863 INFO - Hardware SSL server listening at 8441 port.
09:36:33.863 INFO - Application server listening at 8443 port.
09:36:33.863 INFO - HTTP API and WebSockets server listening at 8080 port.
09:36:33.863 INFO - HTTPS API, WebSockets and Admin page server listening at 9443 port.
09:36:33.863 INFO - Mqtt hardware server listening at 8440 port.
09:36:34.488 INFO - paulblynk@gmail.com hardware joined.

Hello. Did you change server.properties?

Yes to:
enable.db=true
enable.raw.db.data.store=true

Also, I set the table privilages as per:

This message can appear only in case you didn’t specify enable.db property in file. It could be old message. Please remove logs and start server again and check if that message exists.

upgraded to 26.1, removed the logs, restarted server, App and devices connect - working well, but still the same message in the log. Other ideas? Thank you for your help

Here is the system file.

*****************************************
#hardware mqtt port
hardware.mqtt.port=8440

#hardware ssl port
hardware.ssl.port=8441

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

#http and web sockets port
http.port=80

#https and web sockets port
https.port=9443

#application ssl port
app.ssl.port=8443

#address to bind to. by default bounded to all interfaces
listen.address=

#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.ssl.cert=./server_embedded.crt
server.ssl.key=./server_embedded.pem
server.ssl.key.pass=

#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

#maximum number of devices allowed per account
user.devices.limit=25

#maximum number of tags allowed per account
user.tags.limit=100

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

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

#user is limited with 100 messages per second.
user.message.quota.limit=100

#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=5000

#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=6

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

#this setting defines how often we can send webhooks. Specified in miliseconds
webhooks.frequency.user.quota.limit=1000

#this setting defines how big could be response for webhook GET request. Specified in kbs
webhooks.response.size.limit=72

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

#number of strings to store in terminal widget
terminal.strings.pool.size=25

#number of strings to store in map widget
map.strings.pool.size=25

#number of strings to store in lcd widget
lcd.strings.pool.size=6

#maximum number of rows allowed
table.rows.pool.size=100

#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 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

#enable DB
enable.db=true

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

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

#initial amount of energy
initial.energy=100000

#ADMINISTRATION SECTION

admin.rootPath=/admin

#used for reset password page and certificate generation.
#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
#server.host=test.blynk.cc

#email used for certificate registration, could be omitted in case you already specified it in mail.properties
#contact.email=

#network interface to determine server's current IP.
#only the first characters of the interface's name are needed.
#the default setting eth will use the first ethX interface found (i.e. eth0)
net.interface=eth

#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=0.0.0.0/0,::/0

# default admin name and password. that will be created on initial server start
admin.email=XXX@yahoo.com
admin.pass=XXX

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

TOTAL USER ERROR!!! pretty dumb, called the file system instead of server.properties… now it is working - let me go figure out how to get the data out in csv

@Dmitriy You can delete the threat - dont think there is much value for others