Blynk Network Port Forward Config

Blynk app for monitoring Solar Charge
  • please decide for yourself whether exposing this service to the internet is a good thing…? Perhaps you prefer a VPN solution, then your device can simply access internal services when connected.


  • DNS external and internal (dnsmasq on docker)
  • router — internet connection, port forwarding
  • nginx (docker) — proxy traffic to the blynk server
  • Blynk Server (local, docker) — note, local server is now deprecated. decided to discontinue the product.
  • apache — I was not able to get apache to proxy the stream

External DNS

  • => (my external ip address)

Internal DNS

  • => (internal ip of server on vm/docker)
  • => (internal ip of nginx)

Router port forwarding

  • 8080 => (optional, if you want devices in the wild)
  • 8444 => (stream, for the app)
  • 8443 => (https, for admin pages)

nginx config

Forward both 8444 (blynk proto) and 8443 (https) to the Blynk server

events {}stream {
upstream blynkserver {
server {
listen 8444;
proxy_pass blynkserver;
http {
server {
# Server configuration
listen 80 default_server;
return 301 https://$host$request_uri;
server {
listen 8443;
ssl on;
ssl_certificate ssl/;
ssl_certificate_key ssl/;
ssl_session_cache builtin:1000 shared:SSL:10m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
location / {
proxy_ssl_verify off;

Blynk.App config

At the login add

  • custom domain
  • port 8444

Alternative (simpler) solution

Although the solution above is somewhat complex, it allows me to use the same domain+port for internal and external purposes.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store