Upcoming Android 2.18.0 update (IMPORTANT for local server owners)

@harukari did you update app too?

@Dmitriy Yeah the app is up to date, does the library need to be updated too? I have the server updated to 30.2 (that was easy) but my button doesn’t work. I’ve opened the new port 9443 and have the others 8440-8442 open and a custom web management port 64780. Port 8443 isn’t open anymore, could that be the issue?

Nope.

Nope.

What Android version do you have?

@Dmitriy 8.1.0

When I press the button I still get an echo message on the console that the part of code ran but nothing actually happens.

We didn’t change anything related to buttons. So I have no clues right now what is that. How exactly button doesn’t work? It is not pressed or value is not sent?

I don’t know what happened but it is somehow working now.

I have updated my local Raspberry Blynk server and updated my Android Blynk app. Checked server and it seems to be running fine but now my client seems to not want to connect to my local server.

pi@raspberrypi:~/blynkpi $ sudo node blynkclient.js
OnOff mode
Connecting to TCP: 192.168.1.69 9443
Connected
Disconnect blynk

I’m not sure what that last line means “Disconnect blynk”.
Is it trying to tell me that the client is not connecting to my local Blynk server?

I have forwarded all new/old Blynk default ports on my router, tested all new/old ports in Android Blynk app and in my client script and nothing.
Does anybody know what I could be doing wrong?
Keep in mind all was working fine before the updates.
Thanks in advance.

I got it working for now. I just went back to port 8442 on my client script and it works again.

That’s becasue this update was only referring to the App needing the port change, NOT any of the clients (ESP, Arduino, RPi, etc)…

Hi all!

Been running local server in a Docker container for half a year now without problems. App obviously stopped connecting to server after latest update but luckily I had one phone where auto updates are disabled so I was still able to connect to keep controlling some pretty critical stuff. (critical because that stuff was created for the wife and she was pretty pissed when things were not working :slight_smile: :slight_smile:

The new version of the Android app still lets me configure the port back to 8443 in custom server settings but app does not connect to server anymore. Is the port setting now ignored by the Android app or what is going on?

I would really like to just keep using the old local server for some time before I have the time to get my hands dirty with creating a dockerfile for the new version.

Hi there,

I too am having trouble connecting with the updated app. I have updated the server end to 0.30.2 and android app to 2.18.

I have replaced the domain name in the app to the ip address of the server. It still wont connect. I have switched on debug in the server.proprtites file and this is what i am getteting.

2018-01-28 15:20:57.257 DEBUG - -Dio.netty.machineId: 08:60:6e:ff:fe:e8:93:b7 (auto-detected)
2018-01-28 15:20:57.277 INFO - Hardware plain tcp/ip server listening at 8442 port.
2018-01-28 15:20:57.279 INFO - Hardware SSL server listening at 8441 port.
2018-01-28 15:20:57.279 INFO - Application server listening at 8443 port.
2018-01-28 15:20:57.279 INFO - HTTP API server listening at 8080 port.
2018-01-28 15:20:57.280 INFO - HTTPS API server listening at 9443 port.
2018-01-28 15:20:57.280 INFO - HTTPS Admin UI server listening at 7443 port.
2018-01-28 15:20:57.281 INFO - Web Sockets server listening at 8082 port.
2018-01-28 15:20:57.281 INFO - Web SSL Sockets server listening at 8081 port.
2018-01-28 15:20:57.281 INFO - Mqtt hardware server listening at 8440 port.
2018-01-28 15:21:29.699 DEBUG - Generated: io.netty.util.internal.matchers.io.netty.handler.codec.http.HttpObjectMatcher
2018-01-28 15:21:29.707 DEBUG - -Dio.netty.recycler.maxCapacity: 32768
2018-01-28 15:21:29.707 DEBUG - -Dio.netty.recycler.maxSharedCapacityFactor: 2
2018-01-28 15:21:29.707 DEBUG - -Dio.netty.recycler.linkCapacity: 16
2018-01-28 15:21:29.782 DEBUG - [id: 0x4c5856eb, L:/192.168.250.2:9443 - R:/192.168.250.193:35645] HANDSHAKEN: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

Any Ideas as to why this isn’t now working.

Regards

Paul

And it shouldn’t. The new app must use 9443 port (or those one that is specified in https.port of server.properties). If it doesn’t work after update - than most probably 9443 port is blocked in your local network.

As the workaround (in order to check if 9443 port is blocked) you may use next setup:

  1. In the app specify 443 port for the local server;
  2. In the router make port forwarding from 443 to 9443;
  3. The app should work. If it works - problem definitely in router config/blocked 9443 port.
1 Like

Thanks for this news. Some user on my server was reported they cann’t login, after update lasted server, everythings worked fine again.
One more thing is IOS app still running on 8443 port, right ? i dont see any update

A post was merged into an existing topic: Since upgrading to the App 2.18.x I cannot log in with one phone, other works OK

Right. update is on its way.

hey Guys, thanks. I like new features a lot. I just have small issue after update I am not able to connect to web admin dashboard of local blynk server and it looks like my credentials are bad. Could you help me please?

m

To get it working on my local server running 30.3 I had to set the https.port=9443 (was 7443) in server.propeties.

Until then the server was only listening on 8443 (and 7443). But now i Works.

I can confirm the issue is fixed! I assume it was either a recent iOS update or update of local server to version 0.31.0.

@Dmitriy I’m having some trouble with this. I’ve set up port forwarding on my router, and have all ports below open: 8080,8441,8442,8443,9443. The server.properties shows that https.port =9443. I’ve checked that the ports are open multiple times, but the app tells me that the ports are not open. Should I be using the LAN address, or my public IP to login to the app? I’ve tried both, to no avail