Sysadmin's workaround with using reverse-proxy (nginx):
server {
listen 80;
server_name thingsboard.example.com;
# Custom favicon
location /static/thingsboard.ico {
root /var/www;
}
# Custom logo
# Find proper filename with developer console tool (Ctrl+Shift+i)
location /static/36f68b2b2bfda81b4a46fcd2d6f8dead.svg {
root /var/www;
}
location / {
proxy_set_header X-Forwarded-Proto http;
proxy_set_header X-Forwarded-Host 80;
proxy_pass http://172.16.0.1:9090;
# WebSocket Settings
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
}
Place your files in /var/www/static
directory with proper names, e.g.:
$ ls /var/www/static/*
/var/www/static/36f68b2b2bfda81b4a46fcd2d6f8dead.svg <-- logo
/var/www/static/thingsboard.ico
In my case I used nginx, AFAIK Varnish can make this trick, too.
Hint. If you made all correctly but in your browser logo doesn't update -- open developer console again and delete it from disk cache (In my case Ctrl+F5 did not update cache.