I have already posted a picture of the most upper configuration to see router, the firewall is disabled
Try splitting the ports out instead of assigning a range… just a thought.
Thanks I have already tried that, and even formatted the server and installed another linux image but the problem is the same, definitely something I’m wrong but I do not understand something, thanks anyway
Trying 80.183.31.195…
Connected to host195-31-dynamic.183-80-r.retail.telecomitalia.it.
Escape character is ‘^]’.
This means your port forwarding is correct. I can connect to your server on the designated port.
first of all thanks
sorry but I can not understand, you are able to connect? you work? He did not give you token error? as you did, or better where I’m wrong?
Well, it’s a simple telnet command, so I just checked the TCP connection, not the actual Blynk connection. That doesn’t seem to work.
Can you see in the log files my access attempt?
Sure! Now they are at work this evening (for me between 6 hours) I send the log file.
Anyway I had seen it on the server, not immediately, but after a few minutes from the attempt to log this access log appears:
WARN - Hardware not logged. /80.183.31.195:59973. Closing.
does not seem to write anything else on the log file.
However tonight Control and I send you the log, while good day and thank you.
This message means - your hardware tries to send some command without being logged.
thanks Dmitriy
Here is the complete log file.
2017-03-08 13:29:56.839 WARN - Hardware not logged. /89.188.25.132:12789. Closing.
2017-03-08 15:36:20.732 ERROR- Not secure connection attempt detected. not an SSL/TLS record: 474554202f7265636f7264696e677320485454502f312e310d0a54453a206465666c6174652c677a69703b713d302e330d0a436f6e6e656374696f6e3a2054452c20636c6f73650d0a486f73743a2038302e3138332e33312e3139353a393434330d0a557365722d4167656e743a206c69627777772d7065726c2f362e32310d0a0d0a. IP /185.40.4.18:59876
1970-01-01 01:00:36.636 INFO - Using data dir ‘/home/orangepi/Blynk’
1970-01-01 01:00:39.170 INFO - Region : local
2017-03-08 20:35:58.520 INFO - Initializing gmail smtp mail transport. Username : example@gmail.com. SMTP host : smtp.gmail.com:587
2017-03-08 20:35:58.698 WARN - ATTENTION. Certificate /home/orangepi and key /home/orangepi paths not valid. Using embedded certs. This is not secure. Please replace it with your own certs.
2017-03-08 20:36:01.423 WARN - ATTENTION. Server certificate paths cert : ‘/home/orangepi’, key : ‘/home/orangepi’ - not valid. Using embedded server certs and one way ssl. This is not secure. Please replace it with your own certs.
2017-03-08 20:36:03.794 WARN - ATTENTION. Certificate /home/orangepi and key /home/orangepi paths not valid. Using embedded certs. This is not secure. Please replace it with your own certs.
2017-03-08 20:36:05.800 WARN - ATTENTION. Certificate /home/orangepi and key /home/orangepi paths not valid. Using embedded certs. This is not secure. Please replace it with your own certs.
2017-03-08 20:36:07.693 WARN - ATTENTION. Certificate /home/orangepi and key /home/orangepi paths not valid. Using embedded certs. This is not secure. Please replace it with your own certs.
2017-03-08 20:36:10.220 WARN - Failed to find a usable hardware address from the network interfaces; using random bytes: 94:75:bb:3c:fd:be:d4:d9
2017-03-08 20:36:10.410 INFO - Hardware plain tcp/ip server listening at 8442 port.
2017-03-08 20:36:10.420 INFO - Hardware SSL server listening at 8441 port.
2017-03-08 20:36:10.423 INFO - Application server listening at 8443 port.
2017-03-08 20:36:10.426 INFO - HTTP API server listening at 8080 port.
2017-03-08 20:36:10.428 INFO - HTTPS API server listening at 9443 port.
2017-03-08 20:36:10.432 INFO - HTTPS Admin UI server listening at 7443 port.
2017-03-08 20:36:10.434 INFO - Web Sockets server listening at 8082 port.
2017-03-08 20:36:10.437 INFO - Web SSL Sockets server listening at 8081 port.
2017-03-08 20:36:10.440 INFO - Mqtt hardware server listening at 8440 port.
Can this be?
WARN - Failed to find a usable hardware address from the network interfaces; using random bytes: 94: 75: bb: 3c: fd: be: d4: d9
However, locally it works … thanks
Warnings can be ignored most of the time. I do however get the same error as you when trying to register an account on your local server.
Did you setup a server.properties file?
No, I put the file as an example, the left by default as an example.
Configure SSL is required? that’s what I need to configure?
Because the file I have not seen anything that concerns access (users apart filter that I have not configured)
if you want I can give you access to the server …
Excuse Lichtsignaal but are still at the beginning with Blynk. 
SSL is not required. It’s ok like this for testing purpose. Did you read the docs at https://github.com/blynkkk/blynk-server#blynk-server ? There are some directions for configuring the server.properties and mail and so on there.
I’ve already seen many times but the default configuration for mè okay, time, limits, and various settings for mè are ok I do not care to change.
I’ll try to change “log.level = …” to see if the server writes something more log on because otherwise you do not come out of the problem. I am sorry also to continue to make you lose more time, but I do not know what to feel.
I do try to change the “log.level = …” and see if he writes something extra to the log file and then write. thank you
I have no idea what’s going wrong with your setup, but with a default setup it should work allright. I have a more or less default setup at home too, nothing fancy and it works fine.
Are you able to connect/register an account on your local network with the App?
If it imposed local ip in this case: 192.168.1.200 on the app it works ok! connect / register an account ok! the problem is only with the public IP or DDNS.
If it imposed public ip in this case: 80.183.31.195 not works “Please check authentication tokens”.
Then it could be an SSL issue. Did you try to generate self signed certificates? That may help with the app connecting from an external host.
No I have not tried to configure SSL certificates I thought it was not necessary.
Tonight I try as you say to configure SSL certificates, and also to include on log "log.level = …"to see the results, let you know meanwhile thanks again
After many tests (formatted orange pi, configured ssl etc. etc.) I tried to change the router with another brand, and everything started to work. Thanks Lichtsignaal and to all those who helped me.