Local server ports and Android app issues

[scargill]

I am using an RPi2 and trying to set up the latest java 8 compatible local server.

(none ssl)

I tried default ports, server griped ports already in use - probably server running - it isnt at power up - I’ve not implemented that.

If I change port 80 to 89 and hardware default port to 8449, no more gripews when running the server, it seems happy, but the phone cannot connect - something wrong when connecting to the server. please check port 8449 is open in your network.

I’m trying to register as a new user so not authentication.

I simply filled in (to the android app) 192.168.1.158 and port 8449

No idea why it isnt connecting.

[Gunner]

Default ports for App to Local Server is 9443 (or perhaps just 443?).

From all device sketches it is 8080.

New Blynk Library v0.5.1 is Released (important for local server owners)

In this release New hardware support: TI CC3220 (Energia IDE) General improvements Blynk switched to using port 80 by default. Certificates added for easier switching from Blynk Cloud to Let’s Encrypt Add setMin & setMax to widgets Bugfixes: Fix pinMode command Fix ESP32 WiFi credentials provisioning PlatformIO, Particle, ARM mbed and OpenWRT packages have been updated accordingly. Full list of supported hardware is available here NOTE: if you have local server and uploa…

Upcoming Android 2.18.0 update (IMPORTANT for local server owners)

Dear all, in the next few days, we will release new Android update. This update has only 1, but very important change. Blynk app from now will use 443 (default https) port instead of 8443 in Blynk Cloud. This change is required as in many cases 8443 port is blocked by default in some networks. Update may affect existing local servers. Default app connection port for the local servers will be moved from 8443 port to 9443 port. The new app will connect to 9443 port of the local server by defaul…

[Dmitriy]

@Gunner

(or perhaps just 443?).

Not by default as this requires root rights. However, if you have root you may do port forwarding 9443 → 443 to avoid any “blocked” port issues.

[scargill]

sorry not following this… I just pulled this 25 day old file for local server.properties file and heres an excerpt. What should that now read and assuming I’m not interested in ssl for ease initially - which port should the app talk to? Help…

#hardware mqtt port
hardware.mqtt.port=8440

#hardware ssl port
hardware.ssl.port=8441

#http, plain web sockets and plain hardware port
http.port=8080

#if this property is true csv download url will use port 80 and will ignore http.port
force.port.80.for.csv=false

#if this property is true redirect_command will use 80 port and will ignore http.port
force.port.80.for.redirect=true

#secured https, web sockets and app port
https.port=9443

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

[Dmitriy]

App is 9443. (On cloud 9443 -> 443)
Hardware is 8080. (On cloud 8080 -> 80)

[scargill]

Hi Dmitriy

In the example extracted above, the https port is indeed 9443, but I want to go in insecurely initially until I get my head around the ssl… In the past when I initiaally used Blynk I went in on (I think 8442) non-securely. I’m not doing this with full control of the router, I wont have that control for weeks, so this it internal access only. What port for non secure use of the app?

Pete

[scargill]

ignore me - just worked on 9443