I have been continuing to play with Cloudflare tunnels and teams and wanted to put cockpit on a tunnel. I found out it is not as straightforward as one would think. I found a small web of things to do and an undocumented disability/bug in Cloudflare tunnels. It is not as simple as throwing it into the configuration and expecting it to work. No, you have to configure cockpit, tweak the tunnel and have a URL of a certain (loose) format. I am not certain I needed to get a LetsEncrypt cert for it so I am skipping that in this write-up. If anyone does find that it is needed, drop me a message and I will add it at a later date. For quick and dirty setup read after the break.
Some time ago Cloudflare opened up tunneling traffic from origin servers to theirs negating the need for nat punches or breaking out the credit card. This is great for say home use or someone behind a cg-nat that wants to self-host. Not so good for solving gaming issues. I found that you can run their software fairly easily on most systems but I have had one nagging thing that I wanted to try. I finally sat down and figured some of it out. I wanted to run the docker container of cloudflared. My problem has been that there has been kinda poor documentation on the how to get it going. Not saying it does not exist, it’s just not obvious on the steps. Today I will demystify some of this below:
As a follow up to my previous post as curiosity got the better of me. I decided to see how difficult it would be to set up MariaDB/Grafana/NodeRED on my Synology 1815+. Come to find out it is not that difficult to do so once you figure out the quirks of the UI you have to use.
Here is how to setup docker like I have but in a Synology system.
Recently I got the itch to learn something new and I chose to explore Grafana. Of course, I needed something to graph or make a dashboard out of. So I pondered for a while and during that time I had some trouble with my internet connection. This of course had me looking at my cable modem stats page and that’s where I found my inspiration. So many numbers that are a point in time snapshot that I wished I had a historical graph of. So I set about figuring out how to install Grafana in docker and pull the data in. I quickly found that grafana is a display thing and not a collector and display. This meant that I had to collect the data and store it so that grafana could display it. For this, I figured I could store it in MariaDB, as using that in grafana looked simple enough. The problem I had was getting the data off of the modems stats page. I plinked around with a bash script and a python script, neither did that great for me. About this time I remembered that nodered has some power to it and tried that. I managed to pull the data and store it into MariaDB via nodered. I then managed to display the data via grafana and was rather satisfied with myself.
I have written instructions on how to do this for an SB6183, it might work on an SB6190 with a bit of editing to support the extra channels in grafana. Any other modem you will have to figure out the HTML and how to slice it up and make possibly major changes to the NodeRED flow and possibly the database.