Local server starts but I cant login

And the sign-in attempt returns what message?

Pete.

no message

Okay, I’ve changed my logging level to match yours. If i try to log-in with the wrong credentials then I get pretty-much the same result as you…

TRACE- Initialized admin pipeline. [SslHandler#0, HttpsServerCodec, HttpsServerKeepAlive, HttpsObjectAggregator, HttpChunkedWrite, HttpUrlMapper, UploadHandler#0, OTAHandler#0, AdminAuthHandler#0, AuthCookieHandler#0, CookieBasedUrlReWriterHandler#0, StaticFileHandler#0, OTALogic#0, UsersLogic#0, StatsLogic#0, ConfigsLogic#0, HardwareStatsLogic#0, HttpAPILogic#0, NoMatchHandler#0, DefaultChannelPipeline$TailContext#0]
DEBUG- POST : /admin/login
TRACE- Mapping from /admin to /admin
TRACE- Is unpacked.

With the correct credentials I get an extra line that says “DEBUG- Admin login is successful. Redirecting to /admin” …

TRACE- Initialized admin pipeline. [SslHandler#0, HttpsServerCodec, HttpsServerKeepAlive, HttpsObjectAggregator, HttpChunkedWrite, HttpUrlMapper, UploadHandler#0, OTAHandler#0, AdminAuthHandler#0, AuthCookieHandler#0, CookieBasedUrlReWriterHandler#0, StaticFileHandler#0, OTALogic#0, UsersLogic#0, StatsLogic#0, ConfigsLogic#0, HardwareStatsLogic#0, HttpAPILogic#0, NoMatchHandler#0, DefaultChannelPipeline$TailContext#0]
DEBUG- POST : /admin/login
DEBUG- Admin login is successful. Redirecting to /admin
TRACE- Mapping from /admin to /admin
TRACE- Is unpacked.

It seems that the credentials aren’t being recognised as valid.

Is there any possibility that your server.credentials file isn’t actually being recognised, or that you have another one somewhere (maybe hidden) that is being used, with different credentials in it?

I guess one way to test this is to change your logging level from trace to debug and re-start your server then check the logs. If the TRACE entries disappear and you only have INFO and DEBUG entries then what you think is the correct server.properties file is being used.

You could then try to change the credentials in the server.properties file to something other than admin@blynk.cc/admin

Pete.

Okay I will give it a try

Thanks

11:34:37.090 INFO - Using data dir ‘blynk-data’
11:34:37.115 DEBUG- Starting reading user DB.
11:34:37.336 DEBUG- Reading user DB finished.
11:34:37.337 INFO - Region : local. Host : *.blynk.cc.
11:34:37.358 INFO - Using native epoll transport.
11:34:37.619 INFO - Initializing gmail smtp mail transport. Username : SMTP host : smtp.gmail.com:587
11:34:37.647 INFO - Reports : 0
11:34:37.649 INFO - Didn’t find Let’s Encrypt certificates.
11:34:37.649 INFO - Automatic certificate generation is turned ON.
11:34:37.649 INFO - Using native openSSL provider.
11:34:37.649 WARN - ATTENTION. Server certificate paths (cert : ‘/home/michael/Documents/Blynk-server/./server_embedded.crt’, key : ‘/home/michael/Documents/Blynk-server/./server_embedded.pem’) not valid. Using embedded server certs and one way ssl. This is not secure. Please replace it with your own certs.
11:34:38.162 DEBUG- hard.socket.idle.timeout = 10
11:34:38.203 INFO - HTTP API and WebSockets server listening at 8080 port.
11:34:38.204 INFO - HTTPS API, WebSockets and Admin page server listening at 9443 port.
11:34:38.205 INFO - Mqtt hardware server listening at 8440 port.
11:34:47.440 DEBUG- Unsecured connection attempt or not supported protocol. Channel : /10.0.0.236:36410. Reason : javax.net.ssl.SSLHandshakeException: error:10000412:SSL routines:OPENSSL_internal:SSLV3_ALERT_BAD_CERTIFICATE
11:34:55.097 DEBUG- POST : /admin/login

Okay, so it is reading the correct server.properties file.
Now try changing the credentials to something different and see if that works.

Pete.

11:41:39.709 INFO - Using data dir ‘blynk-data’
11:41:39.734 DEBUG- Starting reading user DB.
11:41:39.955 DEBUG- Reading user DB finished.
11:41:39.956 INFO - Region : local. Host : *.blynk.cc.
11:41:39.978 INFO - Using native epoll transport.
11:41:40.241 INFO - Initializing gmail smtp mail transport. Username : removed. SMTP host : smtp.gmail.com:587
11:41:40.269 INFO - Reports : 0
11:41:40.271 INFO - Didn’t find Let’s Encrypt certificates.
11:41:40.271 INFO - Automatic certificate generation is turned ON.
11:41:40.271 INFO - Using native openSSL provider.
11:41:40.271 WARN - ATTENTION. Server certificate paths (cert : ‘/home/michael/Documents/Blynk-server/./server_embedded.crt’, key : ‘/home/michael/Documents/Blynk-server/./server_embedded.pem’) not valid. Using embedded server certs and one way ssl. This is not secure. Please replace it with your own certs.
11:41:40.735 DEBUG- hard.socket.idle.timeout = 10
11:41:40.762 INFO - HTTP API and WebSockets server listening at 8080 port.
11:41:40.768 INFO - HTTPS API, WebSockets and Admin page server listening at 9443 port.
11:41:40.768 INFO - Mqtt hardware server listening at 8440 port.

11:41:39.709 INFO - Using data dir ‘blynk-data’
11:41:39.734 DEBUG- Starting reading user DB.
11:41:39.955 DEBUG- Reading user DB finished.
11:41:39.956 INFO - Region : local. Host : *.blynk.cc.
11:41:39.978 INFO - Using native epoll transport.
11:41:40.241 INFO - Initializing gmail smtp mail transport. Username :. SMTP host : smtp.gmail.com:587
11:41:40.269 INFO - Reports : 0
11:41:40.271 INFO - Didn’t find Let’s Encrypt certificates.
11:41:40.271 INFO - Automatic certificate generation is turned ON.
11:41:40.271 INFO - Using native openSSL provider.
11:41:40.271 WARN - ATTENTION. Server certificate paths (cert : ‘/home/michael/Documents/Blynk-server/./server_embedded.crt’, key : ‘/home/michael/Documents/Blynk-server/./server_embedded.pem’) not valid. Using embedded server certs and one way ssl. This is not secure. Please replace it with your own certs.
11:41:40.735 DEBUG- hard.socket.idle.timeout = 10
11:41:40.762 INFO - HTTP API and WebSockets server listening at 8080 port.
11:41:40.768 INFO - HTTPS API, WebSockets and Admin page server listening at 9443 port.
11:41:40.768 INFO - Mqtt hardware server listening at 8440 port.
11:43:04.443 DEBUG- Unsecured connection attempt or not supported protocol. Channel : /10.0.0.236:36446. Reason : javax.net.ssl.SSLHandshakeException: error:10000412:SSL routines:OPENSSL_internal:SSLV3_ALERT_BAD_CERTIFICATE
11:43:13.889 DEBUG- POST : /admin/login
11:43:24.554 DEBUG- POST : /admin/login

I guess that means it didn’t work then?

Maybe time to order a Raspberry Pi?

Pete.

I have 3 rpi computers but I had hoped to use a better computer.

I have been able to get it to work on Windows 10 and on other versions of Linux. I am not quite ready to give up but am having little to give me hope.

Maybe try a re-install then?

Have you checked that all the paths referred to in your server.properties do actually exist, and that they have the appropriate read/write permissions?

Pete.

The file paths?

I have not checked each path. I had expected it to install correctly. I will look.

Do you have a quick list of paths?

Where should I find the /admin folder?

Should it be in the root of the computer or the root of the server folder?

I meant the paths in your server.properties like these…

Pete.

I don’t see a file or folder named admin.

I deleted the user file and let it recreate it and it now lets me login. Thanks for the help.

1 Like

please mark as solved

Yay!