I can't connect to blynk local server from RPi

I made a hotspot using raspberry pi, i install blynk, i start it and it say: Blynk Server 0.24.3 successfully started.
But when i try to login with phone, dosen’t work… what i need to do? (the blynk admin panel on raspberry pi local work fine)

what ip did you use ?

192.168.42.1 (from ifconfig)

I don’t remember a 100 % but try 192.168.1.200

If ifconfig says 192.168.42.1, it is that. There is no default IP on the Pi. It all depends on your network settings and infrastructure :slight_smile:

What does Blynk.log say in the log/ directory @Mihai_Cojocaru?

2017-05-07 08:51:28.533 INFO - Using data dir ‘/home/pi/Blyn’
2017-05-07 08:51:29.085 INFO - Region : local
2017-05-07 08:51:31.045 INFO - Initializing gmail smtp mail transport. Username : example@gmail.com. SMTP host : smtp.gmail.com:587
2017-05-07 08:51:31.891 INFO - Didn’t find custom user certificates.
2017-05-07 08:51:31.897 INFO - Didn’t find Let’s Encrypt certificates.
2017-05-07 08:51:31.898 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.
2017-05-07 08:51:31.901 WARN - ATTENTION. Server certificate paths (cert : ‘/home/pi’, key : ‘/home/pi’) not valid. Using embedded server certs and one way ssl. This is not secure. Please replace it with your own certs.
2017-05-07 08:51:37.065 INFO - Hardware plain tcp/ip server listening at 8442 port.
2017-05-07 08:51:37.069 INFO - Hardware SSL server listening at 8441 port.
2017-05-07 08:51:37.072 INFO - Application server listening at 8443 port.
2017-05-07 08:51:37.074 INFO - HTTP API and WebSockets server listening at 8080 port.
2017-05-07 08:51:37.076 INFO - HTTPS API, WebSockets and Admin page server listening at 9443 port.
2017-05-07 08:51:37.078 INFO - Mqtt hardware server listening at 8440 port.
2017-05-07 09:03:31.975 WARN - No order field ‘id’
2017-05-07 09:11:04.496 INFO - Using data dir ‘/home/pi/Blyn’
2017-05-07 09:11:06.777 INFO - Region : local
2017-05-07 09:11:08.448 INFO - Initializing gmail smtp mail transport. Username : example@gmail.com. SMTP host : smtp.gmail.com:587
2017-05-07 09:11:08.532 INFO - Didn’t find custom user certificates.
2017-05-07 09:11:08.538 INFO - Didn’t find Let’s Encrypt certificates.
2017-05-07 09:11:08.538 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.
2017-05-07 09:11:08.541 WARN - ATTENTION. Server certificate paths (cert : ‘/home/pi’, key : ‘/home/pi’) not valid. Using embedded server certs and one way ssl. This is not secure. Please replace it with your own certs.
2017-05-07 09:11:12.579 INFO - Hardware plain tcp/ip server listening at 8442 port.
2017-05-07 09:11:12.583 INFO - Hardware SSL server listening at 8441 port.
2017-05-07 09:11:12.585 INFO - Application server listening at 8443 port.
2017-05-07 09:11:12.588 INFO - HTTP API and WebSockets server listening at 8080 port.
2017-05-07 09:11:12.590 INFO - HTTPS API, WebSockets and Admin page server listening at 9443 port.
2017-05-07 09:11:12.592 INFO - Mqtt hardware server listening at 8440 port.
2017-05-07 09:11:24.690 INFO - Using data dir ‘/home/pi/Blynk’
2017-05-07 09:11:25.096 INFO - Region : local
2017-05-07 09:11:26.927 INFO - Initializing gmail smtp mail transport. Username : example@gmail.com. SMTP host : smtp.gmail.com:587
2017-05-07 09:11:27.795 INFO - Didn’t find custom user certificates.
2017-05-07 09:11:27.800 INFO - Didn’t find Let’s Encrypt certificates.
2017-05-07 09:11:27.800 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.
2017-05-07 09:11:27.803 WARN - ATTENTION. Server certificate paths (cert : ‘/home/pi’, key : ‘/home/pi’) not valid. Using embedded server certs and one way ssl. This is not secure. Please replace it with your own certs.
2017-05-07 09:11:32.196 INFO - Hardware plain tcp/ip server listening at 8442 port.
2017-05-07 09:11:32.200 INFO - Hardware SSL server listening at 8441 port.
2017-05-07 09:11:32.202 INFO - Application server listening at 8443 port.
2017-05-07 09:11:32.203 INFO - HTTP API and WebSockets server listening at 8080 port.
2017-05-07 09:11:32.207 INFO - HTTPS API, WebSockets and Admin page server listening at 9443 port.
2017-05-07 09:11:32.209 INFO - Mqtt hardware server listening at 8440 port.

Well, Blynk started all right, more or less.

If you start this at the command prompt of the Pi:

tail -f blynk.log

It all show realtime when the log is being updated (no idea how much knowledge of Linux you have, so just saying :slight_smile: )

After you’ve done that and you try to connect with your phone, does it say “App connected” or something similiar?

No… my ap just can’t connect to server… I try many ip-s and don’t work

@Mihai_Cojocaru is the server running locally and what do the logs say?

Have you changed the server IP in the app to that of your local server?

How to connect my app to raspberry pi using local server with blynk-client command?

sudo ./blynk --server=xxx.xxx.xxx.xxx --token=xxxxxxxx

There is also a port flag of --port=xxxx but it will default to 8442 or whatever the latest allocated port settings is in the server.