I use Caddy to my self-hosted services and computer. Thanks to that, I can use Caddy to convert 192.168.0.23 into tn.domain.com with a valid certificate. I only open ports 80 and 443. I only have to add this to my Caddyfile:
This brings up a blank page with the name of the page as “Admin Panel”. I tried to enter gl.domain.com in 3 different browsers with same results.
I can use Astro Wrap but the web address is harder to remember and it did not work when I was on a recent holiday away from my country. Also I prefer my use of Caddy for consistency.
It looks like Caddy may not be handling .js.gz files correctly.
Since we’re not Caddy experts, we might not be able to give detailed guidance on its configuration.
root@GL-BE9300:~# tail -f /var/log/nginx/error.log
2025/09/08 18:44:00 [error] 16141#0: *297 open() "/www/js/app.73f13df2.js" failed (2: No such file or directory), client: 192.168.8.1, server: , request: "GET /js/app.73f13df2.js HTTP/1.1", host: "192.168.120.73:2080", referrer: "http://192.168.120.73:2080/"
root@GL-BE9300:~# ls /www/js/ap*
apns-full-conf.json.gz app.73f13df2.js.gz
As a workaround, you can decompress all gzip files on your Flint 3 by running the following command over SSH:
find /www/ -name "*.gz" -exec gunzip {} \;
(Please note: you may need to repeat this step after upgrading firmware, since upgrades can restore the original compressed files.)
Decompression of files does not affect the operation of the router.
It uses more storage space, and consumes slightly more data traffic (a few Mbytes) during access.
Yes, you can undo the decompression by reinstalling the latest firmware.