And now i’m taking life easy, learning something new everyday, it’s refreshing not living in the rat race
1 Like
Me too as borne out by those that know my email address. I left the UK rat race to “relax”.
No Corporate Finance and property.
Glad I turned down that invite to NY 
Seriously though didn’t you have manuals or checklists?
Well that depends on what you are reffering too
I have been trying to think of a relevant point to end this day, something to tie this interaction together. So here is what i have come up with. Concorde was the first passenger aircraft to use fly by wire. It was purely analogue to begin with, so even Concorde embraced the digital technology that we all now take for granted.
The most prestigious aircraft in the world was 95% analogue until the day it retired from service. Just imagine how it would have been if it were 95% Digital.
Happy Days !
hi @Costas, my nas default port is 8080 so would this mess my nas box up by putting this command in my local blynk server?
sudo iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8080
I’m not a network specialist like @Lichtsignaal and @Dmitriy so I can’t say for certain, but maybe.
Do you know how to change the NAS port?
Personally I think there are far too many people using local servers where they are not required and not understood by those that set them up. First port of call should always be Blynk’s excellent cloud based servers unless you have a very good reason not to use them and fully understand the implications of running your own server.
yes i do know how to change the nas port.
I only went the local server route due to the energy limitation of the Blynk cloud.
personally i found it rather challenging creating my server regardless of whether i did a good or bad job of it, every little bit helps. Everybody has to start somewhere, it adds to the enjoyment of IOT’s. Even though i use flashed sonoffs, i did make my own switches that work equally as good, I think that’s why people like creating things like their own servers, it adds a personal touch. I have spent weeks and months trying and failing until i get it right, that’s what is rewarding.
There is no limit on the Blynk cloud you can purchase as much energy as you desire and the great thing is that it’s “green” energy i.e. renewable.
I drive a car but I know very little of how it works. I simply turn a key and 99% of the time the engine starts. It would be downright dangerous for me to undertake work on my vehicle.
The same applies to servers used for Blynk projects and some Blynkers have exposed themselves to dangers because they chose to set up a local server rather than use the cloud servers provided by Blynk.
I accept the rewards people get from building their own systems but you still have work to do as borne out by this thread. Sometimes it’s just easier and safer to leave it to the experts than spend you own time and “energy” on replicating a ready made system.
Personally I consider local servers to be important in two areas:
-
Applications that are not internet based, like robotics, and those which require the shortest possible ping times.
-
Areas where the internet is not available without huge expense, like rural Africa.
yeah i can understand your point, but i have solar panels on my roof and i don’t live in Africa, neither do i build robots, live and let live my friend.
Anyway how do i move forward with this IFTTT issue, do i ask the 2 people you mentioned or do they get involved by virtue that you referenced them in this post? 
Change the NAS port and then set up the iptables.
Others will add their input if they see a need.
ok will do
The other thing I would suggest is to do a quick IFTTT test with the cloud. This way you know your basic IFTTT settings are OK and that the problem is local server related.
hi @Costas, rerouted all my nas ports
run both on rasp pi:-
sudo iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8080
sudo iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-port 9443
port forwarded 8080 and 9443 on router
still no good.
Think you said you have already had 8443 forwarded but also forward 8441 and 8442.
Does http://your_external_IP/your_token/project in a web browser show you the json file for your project? It’s not the same as IFTTT but it might suggest if any of your ports are being blocked etc.
Does the cloud server trigger your required pin via IFTTT?
had already forwarded all 3 above ports.
just tried http://your_external_IP/your_token
(replacing correct info)
result in chrome = This site can’t be reached
Send me your external IP by PM.
Considering that I have so many problems with my local server for example i still do not have the ability to email tokens which arose from changing the Gmail settings several months ago and considering the recent problems, I have decided to start again and install a fresh copy of the blynk local server making sure that I follow each step meticulously because I am sure the problem lies with the local server because I do not have any issues with my Nas box for example and I can use the Blynk app using my external IP address without any problems . The IFTTT was not really a necessity but more as something else that may have been useful. Thanks for all of your help so far I will keep you posted tomorrow as I finish the fresh install.
Just one question is there any way I can back up the existing 15 devices with their associated tokens from my existing blynk projects so I could then import them into the new local server?
Yes just save the contents of the data directory.
If it’s a Pi that you are using for the server then it wise to backup the SD card just in case you need to revert back to it later.
You can normally send project cloned QR codes to yourself as a backup but I suspect your server is not configured to issue them.
ok great i’ll save the data file.
lastly, i’m positive it is my local server because if i hhtp my ext ip followed by 8080
it autocompletes to /admin and the message
Failure: 404 Not Found
What happens with https://your_ip:9443/admin when using you LAN and WAN IP’s?
Did you set up server.properties and mail.properties when you created the server?