A cloud VPS service is probably a better, cheaper and more stable solution for you.
For me, a local server (using DynDSN) was good enough, but I had some other things running on my server that was best kept away from any cloud 
1 Like
But as VPS needs our credit card info for monthly billings i am worried about it ! I had a friend whoâs card info was leaked and was used to draw money from the same and lost quite a lot of money before even he realised and blocked the card !
Afraid of credit card scams !!
Once we login from our router to DynDns we will be given an address. So while login in the app should we provide the same ?
Personally, I donât see the point in setting-up your own cloud server, except to give yourself unlimited energy. Considering the relatively low cost of energy and the high cost of a hosted server then the numbers donât add up for me.
The only compelling reason to use a local server is to have a system that continues to function correctly when the internet is down, and a hosted server obviously doesnât do that.
I think youâre asking if you enter the DDNS url in the custom server login screen of the app, in which case the answer is yes.
If you have a local server (on your home network) and the internet goes down then youâd need to connect your phone to your home Wi-Fi and log out of the app then change the custom server setting to the IP address of your local server.
Unless of course youâve set-up your own DNS server to re-direct traffic from the DDNS url to your local server IP when connected to the same network.
Pete.
This is not at all an issue !! Because Blynk is giving us such a good list of features, so paying for the energy is not all a big thing !!!
I noticed a weird thing happening that is, as now i have static ip and port forwarded, i can access the sever as intended !! But now when the internet is down my devices also start to lag(not the blynk app) !! But in the code i have specified the local ip of the server(Rpi0W)⌠when the internet is down i am not able to get the devices work as it will work normally when internet is up !! (ex push button to turn on a LED)
Yes i was asking about the custom login URL in the appâŚ
And what about the server address in the code? Can i put my DDNS url ? just like we do with blynkcloud ?
You donât need to use a DDNS service if you have a static IP.
But, if you put your WAN IP in your sketch rather than the LAN IP of your Blynk server then the sketch wonât be able to connect to the Blynk server when the internet is down. Unless of course you add a static routing rule to your router, or set-up your own DNS server on the network. None of these things are necessary if you simply continue to use the LAN IP of your Blynk server in your sketches.
Pete.
Yes , that is what i am saying. I am using the ip assigned by my router to the rpi server. I am not using my static ip address.
That is why i am thinking how is it effecting my devices even after using internal ip
Buon giorno a tutti voi e grazie sempre per il prezioso contributo !Vi chiedo nel codice come si fa a scrivere Blynk.begin(auth, ssid, pass, âtuo server.no.ipâ, 80); poiche il compilatore arduino da errore! Quando utilizziamo il servizio DDNS .Grazie
Well, first of all the standard non-SSL port for the legacy local server is 8080, not port 80.
Secondly, you only need to put the WAN IP or DDNS URL in your Blynk.begin command if the device isnât on the same network as your server.
If this is the case, and youâve configured a free DDNS service to give you a DDNS URL like âmy_blynk_server@duckdns.orgâ then your Blynk.begin command would be:
Blynk.begin(auth, ssid, pass, "my_blynk_server@duckdns.org" 8080);
Of course, you need to run a DDNS updater on the network where your local server is located so that the DDNS service always knows what your local serverâs public WAN address is.
Pete.
[quote=âPeteKnight, post:28, topic:39944â]
Blynk.begin(auth, ssid, pass, âmy_blynk_server@duckdns.orgâ 8080);
[/quote]
Blynk.begin(auth, ssid, pass, âmy_blynk_server@duckdns.orgâ 8080);
[/quote]
Uploading: no.ip.pngâŚ
questo è il msg di errore exit status 1
âauthâ was not declared in this scope, ma se metto lâindirizzo ip funziona!!
Sorry to annoy you but I canât write.
Blynk.begin(auth, ssid, pass ânameOfYourServer.ddns.netâ, 8080);because the compiler doesnât accept it .want IP address
You need to replace "nameOfYourServer.ddns.net"with the whatever url you chose when you created your free DDNS account with NoIP.com or duckdns.org
But, as Iâve said multiple times before, you only need to do this if your hardware device is on a different network to your local server.
Also, you need to be running a DDNS update client on a device on the same network as your local server.
Pete.
Ă quello che ho fatto âŚma il compilatore da errore!accetta solo numeri indirizzi ip .
Questo comando non viene accettato.
Blynk.begin(auth, ssid, pass, â my_blynk_server@noip.biz,8080);.
Thatâs not really surprising. You have a quotation mark followed by a space that shouldnât be there, and no matching quotation mark at the end.
Pete.
Quella virgolette è unâerrore di battitura.ma nel codice ho scritto bene .
Blynk.begin(auth, ssid, pass,miosito.noip.biz, 8080);
E il compilatore da errore.
Ma se scrivo cosĂŹ.
Blynk.begin(auth, ssid, pass, IPAddress(34, 122, 197, 21), 8080); tutto funziona.
A matching pair of quotation marks are required around the url.
Pete.
Iâm beginning to think that with your lack of IT knowledge you probably ought to give-up on trying to run your own local legacy server.
Pete.
Il mio server il locale funziona benissimo giĂ . da 1anno ormai ed io con lapp ci raggiungo da remoto con ânoipâ ,fin qui nessuno problema, il problema fare in modo che dei dispositivi da remoto possono comunicare con il mio server Blynk. ognuno di noi abbiamo delle lacune per questo io vado sempre a testa bassa .io sono molto tenace se qualcuno può aiutarmi lo ringrazio anche per questo esistono anche le comunitĂ .
Try taking a look at one of your sketches that works on the same network as the local server, and just change the single field within the Blynk.begin command that currently points to the internal IP address of the server and replace it wit your no-ip url.
Pete.