So it seems it does find it, but very very slow
Читать полностью…Yeah you have to give it time. Once you get the red toast saying that the ping failed, it will log an error on the console.
Читать полностью…@DanMag9 @FrancescoSimply may you please pin this to make it more accessible?
Читать полностью…great! now instead of :3333
, write :9000
Sorry you lost me. I have panic running on a server without a browser
Читать полностью…the same way you run https://localhost:3333
to view browser UI
I did curl http:IP:9100/metrics from the panic server and that also goes fine
Читать полностью…ok. try access https://localhost:9000
. you should see the api docs.
Can you check whether it is a firewall issue?
Читать полностью…but then if u use the same URI, the browser can access it?
Читать полностью…When I try to readd it, when I click the Test button it also does not give the green confirmation notification as usual
Читать полностью…@Gianlucatg please pin what I'm about to bump
Читать полностью…I really have to remember trying this when there is something wrong and I can't fix it
Читать полностью…I saw a green one saying succesfully connected
Читать полностью…Nothing happens in the Console when I click the test button on the UI page
Читать полностью…Ok thanks will follow the rest your instructions from here
Читать полностью…then how are you on the PANIC UI right now ?
Читать полностью…then, press the TEST
button, and send me the logs here. Obviously hide any IPs that show up
then go back to the PANIC UI, and open console with F12
.
I already checked multiple times:
9100/tcp ALLOW AnywhereЧитать полностью…
26657/tcp ALLOW Anywhere
9100/tcp (v6) ALLOW Anywhere (v6)
26657/tcp (v6) ALLOW Anywhere (v6)
For the node exporter URL, but in browser still I can reach it like normal
Читать полностью…