-
-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
One Issue, two questions #629
Comments
Just doing a bit of digging, I found this:
This begs the question, how to feed the custom config into the stack? I don't want to speak for Jeff or this project, but this strikes me as an exercise best left for the reader.
I think a fundamental entanglement here is whatever your current Pi's default network gateway is set for. Speculative, but the path of least resistance might be to set up another stack on the same Pi, and set a different network gateway, eg: This might take some tinkering on your part to get Just Right. |
Thanks for your response, overcame my pi-hole issue somehow (seems to need the 32 bit version of the Pi OS). Ran into the next since Pihole does not seem to have DNS resolution itself. Gravity update fails... The second instance to monitor my VPN appears to be beyond my personal skill set. In case I understand how to do that, would that then be available in the same grafana dashboard or would the separation trigger also a seperate grafana instance? THANKS |
For this, I'm assuming you're referring to the It's an issue of routing. You've (presumably) got a default route (default gateway) configured on your Pi. So if your stack is trying to check the speeds to:
how do you propose to tell the network routing "okay for this dashboard, I want you to use the default route, but for this other dashboard, I want you to send the traffic over the VPN"? I suppose if it were me, I would consider setting up a simple website on the other end of the VPN (which I presume is your home?) doing basically nothing at all (eg, the default, static page that gets shipped with nginx) and then adding to the internet-pi config the details needed to a) attempt to contact your private webserver (which would be only accessible via the VPN) and the added dashboard panel. |
Hi,
first of all, thanks for the work!
My issue: When I want to configure pi-hole as described in the instructions, it get "503 Service Temporarily Unavailable". I believe to have followed the intructions correctly.
My questions:
Any help would be apprechiated.
THANKS
homeuser
The text was updated successfully, but these errors were encountered: