Skip to content

Service listens on loopback 127.0.0.1 instead of wild card (0.0.0.0) #145

Closed
@jhawk7

Description

@jhawk7

Hi, I cam across this project when searching for a way to get samba metrics into my prometheus instance running on a separate machine. I was looking for a docker option, but I was able to build the project from source and get it running on my target machine (where my samba service runs) but I was unable to hit the metrics endpoint externally. After some digging, I found that "127.0.0.1:9922" is passed as an argument by default in "etc/default/samba_exporter" the for the "samba_exporter.service" exec command (link here)

Changing it to "0.0.0.0:9922" fixed the issue, but I was wondering why it was setup to use the loopback interface by default. I expected it to listen on all interfaces given the flag value in the parameters.go file here. I'd imagine most users would have prometheus running on a separate machine. Is this mentioned in the documentation?

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions