Remote access to the metrics port seems broken
See original GitHub issueReport from @tzapu:
got a problem with teku that seems eerily similar to one i had with eth2signer ( https://github.com/PegaSysEng/eth2signer/issues/97 ) i’m running with
| --metrics-enabled=true
│ --metrics-port=8008
│ --metrics-interface=0.0.0.0
│ --metrics-host-allowlist=localhost, 127.0.0.1
but getting server returned HTTP status 403 Forbidden when trying to connect from outside the pod. seeing that i am getting 403 the port must be right.
I’ve also had truble with this. Using the options --metrics-enabled=true --metrics-host-allowlist='*' --rest-api-docs-enabled=true --rest-api-host-allowlist='*'
I can access the RPC port remotely (5051), but get a 403 from the metrics port (8008), which is unexpected. Explicitly putting my remote host’s IP address in the allow list does not help.
Local access is working OK for me with the above options.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Cloud Access Connector - Common Installation Issues ...
This knowledge base article provides a brief list of troubleshooting steps for common issues related to installing the Cloud Access ...
Read more >Troubleshoot the Atera Agent (Windows)
RMM software | PSA & Remote Access for MSPs - Atera ... Allow outbound traffic over ports 443 and 8883 (TCP/UDP) in the...
Read more >Why Can't I Connect to Kafka? | Troubleshoot Connectivity
The broker returns metadata, which includes the host and port on which all the brokers in the cluster can be reached. Kafka Broker...
Read more >Troubleshooting intermittent outbound connection errors in ...
If SNAT ports are exhausted, where WebJobs are unable to connect to SQL Database, there is no metric to show how many connections...
Read more >Troubleshoot connecting to your Windows instance
Verify that you are connecting to the correct Remote Desktop Protocol port, which by default is 3389 (use AWSSupport-TroubleshootRDP to read the current...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
My pleasure! Will keep the issue on until we figure @benjaminion’s issue as well, but glad you figured it out.
@benjaminion seems like, for your case, you were missing the
--metrics-interface=0.0.0.0
, which would have made Teku metrics visible to remote hosts. The only reason Rest API worked without--rest-api-interface=0.0.0.0
, is because of this issue we apparently have: https://github.com/PegaSysEng/teku/issues/2213. So if you provide those flags, your metrics should be accessible from remote hosts. Closing this issue as I’m pretty sure that will fix your problem, but let me know and we can open it up again.