I installed v0.5.1 (i am using local server v0.32.0 on windows 10).
I included #define BLYNK_DEFAULT_PORT 8080 and re-compiled but my sketch no longers connects
My port forwarding setup which was working without a hitch when using v0.50.0 is below - it now no longer works with v0.50.1. Any guidance would be highly appreciated.
Hmmm… OK, so just over 8 hours ago, I had upgraded to 0.5.1 and Local Server 0.30.0 … before this latest “addendum”… and everything was working.
But, just to be safe, I just ran that iptables command anyhow on my server and rebooted… and no surprise, everything is still working…
So, I guess I shouldn’t worry about what isn’t broken but out of curiosity, what has changed that required the addendum as it appears to have affected some users and not others… inquiring minds what to know why
And finally, can you clarify this statement.
Does that mean in the hardware sketches we should NOT be using 8442 anymore?? I mean, it stiill works for me…
As usually old sketches will work and connected to old 8442 port. All new sketches will connect to 80 port. Thus local server can’t run on 80 port without root rights, you either have to do port forwarding or connect directly to port 8080 or 8442 (not recomended, as it will be dropped soon).
Server can run on port 80 but port 80 is used for other service on router. So port 80 is not possible to use for fort forwarding. Is possible to use in sketch #define BLYNK_DEFAULT_PORT 8080 or Blynk.begin(auth, wifi, ssid, pass, server, 8080) then we can forward 8080 -> 80
is there any different between 8442 and 80 on local server? i mean, could i use Blynk.begin(auth, wifi, ssid, pass, server, 8442) or #define BLYNK_DEFAULT_PORT 8442 and forward 8442 to 80 ? then all skechtes will use same port, old one 8442 by default, new one 8442 because -> #define BLYNK_DEFAULT_PORT 8442
8080 now is the default port for hardware on the Local Server.
Your hardware now should connect to 8080 port. Port forwarding is needed only when you leave default port in sketch as 80. 8442 will be dropped in next server versions. Of course for deployed hardware you still may do port forwarding from 8442 to 8080.
Hi @Dmitry I trying to get my head around this and get a clearer picture
My hardware sketch uses port 9443 as part of Blynk connect command…I assume that would mean the hardware sketch will try to initiate a session over the internet to my local blynk server using port 9443 (https) … this works today for me [do I have this logic correct ?]
By moving to 0.5.1 it does not work any longer. I’m trying to understand how does the 8080 change effect my situation from point 1.
apology - perhaps I’m not doing a good job in explaining myself.
Here is the extract on my server.properties file:
#hardware ssl port
#hardware plain tcp/ip port
#http port MY note default is 8080]
#web sockets ssl port
#web sockets plain tcp port
#https port My note default is 9443
#application ssl port